• 0 Posts
  • 89 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle




  • I fail to see how that’s relevant here. The guy isn’t a US national and wasn’t in the US when he committed his alleged “crime”.

    He has absolutely no duty towards the US and is 100% free to associate with whoever he wants, and yes, even Russia.

    US has no standing whatsoever in this situation, and it’s a travesty of international law that Sweden and the UK even entertained the idea of extraditing him. The response should’ve been “go sue the American who actually committed that crime on American soil. Oh wait, you’ve already convicted her, and she’s already out after serving her sentence? WTF are you going on about then?”



  • 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.


  • ebc@lemmy.catoProgrammer Humor@lemmy.mlJust getting into JS
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Honestly I think the main thing that the JS ecosystem does well is dependency / package management (npm). The standard library is very small so everything has to be added as a dependency in package.json, but it mostly works without any of the issues you often see in other languages.

    Yeah, it’s not perfect, but it’s better than anything else I’ve tried:

    • Python’s approach is pretty terrible (pip, easy_install, etc.) and global vs local packages
    • Ruby has its own hell with bundler and where stuff goes
    • PHP has had a few phases like python (composer and whatnot) and left everyone confused
    • Java needs things somewhere in its $PATH but it’s never clear where (altough it’s better with Gradle and Maven)
    • C needs root access because the only form of dependency management is apt-get

    In contrast, NPM is pretty simple: it creates a node_modules and puts everything there. No conflicts because project A uses left-pad 1.5 and project B uses left-pad 2.1. They can both have their own versions, thank you very much.

    The only people who managed to mess this up are Linux distributions, who insist on putting things in folders owned by root.




  • ebc@lemmy.catoProgrammer Humor@lemmy.mlJust getting into JS
    link
    fedilink
    arrow-up
    39
    arrow-down
    2
    ·
    2 months ago

    To any non-js dev taking this too seriously: A good half of the technologies mentioned in this meme are redundant, you only need to learn one of them (in addition to the language). It’s like complaining that there are too many Linux distributions to learn: you don’t, you just pick one and go with it.







  • Just be aware that there’s a huge difference between coastal sailing and bluewater sailing. You can sail “on the ocean” but stay relatively near shore in a lot of boats. All the ones I’ve mentioned would be good for coastal sailing, where you’re never more than a few hours away from shore.

    To go truly offshore and cross an ocean you really want something more substantial. Why? It’s mostly because you’re much more likely to get caught in bad weather or to get something that breaks, so you need a lot more redundancy (spare parts, etc) and the boat needs to be built to withstand a lot more forces. Offshore you’re also constantly moving because of waves; something that flexes a little when you hit a large-ish wave will maybe flex 3-4 times during an outing in coastal or protected waters, but will flex every ~4 seconds for 20 days during an Atlantic crossing which adds up to about a half-million times. This can break a lot of stainless parts on your boat.

    Anyway, still achievable, I just wanted to add some perspective


  • ebc@lemmy.catomemes@lemmy.worldWon't someone think of the yachters.
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Licensing isn’t really a thing in North America (except maybe the $50 card we have to get here in Canada), insurance can get complicated / pricey but you only really need liability which is much cheaper, and all the fire & safety stuff usually comes with the boat and isn’t that expensive anyway.

    You can obviously go crazy on electronics, and boy are these expensive indeed, but you can also just use any old tablet* with Aquamaps or Navionics installed. Try to get one that’s waterproof or get a waterproof case.

    The most expensive part, honestly, is where you park it.

    So yeah, it’s a money-pit, but it’s possible to keep costs under control.

    (*) You need a tablet with a GPS receiver. iPads used to only have it on cellular models (no need for a plan), but most Android tablets have it.