Dear Google: we wouldn’t have to do this if you weren’t such a shit company.

Oh, you weren’t aware that you’re a shit company? You legitimately believe you’re a positive force for the world? Well that’s your own damn fault.

What a great idea! Just claim your product is healthy to people that don’t care about their health!

I haven’t read through the other responses in the thread, but I don’t think it’s the slightly old software that’s the problem. I think it has more to do with using older kernels, meaning that the latest hardware won’t always be supported (on the stable branch at least - there’s always testing and unstable too of course which may have better hardware support).

That may have changed with recent releases though - I haven’t used Debian for several years now. But if your hardware is supported then it’s a pretty solid choice.

Some other people sometimes mention that Debian isn’t as beginner friendly as Ubuntu or Mint, but my experiences have been similar to yours - I found Debian to more user-friendly than Ubuntu for example. Assuming that the hardware works of course - if it doesn’t then it obviously is a worse choice.

I could be wrong, but it’s my understanding that, under the terms of EU membership, this would require Canada to adopt proportional representation.

Of course today, it looks like a long shot, but the more this gets talked about, the more likely it could happen. So keep up the conversation, and maybe it will someday!

It’s a publicly traded company, isn’t it? Most likely there is some investor in the CEO’s ear asking him to push this down on all staff… so they come up with bright ideas like putting silly “requirements” like this in their job descriptions as well. And in any case, AI investors are so desperate these days, chances are that they’re doing everything they can to create general LLM FOMO in a similarly desperate push to increase adoption.

That’s what I’m guessing at least. Even to me it sounds a little like a conspiracy theory, but then again these people have a lot of influence.

It means that the parent company has major investors in the LLM space.

The whole notion of CSDs is a blueprint example of what happens when UI designers try to think things through too hard. They come up with grand solutions to trivial problems that are so poorly thought through that they create even bigger problems.

Realistically, nobody is going rewrite their entire application just because of what a tiny cabal of Gnome developers think. Just read this post that was linked elsewhere in this thread. At the end, Tobias is basically arguing that people should go out there and harass the developers of all Linux desktop applications (including the entire KDE project!) to follow through on this ridiculous idea:

Thus, our goal is for as many apps as possible to have the following properites [sic]

• No title bar
• Native-looking close/maximize/minimize icons
• Respects the setting for showing/hiding minimize and maximize
• Respects the setting for buttons to be on the left/right side of the window

Which apps are affected? Basically, all applications not using GTK3 (and a few that do use GTK3). That includes GTK2, Qt, and Electron apps.

If that alone doesn’t alert people of how out-of-touch the Gnome developers are, then I don’t know what would.

Your post is a succinct summary of the “study” of economics. It’s just supporting a conclusion in exchange for taking a bunch of bribes and cherry-picking data to support your argument.

I know what you mean, just beware: in lots of cases it’s not as universal (as in distro-independent) as some still think it is.

This is especially true when we start talking about BSDs and other non-GNU platforms.

Interesting. Were you using a Jenkinsfile? I’m not sure I completely understand your use case, but using a Jenkinsfile would mean that your entire pipeline would be defined in a file in source control, so you could roll it back if you made a change that didn’t work quite right. Seems to be what your looking for if I’m understanding what you’re looking for.

https://www.jenkins.io/doc/book/pipeline/jenkinsfile/

I looked at it for 5 seconds. The UI looked pretty hideous. Even new reddit looks better than it.

I’ve found the edit/test/debug loop in Jenkins to be much faster than Github Actions. It was quite a refreshing change when I made that transition.

The best way I found to do this is by commenting out the portions of the build that take the longest.

Which is stupid, but that’s what you get with Microsoft products.

(I get that there may be ways to test this locally, but I found this method to be the easiest.)

I thought they renamed their entire product line to “Copilot” by now, didn’t they?

Uninstalling it at this point would leave absolutely nothing left!

It’s called tivoization and started with a device called “Tivo” which was the first of its kind to attempt this procedure.

There are probably lots of hardware devices in your house that use GPL software but prevent you from actually modifying it because the hardware will refuse to run modified copies. If a piece of software is licensed GPLv3, it would violate the license terms to do something like this.

That’s certainly one possibility. But another possibility is that the people praise LLMs are not very good at judging whether the code it generates is of good quality or not…

Agreed. To make it a bit more general, whenever I see people claiming to be able to predict the future with absolute certainty and confidence, that to me is just a sign they are idiots and shouldn’t be listened to. Definitely had a lot of those in past companies I have worked in. A lot of the time, they’re trying to gaslight people into believing in their version of the future so they can sell us garbage (products, stock price, etc.). They’ll always get some fools to believe them of course.

The number-one frustration, cited by 45% of respondents, is dealing with “AI solutions that are almost right, but not quite,” which often makes debugging more time-consuming. In fact, 66% of developers say they are spending more time fixing “almost-right” AI-generated code.

Not surprising at all. When you write code, you’re actually thinking about it. And that’s valuable context when you’re debugging. When you just blindly follow snippets you got from some random other place, you’re not thinking about it and you don’t have that context.

So it’s easy to see how this could lead to a net productivity loss. Spend more time writing it yourself and less time debugging, or let something else write it for you quickly, but spend a lot of time debugging. And on top of it all, no consideration of edge cases and valuable design requirement context can also get lost too.

I’m a slow adopter of new technologies like AI LLMs. My reasoning is that if it turns out to actually be a good product, then it will eventually prove itself, and the early adopters can be the “beta testers” so to speak. But if it turns out to be a bad product, then I won’t have wasted my time on something that isn’t worthwhile.

Maybe a day comes when I start using these tools, but they clearly just aren’t all that useful in their current form. In all honesty, I’m pretty sure that they will never be useful enough for me to consider them worth learning, but definitely not so today.

Cupertino has complied anyway, and said it introduced “Notarization for iOS apps, an authorization process for app marketplaces, and requirements that help protect children from inappropriate content and scams.”

Notarization requirements mean that they still maintain total control over the operating system and what software it can run. These kinds of onerous requirements keep the bar artificially high for competitors and are only possible because they are still enforcing their monopolistic control over the platform.

So no, they’re not complying at all actually. They’re just doing the same thing in a different way.