deleted by creator

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.

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.

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.

If you can use containers always use containers as a rule of thumb. VMs are less efficient in almost every way and they add some unnecessary complexity.

For docker you basically only have to backup the persistent data. So in case of the docker setup you just have to backup the mounts and probably your compose file you are using. This probably also answers your third question already. Container files can be left alone and don’t need to be considered for backups as they should be stateless and can reside in their default location (/var/lib/docker/overlay2 or so by default).

Overall it is quite simple as you only really have to consider the mounts and the docker setup. The mounts you define and should be really obvious and the docker setup is just a few config files at most or just the compose file.

Many good choices here. I didn’t see Half Life Alyx here yet. It is an amazing game which alone is almost worth the cost of VR.