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.

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.

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.

To answer your question (and not just recommend another piece of software instead):

Making a cylinder and deleting the cap faces makes what’s known as a non-manifold mesh. To my knowledge this means you can see the backfaces without travelling through any existing faces (in your case, you can see them by looking through the holes you made when you deleted the cap faces).
That cylinder has walls that are theoretically infinitely thin, so you should thicken them up before attempting to print it. You can do this with a Solidify modifier. You can also extrude and scale them if you like, it achieves the same effect.

Given a manifold mesh, your slicer will treat the inside (as in, the direction the backfaces are pointing) as solid, and you can change the density and infill pattern to whatever you like.

Make a few of these shapes, both manifold and non-manifold, and see how your slicer reacts when you tell it to slice them.

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

I took a look at Unison a short while ago when I saw it mentioned elsewhere on Lemmy and I’ll say what I said before: Their Hello World example, and by extension the rest of the language, looks very weird and unwieldy to me. With the repeating identifiers and relatively alien syntax I’m having a hard time seeing this catch on.

Crystal is very similar to Ruby, but is compiled to native code instead. Would you consider that? Why or why not?

Fira Code was my font of choice for a while, but now I use JetBrains Mono! Cascadia Code is also acceptable.

I’d give it a try, but I can’t see anything before being asked to sign up.

Websites that do that just leave a bad taste in my mouth, asking for your information before they’ve even shown you what you’ll get for doing so.

It’s a stretch, but the only thing I can think of is that it might be a bit better for dyslexic people because the letters are a bit more diverse, but I don’t think it’s nearly enough to be considered an actual dyslexia font.

Neon and Argon: Seem okay. They’re really quite similar though. It’s like the designers couldn’t decide which they liked more and so just decided to release both.

Xenon: It feels alright. The horizontal serifs give everything a more uniform look, but you can also get that with any other serif font.

Radon: Uh, no thanks. It’s like someone took the weird letters from Dank Mono and said “what if we did that but for the whole font?”

Krypton: What if we just took OCR A and added ligatures? Alternatively, “Floating Point Precision Error: The Font”

Overall, none of these are compelling enough to make me want to try them. I quite like the Texture Healing feature, but it’s not enough to make me want to move to it.

Also, using multiple different fonts in one code file sounds horrendous.

this is a very old screenshot

What do you mean? It says “0 minutes ago”! Clearly it’s very recent! /s

The trick is to use tools::WireBrush;. It helps immensely for cleaning up your code.