That old autocomplete is great. It’s specifically the AI autocomplete that’s less useful.

Wow, well it’s absolutely terrible at A. B is worth a shot, but it’s 50/50 to bullshit you in my experience.

Eh, I’ve enjoyed writing a SQL query and having AI translate it to Linq. I’ve had at least one work directly, very clear on what it’s doing, just with Linq’s odd syntax. The other query was more complicated and wasn’t something that translated well to Linq. I may have had to split that into two Linq queries.

Then again, I wouldn’t count translating psuedocode (or SQL) as really vibe coding. To me “vibe coding” means you’re not really looking at the code it produces.

Yeah, I just wrote a blog post comment about how I enjoy using Copilot. But that’s when I explicitly ask it a question or give it a task. The auto complete is wrong more often than it’s right.

Probably doesn’t help that if it was tedious, boilerplate code I would have already explicitly asked it.

That’s not what the phrase “dark pattern” means.

The app didn’t seem to respect the environment variable for X11 I tried to set for that one app.

I have an odd monitor configuration, one 2k high refresh rate, HDR monitor in the center, 1080p monitors to the left, right, and above. The right is also a higher refresh rate.

I could get it to work in Ubuntu… inconsistently. Sometimes I’d log in and have one 640x480 monitor in the center. PopOS just worked.

Yeah, my monitors didn’t work under Ubuntu X11. At least on PopOS, that just worked.

I want Omnissa (VMWare) Horizon Client to support Wayland. Until then, while I have to boot into Windows for one thing, I might as well boot into Windows for everything.

Maybe next year will be the year of the Linux Desktop.

Seems like clickbait. Wikipedia does not need actual visitors that badly.

Are we not allowed to talk about an interesting intersection of advertising and politics?

You know this is a discussion board, right? If you didn’t want to discuss, why are you posting?

putting in the design effort to improve the tools in the ecosystem

They have. The problem is that they generally cause as many problems as they solve. Adding another layer in software is often as harmful as it is helpful.

LLMs are nice in this regard, because they don’t really add another layer, but they do take care of the excessive boilerplate that’s easily understandable.

But… That’s where you’d put this crap. Notepad had one job, and it did it well.

It’ll sometimes do dumb and/or redundant or too complicated shit. Pile up a couple of those and your codebase can get unmaintainable fast.

I find if you give it small chunks and keep an eye on it, it’s great.

I think one of my recent prompts was “Create a procedure that creates an example configuration file with placeholder values. If a config file doesn’t exist on start, give a warning and create the example config.”

It also works great as a replacement for an ORM.

I understand how to turn the results of a select statement into an update statement, but the AI does it a hell of a lot faster.

I find if you give it small enough chunks, it’s easy enough to review. And even if you do have to correct, it’s generally easier to correct than it would be to write it all by hand.

Also applies when the dev could know what they’re doing, but just doesn’t care to.

A diy VPN is exactly the disaster scenario of vibe coding.

Go to their GitHub and look at issues and their comments first.

Reddit was profitable off of just minimal advertising and Reddit Gold. I’m concerned about video hosting, but I think mastodon and Lemmy can scale just fine.

We have apps for that, and they’re typically a pita. They certainly take longer than just talking through your order.

It’ll go the other way, eventually. Keep the experienced people who are willing to use AI and can handle the more complicated things AI can’t.

But for now they’re just firing people and hoping things still work later. Since research and development both have delayed results, they can celebrate their win immediately and not pay the consequences til later.