This website uses Deno's Fresh framework. Simple stuff, really, website and framework alike. But the rant I want to make is that there are just TOO MANY DAMN WEB FRAMEWORKS. The worst part is that this complaint is just another one atop the slop-pile. Let's be real, however. Want a job? Go get yourself some React or Angular. If you pick React, don't forget to learn a cool meta-framework. I actually have no idea whether Remix or Next.js is best in this case, but it seems Vercel favors Next. Don't take my word for it, though, because I'm not about to fact check the contents of an emotional outburst. If you feel like Angular, don't forget hope.

Professionally, I've always been an Angular boy, with a sprinkle of JQuery way back, but I'm not about to count it as actual experience. This being the case, I can't say I have ever used advanced features from other frameworks, as one would expect from a breadwinner choice. Despite this, I've always managed to get the job done (by "done", read "as far as my patience took me"), and mental gymnastics weren't very necessary. This does not feel true for our chomky Google contender, because I always need to pull in some RxJS and subscribe to it to get the value from an API call. Oh wait, now you don't unsubscribe on ngOnDestroy, you use takeUntilDestroyed. Signals are a thing, but don't forget you need to create them in an injection context. Good effin' luck using TestBed/Spectator.

Look, I realize these are mostly nitpicks and you'll do what you will with the framework, but continuous work has become more and more friction instead of a little lubricant. Its tools are featureful, but don't keep things simple, because you have to go the extra mile to use the whole swiss army knife to cut a little wire.

Let's step away from Angular for a bit, because this isn't what the whole post is about, really.

Everyone knows the pop choices, anyone can get proficient in the tools (but don't think it will happen overnight), and the ones you dream of will end up as the drivers of your side projects. Should you run into an exotic case of a company asking for experience or willingness to write in an atypical language or framework, be wise, be wary, and think ahead of the questions you'll ask in the interviews about why in the world some architect decided using a tool with a smaller ecosystem was hip.

It's not just frameworks, it's literally everything in tech, and a reality we'll have to accept. Maybe drink the kool juice and go freelance creating stuff with the tools you love, y'know? It's not absurd. "Find the right tool for the job" feels like bullshit to me, because WE are the tools, and, in the end, we pick the jobs we are able to do. I'm a webdev, so I don't go around writing bare-metal code, I just do what I know.

If the answer to a problem you want to solve happens to be "I don't know enough", good! Go study, and, most importantly, don't forget to write down your process for the good of those who will come in the future. Sometimes, however, you should flip the perspective and ask yourself: "what is it that I can achieve with what I know that would not require me to learn something from the ground up?". If you find a good answer to that, do wiz biz.

Note as of 2025-04-19: I will eventually add a comment section for no one to write.