Yeah but like, what new features do apps have which weren’t available in those times? Embedded videos maybe? Doesn’t justify the bloat.

You might enjoy learning vanilla js and making a site with as few deps as you can get away with. Or a lightweight framework like svelte or preact. The browser stack is definitely some weird shit but it’s still somewhat approachable if you dig under the abstractions that most web devs never venture beyond. It definitely helped me cut through all the manufactured noise.

They probably got stuff done, just not the things you left half implemented code for…

Software devs in general seem to have a hard time with balance. No comments or too many comments. Not enough abstraction or too much, overly rigid or loose coding standards, overoptimizing or underoptimizing. To be fair it is difficult to get there.

Interesting, yeah. I inherited a Blazor project though and have nothing positive to say about it really. Some of it is probably implementation, but it’s a shining example of how much better it is to choose the right tool for the job, rather than reinventing the wheel. For a while I was joking about setting the whole project “ablazor” until we finally decided to go back to a React/C# ASP.NET stack. If you’re thinking of using Blazor still, though, I think two fun things to look into are “linting issues with Blazor” and “Blazor slow”. I’ve heard people praise it, but they tend to be those who consider themselves backend devs that occasionally get stuck making frontends.

I use Vscode with markdown preview, with a git repo. The only downside is that Windows incessantly wants to group instances of an application, so it’s hard to keep my notes separate from my coding stuff.

I wrote a json prettifier a couple months ago with just a couple lines of code. I thought it would take a while but ended up taking like 10 minutes.

If you think that’s bad, don’t think about how many important communications in the world happen completely verbally.