It kinda is though. Iirc it received an interrupt it shouldn’t have received and doesn’t know how to resolve. It is not supposed to ignore it, but then the only other option is crashing at this point. Basically it continues in a dazed and confused state.

Of course the message could be clearer, but at least it also makes the message easily searchable.

Up to 355687428096000? That’s impressive!

That’s actually cool. I have to remember it next time I have to deal with html mail.

Now do html mail!

None of the tools are really made for the most trivial use cases though. Although it doesn’t take much effort to set everything up in a simple project I would probably also skip most of it. But this discussion about tiny one off projects is kinda pointless as you don’t have many of the problems to solve anyway.

I implemented a reddit frontend (kiosk mode) a while back using only vanilla JS for fun, because a previous implementation by someone else broke. There was not really a point though as it wasn’t even simpler than using the proper tools. It was just for the hell of it, but nowhere close to a “real” project.

And the simple answer is no. You can remove a layer here and there, but this is what the modern dev environment looks like.

I mean sure you can implement all that yourself and carry all the extra cognitive load, but it is not productive to even skip babel or so. There is no point, but the challenge.

Of course it is a bit more complicated to pick the right tools and you don’t have to use everything, but that’s a whole different discussion.

You always have linter steps, testing etc and a competent developer should be able to deal with all that. Of course you don’t start with all this with new students, but I don’t think that is what this post is about.

Why though? I think I am missing the point, but I don’t see the problem with having a build step in your projects. Especially for frontend it is not just JavaScript, but things like Sass/SCSS to consider etc.

Yea, especially avoid food with lots of starch. It is worse than plain industrial sugar as it is basically pure glucose, all it needs is some saliva.

Ctrl/Shift+Insert gang rise!

I was about to write the same thing. Really the object thing is the whole reason to use ORMs.

Using plain SQL is a compatibility and migration nightmare in medium and bigger sized projects. If anything using plain SQL is just bad software design at least in an OOP context.

Two weeks? I would throw away the whole fridge if I left any food in there for two weeks.

Most foods are okay for around two days without any problems. Some foods may last up to 5 days if they are salty or contain some vinegar, but it requires throughout heating to be save at this point.

I would never eat anything older than that which has been exposed to air. It’s a biohazard!

deleted by creator

Actually I did below! You are absolutely correct.

Which actually breaks the code if you don’t have sw configured to the same width as used by the code.

If anything that proves my point.

Just copy some code over into a not properly configured vim.

People seem to forget that not everything is a fully configured development environment working locally on your laptop which attempts to fix the issues introduced by that design decision.

Absolutely yes. JSON and SCSS > YML and SASS

You can work around most issues in any language with the right tools. That’s not the point.

If a design decision introduced a whole new class of errors it is probably just bad design.

Python is stupid. Using non printable characters as anything other than token separation is just asking for trouble.

Kinda. They still appear with a message telling you that they are blocked. You can press a button to show the comment anyway. It is like a soft block where you can decide if you want to read a comment or not.