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.

🧜‍♀️ Mermaid + 🔥 Fire = 🚨 Siren

Clever…

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.

that would break iMessage support on older iOS devices that no longer are supported

Yes, that’s what “no longer supported” means.

Valve is currently a private company, which is likely why they’ve been able to avoid enshittification for so long. All we can do is hope that whoever eventually takes over when Gabe steps down also has his ideals at heart.

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.

Ah I see. I don’t think there’s a way to do that yet.

If you’re so inclined, perhaps you could contribute to the discussion (or development) around tags on Lemmy here, since a feature like that would solve your issue.

Just block the community. It would have been faster than typing this comment.

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.