Hacker Newsnew | past | comments | ask | show | jobs | submit | trelane's commentslogin

> I always say a Pixel, because they will at least get the latest OS support in a timely fashion.

You can also install e.g. GrapheneOS after Google stops supporting them. https://grapheneos.org/faq#supported-devices


GrapheneOS only updates Pixels for as long as Google does. All their supported devices currently receive the stock OS updates from Google. LineageOS is different in that regard.

Even something already available off the shelf!

https://www.fsf.org/blogs/membership/jitsi-meet-an-often-ove...


One of my networking groups uses Jitsi. It's fine.

It's pretty awful to setup compared to the Livekit-based solution.

Was going to say the same thing about emacs: https://news.ycombinator.com/item?id=42256409

What is share dot google? Here's the real link: https://news.ycombinator.com/item?id=42256409

Bah. It's what chrome on Android is doing now when I ask it to give me the link. Fixed it. Thanks!

I had searched for it in the search bar at the bottom of the home screen, which opened it in a chrome window. If you tap the share icon on the top right, you get the share.google link. If you tap the three dots and then something like "copy link" you get the actual link.


Emacs is a full IDE, not just a quick one-off editor. Its power comes from having everything scriptable from the ground up. Contrast this with the modern Extension concept, where there is a hard line between the editor's code and any changes you might want to make to its behavior.

I think vim is probably similar, but I've not gotten into it that much.


Exactly, and infact vim is very simular, neovim in my case extensible through lua scripts as an example. It's as light or feature packed as I like.

Contrast that to Eclipse and Visual Studio (not vsCode) and it's clear why the larger IDE's are falling out of favour.


It necessarily increases the concentration of power in the hands of the few. Some of you may recall a statement about power corrupting, etc.

Just on the face of it: extending the idea of company towns to an entire _nation_ seems bad to me on paper.


My son had no problem getting a beer with his meal at 15 in Munich. We were there, though, so it was supervised. It was also Radlers, so half beer, half soda.

Indeed, "iPad" is almost a generic term for "tablet," especially for kids.


Who's buying those Samsung and Walmart ONN tablets by the truckload then? Tablets for kids are the equivalent of portable DVD players in the 2000s - a commodified device to play Netflix and Youtube on. There is no point in paying an Apple premium for something that's likely to be easily broken and need replacing.


That would be what is referred to as a market for lemons.

Apple tries extremely hard to be durably differentiated from products in the same category to avoid being dragged down in a price war to have cheap quality.

That in turn makes it hard for others to compete with them - you don't have differentiating features that would pull existing users off a mature product like iPad, and you can't come out with a cheaper product without discriminating consumers being concerned that it is fragile, clunky, and/or incomplete.


Who would ever flash alternate firmware on their wifi routers?! Or do it for someone else, like family members?


> we still don't have a filesystem that works on Mac OS, Windows, and Linux.

One of these things is not like the others.

In fact, that option supports the others as well as it can, despite stiff opposition from the other two.

Choose the "works as well as it can with everyone" option instead of the two options that try to keep their users trapped, at least, if you want to see increased interoperability.


How does this compare to the Amiga filesystem support built in to the Linux Kernel? https://github.com/torvalds/linux/blob/master/fs/affs/Kconfi...

It looks like it shoehorns proprietary binary blobs into Linux, but what is missing from the built-in drivers?


The biggest problem we have had is, that the most popular filesystem (PFS3 and its variants) and the second popular filesystem (SFS) never made it to the Linux kernel.

Just about everyone uses a flavour of PFS3 in their Amigas these days and it is a bit of a pain that we haven't been able to just mount hard disk images natively. Instead we've had to run a full Amiga emulator to transfer data to and from disk images or hard disks/memory cards, which eats into file transfer performance.


What’s the common take on SFS vs PFS? SFS came along after I sold my Amiga and I wondered which one I want to use with UAE.


PFS3 seems better maintained.

Also, I had one bad experience with SFS, but none with PFS3AIO.


Thanks! This was very informative.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: