A more pragmatic approach would be to run the content through something like readability[0] but leaves navigation untouched. The AI could hallucinate and add content that isn't in the original, something accessibility tools don't.
I do 90% of my browsing using Offpunk (reading blogs and articles) and, suprizingly, it often works better than a graphical browser (no ads, no popup, no paywall). Of course, it doesn’t work when you really needs JS.
What's going on at Apple? I don't own any Apple devices but the intuitive UI is their biggest selling point (even if a colleague had to explain that I have to drag the program to some window to install it).
This seems like a very strange thing to release for a company that's supposed to care about the details.
What? You can just put the executable in your path (in simpler terms put the program where the OS will look for it). You have the install command which does that and sets some permissions. That's not a hack that's just how it works. There's also apt-offline[0] which is apt (the package manager on Debian/Ubuntu and the rest) but wait for it... offline.
Of course you will need to get the source or the executable on the machine by some method, such as a USB or whatever. But I'm pretty sure Windows or Mac can't create software out of thin air either. Can you give me an example of a workflow that you use on Windows that you would like on Linux? I'm pretty sure I can help you solve it without hacks.
If you forget what you believe "installing" software means I'm sure you can learn to appreciate Linux and maybe even see that it's simpler and easier than Windows.
I'm still on X because I'm too comfortable with dwm and I've never had problems with Wayland the few times I've tried KDE/Gnome. That said blaming the user for lacking skill for basic stuff like copy/paste between applications or screen sharing isn't constructive. Those features should just work and shouldn't require skill. Building a niche window manager from source is a different discussion.
Alright, good point. Sorry for my bad first comment, I am just a bit defensive after all these years of people saying Wayland is unusable. The problems you describe with screen sharing are likely because of missing xdg-portal implementation (the implementation depends on your setup).
>Those features should just work and shouldn't require skill.
Maybe, yeah. But we are on hacker news, I assumed people would be open to hacking on things, but the comments are always very much not like that.
Is the IoT version of Windows 10 a full desktop? I tried it on my Raspberry Pi when it was released for free but I didn't get past booting. I dropped it because I didn't understand what it was, or what I was supposed to do with it and I wasn't curious enough to find out. This is your suggestion for my grandmother over some simple Linux distro with a browser?
Have you tried replacing Microsoft Office with Libreoffice? It's been perfectly usable for years and I'm even comfortable sending anyone .odt files. I haven't got a single question or comment about it. You may not be able to but in that case just use the .docx extension, install whatever fonts your colleagues expect and continue exactly as you were.
I can't take these kinds of arguments seriously because I regularly read, edit and create documents and spreadsheets and never felt the need to use Word or Excel. It seems most people I've met who claim they can't use Linux because they need X, Y or Z never really tried when I ask. It's just an assumption and they deal with Microsoft based on it.
It's a shame, we could have a world without data-mining and vendor lock-ins if we were principled and didn't always choose the easy path.
> Most people don't make their coffee in an Aeropress either.
Stupid analogy, the Linux version of that would be whatever french press you want to use. Buy your coffee ground or as beans and grind yourself, depending on preference. And for my girlfriend there's always the Starbucks equivalent (Debian stable with Gnome).
Apple would be picked by modern slaves and sold in a capsule at 100,000% markup and it only fits their machines. Windows comes with pesticides for the "benefit of the user".
I don't see how their analogy is stupid. Aeropress and french press are pretty similar from an "enthusiast coffee device" perspective. Lots of room for variability in grind size, coffee choice, and specific brewing technique with both methods.
Aeropress is a brand, one I've never heard of. It fits in the Linux ecosystem (maybe as one of the Red Hat flavors?) but as an analogy it is simplified. Linux is so much bigger than that and there's everything from LFS (grow, grind and brew with tools you've sourced and put together yourself), to Android (plain old drip machine). Reducing everything that's the Linux ecosystem to a niche brand of a specific type of coffee maker is dishonest.
I use a french press myself, and never heard of Aeropress. My machines all run Debian with DWM and I never have any problems. My non-technical girlfriend is fine on Debian and doesn't really know the difference. She did mention how fast her laptop boots though.
I am too lazy and not enough of a snob to write several paragraphs on why Aeropress is objectively better and different from French Press, but it is, and I hope someone can step up and do that here.
> Apple would be picked by modern slaves and sold in a capsule at 100,000% markup and it only fits their machines. Windows comes with pesticides for the "benefit of the user".
The exploitation of labor in developing countries in the electronics supply chain is a serious issue, and worth discussing, but it's not the dimension of the subject my comment was addressing.
Could you elaborate a little? Are you saying it should ignore vulnerable packages simply because you pinned it to a specific version? Or does it warn even if your specific version isn't vulnerable?
I use a custom grayscale theme in Neovim with 3 light and 3 dark colors. Comments are darkest, language syntax like keywords and brackets are normal, and assigned values bright. This helps me focus on what's important and ignore the boilerplate around. Everything is still readable but I can parse the code by just taking a glance at the relevant stuff.
[0]: https://github.com/mozilla/readability
reply