The amount of their output goes up. More importantly, they excrete code faster than good developers equipped with AI, simply because they don’t bother to review generated code. So now they are seen as top performers instead of always lagging behind like it was before AI.

Whether it actually results in better code is debatable, especially in the long run.

So you double check your work, you try to be reasonably confident in your answers, and you make sure your code actually does what it’s supposed to do. You take responsibility for your work, maybe even take pride in it.

In my experience, around 50% of (professional) developers do not take pride in their work, nor do they care.

What’s even the point of playing story games then if the story is condensed and simplified to such a degree? If all explanations are spoon fed to you and the story if so primitive that the bar is on the floor it just becomes boring. At this point you are better off playing games that focus on gameplay instead, it will be a more fun experience.

It’s like reading a summary of a book of just watch a short clip about it on TikTok because books are “too long” and then calling yourself a reader.

Simple, add additional columns for the frame of reference (e.g. Earth) and elevation. You could even store space coordinates using Sun as a reference point (though you would need to update data regularly for spacecraft as they move of course).

Why do you need to store the name of a country in the database? Frontend can take the country code and display a full name on its own, and do it in a localized way too.

You are late. They have already did the same with C# extension, and made it closed source too.

Avowed and X4 depending on the mood. X4 started slow but I think I’ve started the process of getting the hang of the basics after 30 hours.

That’s not a good argument. Most of these additional languages are used for separate things, like build scripts and stuff. They don’t affect actual kernel code which is C and assembler language.

It is hard when you mix them in one codebase and need bindings and wrappers for interoperability. This always introduces additional work and maintenance burden. It’s always a tradeoff and for most projects not worth the effort. Tech corporations that do this regularly have dedicated teams to deal with boilerplate bullshit and tooling issues, so that regular devs can just code with minimal friction. Rust-in-Linux community decided to take it upon themselves, but I’m not sure if they can keep it up for years and decades in the future.

Though gradually getting of C is still a good idea. Millions of lines of C code is a nightmare codebase.

What I don’t like about Go’s error handling is that it’s built on returning a tuple of result/error instead of enum/union/variant/whatever-its-called. Which means that on error path you have to return something for successful result too (usually a “zero-initialized” struct because Go doesn’t have optionals). You are not returning result or error, you are always returning both. This is just wrong.

AFAIK kernel itself doesn’t send any signals to processes on shutdown/reboot, it just stops executing them. This is a job service manager (e.g. systemd) that terminates processes using SIGTERM before asking kernel to shutdown.

That’s why you launch them through systemd.

Some differences I see: Shepherd does some firewall management with ports, and I don’t see the services it depends on.

That looks like it sets up sshd to start when someone connect to its port, not on boot. You can do the same with systemd, but you need additional .socket unit that will configure how .service unit is activated.

Why this kind of files should be written in a programming language at all? I guess it’s a remnant from the old times, but I like when tools abstract away the programming parts, and users shouldn’t have to deal with that

Systemd invents its own configuration language (it looks like ini but there no standard for that and systemd’s flavor is its own) so you still need to learn it.

That’s the problem of most general-use languages out there, including “safe” ones like Java or Go. They all require manual synchronization for shared mutable state.