Just getting into JS

Is this the one with the competing standards? Are we having a meta meme now?

I spend more time researching and weighing options than actually programming.

It's called Analysis Paralysis caused by Overchoice. Basically, the more similar options there are, the harder it is to pick.

It's true that you can easily fall into analysis paralysis when you start learning JS, but honestly things have somewhat stabilized in recent years. 10 years ago everybody was switching frameworks every 6 months, but these days we're going on 8+ years of absolute React dominance. So I guess that's it for the view layer.

The data layer has seen some movement in more recent years with Flux then GraphQL / Relay, but I think most people have settled on either Apollo or react-query now (depending on your backend).

On the backend there was basically only express.js, and I think it's still the king if you only want to write a backend.

Static websites came back in fashion with Jekyll and Github Pages so Gatsby solved that problem in js-land for a while, but nowadays Next also fulfills that niche, along with the more fullstack-oriented apps.

Svelte, Vue, Aurelia and Mithril are mostly niche frameworks. They have a dedicated, vocal fanbase (see the Svelte guy as sibling to your comment) but most of the industry has settled along the lines I've mentioned.

I want to add that, like you, I've become a big fan of restricting the numbers of ways to do something.

IMO, It's more time wasted choosing, more time wasted reviewing, and makes it easier to overlook errors. I want more opinionated languages and frameworks.

This is exactly why I always tell myself it'll be super fun and easy to replace a Linux distro on one of my machines, and I do the fun part of balancing release style, desktop environment, all the shiny stuff....know what stops me dead in my tracks upon install?

Deciding a file system. Because it feels like such a weighty decision with far-reaching effects.

According to internet research, they're all the right one, they're all the wrong one, they're all just fine, and don't use any of them because they'll wipe all your data. Lol

Your documentation on file system choice is either anecdotal or engineering-masters-thesis, seemingly no in-between.

I've just decided BTRFS with snapshots is great, and keep good enough backups that I shouldn't have to fiddle with the fanciest deep-knowledge features to save my system.

Might be my ADHD as well. XD

I feel the same way. Designing good, opinionated APIs is HARD, but it also provides the best experience for both the author and the consumer.

• Prettier is the undisputed king of JS formatters because it has no options by design. You set and forget.
• One of the reasons iOS is so successful is because they lock down their APIs and put strict standards on apps, making it hard to write something that doesn't at least look good and slot into the OS well.

Among other examples.

I came from a cpp background and loved it the moment I saw it. Like, you mean I just go var foo = ... and then I can put anything? No type casting?? No types??? Finally, I was free.

But I've always been more of a hacker than a real programmer. I've since learned that there are advantages to using types, static checking, etc...

All of these bring me a sense of dread, each in a unique way.

Java I have a special loathing for, but the ecosystem isn't too wild, just verbose and so XML heavy.

JS is its own hell because of the sheer number of permutations of technologies a given project will use. There's always at least one nonstandard framework or tool lingering around from an old trend.

Python reimplemented the same dep management wheels 5x each, and I have no idea what common stacks look like anymore, but every time I encounter Python projects, something is always broken.

C is nice and easy from what I've used (just GCC & make), but idk what complexity arises in bigger projects.

Just so glad I'm not a webdev anymore and work with mostly just Rust, cargo, and containers.

I like Tailwind. It makes me not write CSS or any preprocessor DSL. It's nice.

Good ol' jQuery - never thought I'd hear that

Some even turn the safety off for you

Wait are people writing Go for frontend code now? Or do you mean just replacing the node back end with Go?

I’ve heard nothing but good things about HTMX

I've only ever heard anything "bad" about HTMX and it was here on Lemmy, actually. I ran into someone who was absolutely certain that HTMX was unsafe by design because it leveraged HTML over the wire and was therefore susceptible to HTML injection attacks, specifically by injecting malicious scripts that could be ran from domains you didn't control. I tried explaining that proper utilization of access-control headers innately prevented this because they worked on the browser level and couldn't be intercepted or interfered with by HTML injection by design, but he kept insisting it was unsafe while refusing to elaborate. He was very wrong, of course, but also very confident.

Not yet but I've looked into it.

I guess a hint is that is probably barely a JS framework and it's for static sites.

Well, if it gets the job done. I'd only argue about maintainability there maybe, as other devs get involved.

In my final apprenticeship work, I also only used vanilla php and argued that it would take too much time in this project to evaluate and learn a framework and that I know the vanilla way pretty good, so it's valid this way around.

I used to use JQuery (and I still do occasionally when doing scripts for WordPress where its included natively), but modern vanilla JS has solved 90+ % of the reason why we needed JQuery back then.