> The first rule you should remember when reading HN is the real world is not HN.
Can you explain what you mean by that?
Can you explain what you mean by that?
I truly believe that mithril is better than React or Vue people just don't know about it, it's not part of the hype cycle. React is FB and was one of the first and Vue is designed in a very community-centric way. Had we done that project today, we'd probably pick one of those because they are a lot better on resumes.
HN is full of people that post dozens of comments a day. You have to ask yourself what the people who don't need to talk about it all the time are using.
That same team I'd sit down and chat with the CS PhD majors that were doing machine learning. It genuinely surprised me when a brilliant student said he'd never heard of Rust.
TIOBE is a garbage metric, but Rust's numbers are paltry there. It's key to some really important projects, but it still isn't a widely-used language.
IMO it’s better (explicit) to see a call to `.clone()`, but maybe this is because I’m not up to my elbows in C++ everyday. Either way, I think Rust will continue to grow in popularity (C as well).
And it's used exactly nowhere. Can you name one project that is rust based and isn't part of the rust toolchain?
Parts of Firefox are implemented in Rust.
Swc is a JS bundler written in Rust.
I agree it's not a super in-demand skill as far as job postings go, but it's not exactly completely unused either.
Some others : https://lib.rs/command-line-utilities
Oh hey, that's me :)
I'm a big believer in the idea of mastering fundamentals, and even explicitly mention in the mithril.js framework comparison page[0] that you can build production quality stuff with any framework (including of course mithril.js)
There's this pervasive notion with newer tech that new things must be objectively superior than old stuff, but the way I see is that everything comes with trade-offs, e.g. Rust may indeed be safer than C, but conversely it's also been characterized as difficult to learn/keep up with, and IIRC has a less broad range of target architectures.
I think, however, that reading resources like the "The descent to C"[1] article that's up on front page can help someone getting into C, but also Rust, and even someone who wants to gain some insight about how Javascript works under the hood, precisely because it's a resource more about fundamentals than C per se.
Similarly, there are fundamental patterns that appear over and over in competing technologies (e.g. routing in JS frameworks, or DI in object oriented systems), and this goes for even the design of said patterns (e.g. principles of encapsulation, composition and orthogonality)
I've even had success applying the search of fundamentals to other disciplines. Bruce Lee famously said "fear not the man who has practiced 10,000 kicks once, but I fear the man who has practiced one kick 10,000 times". But one hidden insight is that in martial arts "it's all about the hips": once you "get" the insight about the role of hip rotation, all striking techniques improve by leaps and bounds. Many such "fundamental" insights exist, from insights about balance to insights about tells.
In music playing, one universal insight is that effortlessness is quite literally a matter of muscle relaxation (beginners often get stuck in a rut because they tense up unconsciously). Etc.
It's fun looking for fundamental insights.