Beautifully put, poetic even. The only problem is that, in (*actual).reality, unsafe Rust is difficult to read, difficult to write, difficult to maintain, difficult to learn, has zero features for ergonomics, and has poorly defined rules.
C and Zig have a big advantage for writing maintainable, easy to read unsafe code over unsafe Rust.
For a good base, I recommend the book "The Design and Implementation of the FreeBSD Operating System" by Marshall Kirk McKusick. It's really in depth and I was able to follow it without previously taking an OS course.
Don't forget about Objective-C++! That's where the true powers of the dark side are.
Side Note: Objective-C is such a criminally underrated language. I often see people complaining about the syntax, but it's just syntax. Once you get over it, I find that the language makes the OOP paradigm a joy to work with.
Yes, agreed. IMO, curly braces would have made much more sense. It's not even bikesheding, really. It's just a fact that curly braces are less used in most written languages. I would also argue that curly braces are a better signal to the programmer that "something programmatic is happening here", due to their prevalence as scope delimiters in most popular languages.
Swift's string interpolation doesn't catch my eye like, say, Ruby's does: `#{my_var}`. It's very easy to gloss over `\(something_like_this)`. I suspect they were going for a more "elegant" syntax at the cost of pragmatism.
" Using props and state, we can put together a small Todo application. This example uses state to track the current list of items as well as the text that the user has
entered. Although event handlers appear to be rendered
inline, they will be collected and implemented using event delegation. "
I don't see where the parent suggested no framework. It's likely he or she prefers working a different framework or library, like vue.js or even jQuery.
For me, jQuery is the bare minimum requirement. I would never attempt to write a large app in pure JS, even with babel. You would definitely run into some of the problems you mentioned.
EDIT: I see now where he mentioned no-framework JS
Regardless of these complaints, the job market for React is just too damn good to ignore. I bit the bullet and began learning. As a newbie, I understand the sentiment of this article. However, it's really not as bad as the author makes it out to be.
Also, className instead of class took all of 3 seconds to learn.
If you're interested in iOS/Cocoa development, Swift is a top-notch statically typed language with lots of paradigm flexibility. Unfortunately, it isn't used as much outside of that domain.
When I'm not on medication I'm prone to manic/psychotic episodes and usually begin to hear voices. Maybe drugging isn't the best solution, but for me it's the only one that lets me live a normal life.
There's an observable soft spot for Nintendo consoles in a lot of "PC master race" types. I'm definitely not a part of that community, but I agree a higher powered PC plus whatever Nintendo's newest console is brings something very special to the table. It also helps when my little cousins come over and I have games like Overwatch on the PC and Super Mario 3D World on the Wii U for them to enjoy
Eclim is already fairly useful for Ruby developers. I use it for the "stellar omnifuncs" it provides YouCompleteMe as described in the official docs [0].
C and Zig have a big advantage for writing maintainable, easy to read unsafe code over unsafe Rust.