check this out!

Completely useless…

Yes

This is your second post about this and you got the same response last time.

Try a third post, maybe it’ll go differently next time.

I don’t know of any other IDE maker that has the depth and quality of language support that JetBrains offers.

Honestly, throwing your toys over a modal commit dialog seems a bit misguided when switching to any other IDE is going to involve coping with much bigger changes.

You have the option of using an old version if the newer ones aren’t to your style. I’m still on the 2023 version of PyCharm, for instance. And the 2020 version of PhpStorm, haha

Yeah a little bit of coding

Here and there.

A couple of lines probably.

Hey @[email protected] did you use a LLM like Ollama to write your post?

No shade if you did, I just want to make sure we’re categorizing things correctly at our end.

Thanks for the update.

So far the only OS / DE I’ve found that explicitly bans LLM contributions is Haiku OS.

Months of work to redo one super basic dialog box.

It blows my mind how slow large companies are.

I’ve been happily using lxqt for 6+ months. Their matrix channel is very alive and knowledgeable.

Ahh yep, that’ll be it. Thanks.

That I regret link isn’t working for me.

Yep me too.

Fuck off Jack

Apparently Bun was always an especially bad example of how to use Zig.

From https://andrewkelley.me/post/my-thoughts-bun-rust-rewrite.html

The Zig team regularly checks in on our users’ projects. We read source code to find out how the language is affecting users, we test changes to see how problematic breakage might be, and we check for performance regressions.

We became increasingly horrified at the programming practices we saw in Bun’s codebase. Hacks on top of hacks. Abuse of assertions. Most of all, recklessly speeding past feature after feature with very little time taken for reflection and elimination of bugs and technical debt. Jarred was already writing slop well before he had access to LLMs. Now, it’s not our business to police what our users do, but you may have noticed people screaming in our faces about memory safety constantly. You can imagine how we might want to put some social distance between ourselves and a project whose irresponsible software engineering practices invite the exact kind of criticism that people are eager to level.

We made futile attempts to guide them towards better programming practices. There were a few exceptional heroes who did their very best in a dysfunctional company. You know who you are. But you can’t stop a rising tide.

By this time, we all felt at ZSF that Bun was a net liability, and this was before RoboBun became the #1 contributor.

Yep. Assume the worst, imo

Ahh so bots are finding subdomains by scraping SSL certificates?

Yep. Everything on that site is AI generated. Another one for the block list!

Good question.

A GUI will be easier to get into - you can use a gui file browser app to learn the layout of the file system, you can use a GUI text editor to change config files, that sort of thing. It’ll mean you can do a few basic things intuitively which will be less intimidating. So from a maintaining momentum and morale point of view it might be best to have a GUI initially even though you have to learn all the cli stuff eventually anyway and you’ll most likely be running a headless server on real hardware eventually.

Self-hosting is a very individual journey - everyone wants different things and finds they own way to meet their own requirements. So there isn’t really one guide that covers everything.

Anyway, as a general road map:

1. Create a Virtual Machine on your PC. Install Linux inside the VM.

2. Play around in the VM to learn Linux basics. When you break the OS you can just wipe the VM and reinstall.

3. In the VM, try some docker containers until you’re comfortable-ish with docker.

4. Maybe try Yunohost in the VM. You might find Yunohost saves you a lot of time and hassle.

5. Get hardware suitable for your goals.

6. Install Linux, configure networking and docker containers on real hardware.