Something something dining philosophers.
Something something dining philosophers.
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.
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:
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.
C is crazy. While you are learning it you are learning Make and gcc without your consent.
Java is crazy. While you are learning Spring you are learning Maven or Gradle even without your consent.
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.
Haven’t watched the video, but what do you think circularization is? If you’re “just a circulization away from orbit”, you are indeed going a bit slower than orbital velocity. There’s no point to going orbital velocity if your trajectory still brings you back inside the atmosphere. To get to orbit you want to raise your periapsis outside the atmosphere, and you do that by doing a burn at the apoapsis, which is what we commonly call “circularization”.
I use famous programmers. First Linux server was Torvalds, first mac was Woz, currently in service I have Kernighan (one of the inventors of C), KJohnson (Katherine Johnson was a programmer for NASA) and Shamir (The S in RSA).
A great point in favour of maps is that each iteration is independent, so could theoretically be executed in parallel. This heavily depends on the language implementation, though.
shove some text into stdout
That’s not what this operator does normally, and if you try to “shove” something into anything else (an int into a variable? a function into an object?) you’ll get surprises… Basically it’s “special” and nothing else in the language behaves like it. Learning hello world in C++ teaches you absolutely nothing useful about the language, because it doesn’t generalize.
C, in contrast, has many instances of complex functions like printf (another commenter mentioned variable arguments), and learning to call a function is something very useful that generalizes well to the rest of the language. You also learn early enough that each different function has its own “user manual” of how to use it, but it’s still just a function call.
this std::cout << "hello world"
bullshit is in no way intuitive. You’re using the bit-shift operator to output stuff to the console? WTF? Why 2 colons? What is cout? And then these guys go on to complain about JS being weird…
No, C is where it’s at: printf("hello world");
is just a function call, like all the other things you do in C.
Meanwhile I actually studied computer engineering, but can’t legally call myself an engineer (yay Québec).
In most jurisdictions the protected title is “professional engineer”, but here it’s just “engineer”.
I use Canadian Multilingual on a ISO-style keyboard, mostly because my main language is French and typing accents on a US keyboard is horrible.
Coding makes a hefty use of Alt (“option” on mac), but they’re relatively well-placed (see the labels on the bottom-right of the keys in the pic)
My main annoyance with it is that the ANSI-style keyboard puts “ù” to the left of “1”, instead of the “/” you get on that key on a ISO keyboard (where ù is between the left shift and z). You can see how annoying this would be when programming or using the command-line. And of course, Apple stores only stock MacBooks with ANSI keyboards…
Pay peanuts, get monkeys.
I might’ve very well glanced over it, but the point is that I missed it when it’s probably the most important one. Why is it added when you do ctrl-f but not when clicking?
EDIT: Actually, it doesn’t show it until you actually type in the box:
It shows you all the filters except the one for the channel…
Having tried it, search is horrible. You have to look up the help to even know how to filter the search to a specific channel, by default it searches the whole server. I never managed to find anything, I had to ask again instead…
I have 4 kids and I don’t want to pay over 100k for a car. Believe it or not, there is currently no EV option on the market. It’s looking like the EV9 will be the first…
I use pancake, works pretty well. It’s paid, but only a one-time payment and you get the code.
EDIT: here’s the link: https://www.pancakeapp.com/
As a beginner you don’t see the benefits as it is indeed JS with extra steps. It’s not worth it for small projects and prototypes, but once you start having larger projects where you need to refactor something, you’ll see the benefits.
Also, auto-complete.
Docker’s secret that most “getting started” tutorials seem to miss is docker-compose.yml. Who wants to type these long-ass commands to start containers? I always just create a compose file, and then
docker compose up -d
.Dockerfile is for developers, you shouldn’t need more than a docker-compose.yml for self-hosting stuff.