FizzyOrange

Presumably because Forgejo didn't have CI support until extremely recently. And because Jenkins is trash.

Depends what it's for. I think a simple CLI text editor like this probably shouldn't have any smarts. Obviously an IDE like VSCode or IntelliJ should.

It's not quite that bad. They say

This means that we cannot accept any changes based on the GNU source code.

You are totally allowed to look at it. For example if there was some weird behaviour that you couldn't work out, you could look at the GNU code to understand it.

What you can't do is closely base your code on the GNU code. I.e. you can't just translate it from C into Rust.

I agree. The right way to integrate AI into this process is to pre-fill the "release notes" box with an AI suggestion, that you then edit.

I don't think it works well enough yet.

Some of us live in the real world.

I don't think height adjustable matters. It's more important that it's deep (80cm+). Though I think most height adjustable desks are that deep.

Yeah based on my experience of lots of people using Linux in companies, you're pretty lucky.

But obviously it can both be true that most people have no issues and it's really unreliable. Like, I would guess 20% of people in my company have serious issues with Linux - random crashes and not going to sleep in bags. That's really bad! But still 80% of people have no issues, which is why you always see confused comments like yours on forums saying they don't have any problems.

You can't automate these tasks without AI because anything that was capable of generalising to automating such a diverse set of tasks is AI.

Unless you're never doing new development you can't automate them. The kinds of tasks I've used this for:

• Making an HTML visualisation of some complex function inputs. One-off project. I could totally do this but it would take me way longer.
• Formatting a complex and very long SystemVerilog file. There aren't any existing SystemVerilog formatters (and certainly none that would handle the insane level of ifdefs in this file).
• Writing a script to delete all Git branches at a particular commit. I only used this once.
• Writing an Asciidoctor custom annotation. I don't know Ruby so...

You can't automate any of those.

I think this strategy makes perfect sense and is really working.

Most of the open source community uses Linux or Mac for development. Windows is pretty much an afterthought. You even sometimes see "cross platform" projects that don't work on Windows.

But now that you can use WSL for all that development there's much less reason to use Linux in the first place. At my company we have a couple of hundred people using Linux, and we're considering all moving to Windows with WSL because the hardware support on Linux is just too unreliable - random crashes, laptops not going to sleep when you close them, poor thermals, bad memory management, etc.