Pyro

Not to mention VSCodium already exists.

I figured they would just run sfc /scannow and then sit staring at their screen bewildered when it inevitably does nothing.

Just found this article about it that seems to fundamentally misunderstand it in every single way. I didn’t know it was even possible to be this clueless. Either that, or it’s AI.

Thor from Pirate Software (a game studio) does this. He has his set up so that if he doesn’t log into a specific server for a year, the source code to his game will be automatically published.

You could do the same thing. Just grab a super cheap server that checks the last login date and sends out emails.

Probably off-by-one errors

You can code in Notepad in the same way you can eat off the floor with your hands. Using better tools is a nicer experience.

As for performance, when one of the world’s most popular editor runs on Electron, it’s not that hard to see why performance could be an issue when working on large projects on older hardware.
I’ve never personally had an issue with VSCode’s performance, but I’m also fortunate enough to be in a position where I can afford a relatively modern machine. Many others have to make do with what they have, which is why Zed might appeal to them.

implying that any developer actually reads warnings

I reverberate.

I want to like Forgejo but the name is really terrible.

Is it “forj-joe”? Nah, that double-J sound is way too awkward.
Do you then merge the J sounds to make “forjo”? If so, why not just call it that?
Is it maybe “for-geh-joe”? That seems the most likely to me, but then that ignores the “build < forge” marketing on their website.

I know it’s pretty inconsequential, but it feels weird using a tool that you don’t even know how to pronounce the name of.

Seems like a “haha JS bad” kind of joke, but OP seems to forget that Python is also in a similar boat.

You at least have to know that it’s a meme format. Otherwise it just looks like someone complaining about async with a bad crop.

Interestingly, this JXL loads in Boost, but the one in the post doesn’t. Perhaps it’s because it’s inside a comment?

I would say finding that the bug is in a library is worse than finding it in your own code.

If it’s your own code, you just fix it.

If it’s in a library you then have to go and search for issues. If there isn’t one, you then go and spend time making one and potentially preparing a minimum reproducible example. Or if you don’t do that (or it’s just unmaintained) then you have to consider downgrading to a version that doesn’t have the bug and potentially losing functionality, or even switching to another library entirely and consequently rewriting all your code that used the old one to work with the new one.

Yeah, I’d take my own bugs over library bugs any day.

Do people actually say “select star”? When I read SQL I always say “select all” because it reads better.

That’s horrendous, I love it.

I quite like the term Software Alchemist.

To me, the words “engineer” and “developer” both imply that a well thought out and structured plan is in place for them to do their job. Not so with “alchemist”, which implies a fair amount of experimentation and uncertainty, both of which are very common in the software industry.

I get the advantage, and if I could change our schema with a click of my fingers I would, but it’s not that easy. We do use the native date type in our schema, but the dates we store in there are in local time. It’s bad, I know. It was originally written by a couple of people about 15 years ago, so software standards were a lot more lax back then.

We already have many customers with lots of data that are currently using this product, so it’s unfortunately non-trivial to fix all of their data with the current systems we have in place.

We developers often want to fix so many things but we’re often told what to do based on what the business cares more about, rather than what we actually want to fix. That’s why we always end up building shit on top of shit, because the business doesn’t want to pay us to rewrite 15-20 years worth of legacy code despite in doing so it would make the product an order of magnitude better in every conceivable way.

I think what they meant is requiring that only UTC time should be in the database. This prevents ambiguity when pulling dates/times out as with many poorly designed systems it’s not possible to know whether a date represents UTC time or local time.

At my work we store local time in our database and I hate it. We only serve customers in our country, which only has one time zone, so that’s fine for now. But we’ve definitely made it harder for ourselves to expand if we ever wanted to.

Inko looks like it copied Rust’s homework and changed it a little.

I don’t really see what it offers that I couldn’t get from another lang. What’s the USP?

The did not follow the hivemind of “Rust good, JS slow, C complex, PHP bad” which clearly means they are in the wrong /s