i love your 10 tips! the way you contrast one point in direct contrast to the next point is just great! 'don't sell rust' then next tip is 'sell rust'. 'the hard part of programming is not programming' then next tip is 'the hard part of programming is programming'. (and for those who haven't watched the video, she doesn't contradict herself. just the titles contradict. it's done with such intelligence. i love it!) Nice talk, Ashley! top quality!!
I loved Ashley's talk at JSConf.... ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-DN4yLZB1vUQ.html it's funny... at the end of that talk I was thinking "hey... 'beginner's mind'... she could sneak some Zen in there"... and here we are, starting this one with a little bit of Zen.
26:33 that Log Parser's story line was left unfinished... Please tell me if they ended up re-writing it from JS to Rust in a way that actually worked faster at all? Also, I wonder how and why NPM eventually decided to choose Rust over Golang? coz Golang I would guess could be a much better choice in terms of practicality since Golang is super easy to catch-up with compared to Rust's huge learning curve.
Ashley great talk. Rust is a great programming language that allows one to control their machines and make most of your resource even when they are limited.
I would to hear about why people prefer Rust over Go. Not to start a debate, but as a Go user, I'm still trying to understand why people choose Rust. I'm not attached to Go, but I suppose there must be a good reason why people are choosing to learn a much more complicated language that solves pretty much the same problems.
Well Rust is a lot more low level (and high level at the same time!) than Go and lets you write things you couldn't in Go, like an OS Kernel. But apart from that it actually does a lot of other things that are just as valuable if not more so: * it's memory safe without even having a garbage collector * it allows really low level control over execution and memory layout * it allows really high level abstractions like map-reduce with little to no overhead * it prevents a whole class of memory safety issues, some of which (data races) even Go has! * the ownership system prevents many annoying logic bugs by default including iterator invalidation * concurrency isn't baked into the language allowing third parties to integrate all sorts of new paradigms * concurrency is really really safe in Rust, you for example cannot accidentally share a non-thread safe data structure between threads. Rust prevents that at compile time And some more probably. Rust also isn't _that_ hard. Sure, it's way more complex than Go but it is certainly not the beast that C++ is. Once you've got over the inital "fighting the borrowchecker"-hump it is _surprisingly_ easy and intuitive to use, so much so that I even prefer Rust over Python for quick scripts nowadays (I'm not a massive fan of Python though, to be fair)
You can sudo apt-get nodejs but you can't npm install apt-get What other proof do you need? But seriously, AFAIK there aren't any complete stats but what we do know is that a large majority of nodejs users use linux, and what are the most popular distros? Debian and Ubuntu, both using apt-get. You also have to remember that there are a lot servers around the world using debian or ubuntu.
In number of modules npm is first and maven central is second. www.modulecounts.com *2017* (28.12) npm 749272 [avg growth 477/day] maven central 262168 [avg growth 153/day] But if you ask me, most npm modules are a pile of junk.
The statement is itself misleading because it does not factor in the size and complexity. lines of code or hours spent making that code would be a better metric then a simple count. Not that anyone should really care.
Beginner tip: Don't ask Rust questions on Stack Overflow. You'll most likely get people telling you "You didn't read the book" which is the quickest way to alienate someone from a language. Instead, the part of the talk around 24:00 gives some nice tips. The Rust community is nice. The people answering Rust questions on Stack Overflow aren't.
that has nothing to do with being nice , you should not ask beginner questions on SO, because those have been asked and answered already 100 times somewhere on interwebs, use duckduckgo to find an answer.
The thing that probably trips you there is that the front page of maven displays the total number of jars (not the total number of packages) in a non-deduplicated fashion. Modulecounts uses the deduplicated number given here: search.maven.org/#stats The number Ashley quotes is the total number of _packages_ NPM publishes and with the code size and granularity that the JS community works, it's unsurprising the package count is higher.
