Look, the naming ship has sailed and sunk somewhere in the middle of the ocean. I think it’s time to accept that “AI” just means “generative model” and what we would have called “AI” is now more narrowly “AGI”.
People call videogame enemies “AI”, too, and it’s not the end of the world, it’s just imprecise.
That is a stretch. If you try to download and host a local model, which is fairly easy to do these days, the text input and output may be semi-random, but you definitely have control over how to plug it into any other software.
I, for one, think that fuzzy, imprecise outputs have lots of valid uses. I don’t use LLMs to search for factual data, but they’re great to remind you of names of things you know but have forgotten, or provide verifiable context to things you have heard but don’t fully understand. That type of stuff.
I think the AI shills have done a great disservice by presenting this stuff as a search killer or a human replacement for tasks, which it is not, but there’s a difference between not being the next Google and being useless. So no, Apple and MS, I don’t want it monitoring everything I do at all times and becoming my primary interface… but I don’t mind a little search window where I can go “hey, what was that movie from the 50s about the two old ladies that were serial killers? Was that Cary Grant or Jimmy Stewart?”.
Seems to go to the OPs point of having open software alternatives, though. I am in a fairly unusual place regarding the practical usage of some of these things, but I do agree that if the entire concept is fundamentally rejected among proponents of open software that delays the possibility of developing viable alternatives to work around those issues.
Yeah, for sure. If you just drop Ubuntu or Fedora or whatever on a machine where everything works for you out of the box the experience is not hard to wrap your head around. Even if one thing needs you to write something in a terminal following a tutorial, that’s also frequent in Windows troubleshooting.
The problem is that all those conversations about concurrent standards for desktop environments, display protocols, software distribution methods and whatnot are hard to grasp across the board. If and when you hit an issue that requires wrapping your head around those that’s where the familiarity with Winddows’ messy-but-straightforward approach becomes relevant.
In my experience it’s not going through the motions while everything works or using the system itself, it’s the first time you try to go off the guardrails or you encounter a technical issue. At that point is when the hidden complexity becomes noticeable again. Not because the commands are text, but because the underlying concepts are complex and have deep interdependencies that don’t map well to other systems and are full of caveats and little differences depending on what combination of desktop and distro you’re trying to use.
That’s the speed bump. It really, really isn’t the terminal.
Well, the good news is that of course you can use Linux with only as much command line interaction as you get in Windows.
The bad news is that the command line REALLY isn’t what’s keeping people away from Linux.
Hell, in that whole list, the most discouraging thing for a new user isn’t the actually fairly simple and straightforward terminal commands, it’s this:
Here’s where it gets a little trickier: Scrolling on Firefox is rough, cause the preinstalled old version doesn’t have Wayland support enabled. So you either have to enable Wayland support or install the Flatpak version of Firefox.
This is a completely inscrutable sentence. It is a ridiculous notion, it brings up so many questions and answers none. It relates to concepts that have no direct equivalent in other platforms and even a new user that successfully follows this post and gets everything working would come out the other end without understanding why they had to do what they did or what the alternative was.
I’ve been saying it for literal decades.
It’s not the terminal, it’s not the UX not looking like Windows.
Hey. Hey? Hey. Hello friend.
You just got good advice. Remember that the world is not only for you.
Like, it’s super not for you. It’s mostly not for you at all. If you ask me whether I care about things for people with disabilities or things for you, you don’t even chart. That’s only two options and you’re not even second on that list.
So yeah. Good advice.
Local and secure image recognition is fairly trivial in terms of power consumption, but hey, there’s likely going to be some option to turn it off, just like hardware acceleration for video and image rendering, which uses the same GPU in similar ways. The power consumption argument is not invalid, but the way people deploy it is baffling to me, and is often based on worst-case estimates that are not realistic by design.
To be clear, Apple is building CPUs that can parse these queries in seconds into iPads now, running at a few tens of watts. Each time I boot up Tekken on my 1000W gaming PC for five minutes I’m burning up more power than my share of AI queries for weeks, if not months.
On the second point I absolutely disagree. There is no practical advantage to making accessibility annoying to implement. Accessibility should be structural, mandatory and automatic, not a nice thing people do for you. Eff that.
As for the third part, every alt text I’ve seen deployed is not adding much of value beyond a description of the content. What is measurable and factual is that the coverage of alt-text, even in places where it’s disproportionately popular like Mastodon, is spotty at best and residual at worst. There is no question that automated alt-text is better than no alt-text, and most content has no alt-text.
That is only the tip of the iceberg for ML applied to accessibility, too. You could do active queries, you could have users be able to ask for additional context or clarification, you could have much smoother, automated voice reading of text, including visual description on demand… This tech is powerful in many areas, and this is clearly one. In fact, this is a much better application than search, by a lot. It’s frustrating that search and factual queries, where this stuff is pretty bad at being reliable, are the thing everybody is thinking about.
Same but for tab groups. I can’t believe it took this long and every extension-based alternative is busted in some fundamental way.
AI generated alt-text running locally is actually a fantastic accessibility feature. It’s reliable, it provides a service, it can absolutely be deployed securely.
It’s fine to be critical of technology, it’s not fine to become as irrational about it as the tech bros trying to make a buck.
You guys know that MS rolls out updates through a system of multi-layered opt-in channels and deploy to the wider channels in chunks over longer periods of time, right?
They may not be the most competent or scrupulous megacorp, but they do hire actual software engineers and stuff.
Quest Link yes, I was referring to the alternative Steam Link app that is available on Quest. That’s maintained by Valve (and honestly works better than the wireless version of Quest Link, IMO). I was wondering if that works as an alternative, but I wouldn’t be surprised if there are still dependencies for controller inputs and head tracking that need Oculus software installed to work on the server side.
It’s roughly consistent with Steam survey data, and given the current context, Linux Steam users are heavily incentivized to contribute to the survey. The numbers are what they are.
Plus the guy’s argument is that relevant data sources separate ChromeOS out because it’s substantially different, which is a fair point, regardless of the accuracy of the data.
You used a bunch of words but you aren’t saying much new.
Again, those differences are meaningful. It makes sense to have a different name for it. You can lump it and MacOS and Android as a singular family of OSs, but they’re clearly different products with different branding and different functionality.
You’re also ignoring how much all of those “succesful Linux” non-Linux systems are tied to hadware, which is ultimately the issue. The terminal isn’t as much of a dealbreaker as the Linux community makes it out to be (and neither is the UX not being identical to Windows, BTW). The problem is the lack of hardware support and the finicky configurations, terminal or no terminal. Steam OS, all the flavors of Android and Chrome OS are all customized to the hardware they ship with and work well with it. In all cases the hardware is locked and it doesn’t need much readjusting, and when it does it’s often through a live support update system.
And yes, I have thought of ChromeOS as Linux, don’t be patronizing. I am saying it’s not the same as the desktop-focused Linux distros that are trying to support modular PC hardware in the way Windows does. Because it isn’t.
As a person that also went “screw it, I’m going back to Windows 95” for the exact same reasons in a previous millenium…
…no they aren’t.
This isn’t new, this has been the way this works for decades. Sure, there have been improvements, but also plenty of steps backwards. This run at it has been a noticeably worse experience than, say, being told about Ubuntu and being surprised at it having a smooth installer for the first time. Sure, gaming then was a no-go, but with PC hardware being a much narrower path then, it was so much easier to get the hardware itself running.
And yes, it was about to be the year of Linux desktop then, too.
I mean, it is, but part of the appeal with the stock GNOME was how streamlined and un-Windows-like it was. I tried moving to KDE but, honestly, it does feel a bit worse to use.
Not that it matters, because eventually a bunch of other more fundamental unsupported features made me switch back instead. Couldn’t get the Nvidia dGPU to work and messed things up enough in the process that I’d have to start over, which is a dealbreaker. Plus it turns out that the suspend/restore functionality was completely broken and the hardware volume buttons were partially broken.
So yeah, no, I’m back to Windows now.
It doesn’t, and it can’t. Also can’t do any UI scaling between 100 and 200% out of the box. There are some astounding gaps in it for how long it’s been around.
It’s not about being 1:1. I have used Android, iOS, MacOS and a bunch of other systems. Most of those have been easy to adapt. In fact, like your friend, I prefer the GNOME look because the MacOS-ish UI feels fun and fresh after being on Windows for so long.
It’s the ratio of troubleshooting versus usage and the lack of definitive resolution for things.
FWIW, I just went back to Windows, not because I found the terminal commands hard to grasp (I started working with computers in the 80s, I’m not intimidated by a command line), but because they often didn’t match what tutorials said, or because something that didn’t work didn’t generate an error and simply did nothing, or because something just randomly stopped working for no reason and just dangled there, broken, indefinitely.
Say what you will about how haphazardly Windows is architected, but most of the time if something breaks it’s a matter of either installing the right thing, uninstalling the right thing, finding the right setting or reinstalling the OS. That sense of rebuilding your bike as you ride on it that Linux still forces upon you is just so friction-heavy, and the failstate of it is so frustrating. There’s a reason why a dedicated Android or ChromeOS for your hardware feels just fine but desktop Linux is untenable for 90% of users, and it’s not the 1:1 parity with Windows.
That’s a fair point. I suppose conceptually that’s what those organizations were trying to do. So it’s a failure in execution which then probably acts as a deterrent for other corporations considering stepping up to challenge MS on modular desktop PCs, which aren’t that big of a market in the first place.
I guess if you were going to do that you’d pair it to rigid hardware instead for that reason and at that point you’re Apple and we’re talking about MacOS.
Well, no, that’s not applicable here. I’m suggesting a proprietary, corporate-backed desktop default in the way we have a proprietary, corporate-backed laptop reference in ChromeOS, a corporate-backed mobile reference in Android and a proprietary, corporate-backed handheld default in SteamOS.
It’s not about covering everyone’s use cases, it’s about applying commercial priorities and funding to one specific use case.
I mean, you know the Linux community craves that opportunity, because the amount of hype around SteamOS when that dropped on the Deck was insane, and despite their clear lack of interest in expanding it into a Windows alternative for other product types there’s been no pushback in those circles.
Yeah, on that I’m gonna say it’s unnecessary. I don’t know what “integration with the desktop” gets you that you can’t get from having a web app open or a separate window open. If you need some multimodal goodness you can just take a screenshot and paste it in.
I’d be more concerned about model performance and having a well integrated multimodal assistant that can do image generation, image analysis and text all at once. We have individual models but nothing like that that is open and free, that I know of.