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.

Perhaps try making a simple web chat application. I recommend it for a myriad of reasons:

• You’ll get to touch upon all the layers of a web app (DB/backend/frontend) in a manageably small way.
• You’ll be able to make multiple choices to learn different technologies - like which database type to use (SQL/document), which message passing method to use (requests/sockets), which frontend framework to use (Solid/Svelte/HTMX/etc), and so on.
• Getting a minimum working system is very fast. You can easily spend less than a day completing this, even as a novice.
• Once completed, there are many extra goals you can set yourself. Try adding roles, commands, enable sending pictures, embedding metadata for links, etc. You need only look to your favourite chat app for your next idea!

“Will ever finish”, not “has already finished”. It needs to predict.

It’s a reference to this.

It’s not even that. I can generally read a C-like language, but when the first line I see is a long-ass array of bytes with zero documentation it just makes me not want to even try.

While I agree with the premise of the article, the code is completely unreadable to me. I took a look at the first snippet and just thought “Nah.”

I used to only use C#, and I liked the simplicity of only using one symbol to access any prop/field/method. But now I’ve used Rust for a while I do prefer separating the two for the same reasons you mentioned.

So no, you’re not alone. Even cross-lang!

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

Last I checked, almost none. They provide a JS API for common functions, so as long as you’re keeping things relatively simple you might not have to touch much Rust at all.