React 16 is for browsers, it doesn't have much to do with ReactOS. I'm not sure what you mean.

These are not very helpful questions, are they. I do care about the memory and it's state, thanks. And of course the longer the code the longer it takes for it to compile - this is why we optimise.

Mostly, yes. Does it mean they are less important?

Man, it got serious... I admit - it was easier to get help from the Ruby community a few years ago than it is now, but still - it exists and there are many answers to interesting questions available in the Internet, one of them being my post. So - it is a wild community, but it is a good community. You may think that Ruby sucks, but I know what I know - it's awesome to prototype apps efficiently and quick start basic API (with Ruby 5).

I'm not sure if junior devs can tell the difference between several different ways of coding the same features, if you ask me. It would be an easy world if they did, because seniors wouldn't have to lead every ticket in the project. But to teach them and help them is the very reason why I wrote what I wrote, so you're probably right. Thanks!

Compared for example to Elixir. Some things that are the reason why it's so easy to start coding using Ruby, follow the programmer for years - like Active Records and no 'join' or 'include' in quiry, which causes 'n+1'.

As a Ruby programmer, I often hear that Ruby and Ruby on Rails are very slow, but are they really? After a few years working with Ruby code I think that the problem is more complex. In this short article I would like to show you where the main problems are and how not to fall into their trap. I hope that after reading it, you will look at code in a different way.