I saw it and I don't think it make it any justice, Ruby on Rails changed the paradigm of creating web applications with routes instead of files (like PHP, JSP and Webforms did) with the MVC pattern that now is present in every respectable web framework and the documentary doesn't tell that. It was enjoyable though.

Struts was a popular Java MVC framework in the early 2000’s and was pre-Rails.

I kind of feel bad mentioning Struts and Rails in the same sentence, though, as Rails did much more than Struts.

MVC dates all the way back to Smalltalk in the early 80s.

I do seem to remember DHH complaining about "XML pushups" when Rails was released, and knowing what he meant from Struts.

MVC was already used in frameworks like WebObjects for example (and maybe others) quite a while before Ruby on Rails was born.

Sure but I think the point is Rails popularized it.

MVC was popular before Rails. Rails certainly introduced MVC to a lot of new people, though.

It probably made it more available to the masses (as WebObjects was not free and license costs where in the region of a car at some point)

the `<Book>` generic type doesn't translate to anything at run time, so you cannot actually parse the json out as a book class, unless you already knew it was going to be a Book. The parse() method cannot be generic over all possible inputs as is - unless the user also pass in the `Book.class` parameter!

You can use something like `new JsonParser<Book>(){}.parse(json)`

Not saying that's a good idea, though.

Type erasure.

Parent just missed the new keyword, and generics can work based on return type as well with the above syntax. It has nothing to do with erasure, we are at compile time.

I've maintained the same Delphi application for 16 years now, made with Delphi 7, and is working 24/7 all the year (no failures, generating about 20,000 db records daily), amazingly only consumes 7mb of ram and is superfast, try doing that with electron.

I've heard from some of its employees that Jetbrains is on panic, they are losing tons of webstorm and pycharm customers to VSCode.

I'm in a mixed setup, 3 days in the office plus 2 from home, works fine, as long as they see my commits in Github they have no problem with that, I'm planning to change it to 2 days in the office and 3 from home.

To me is simple, to never ORM, it saves lots of wasted hours in the future.

It doesn't work on Edge nice job Google. https://imgur.com/a/QhIzx4e

And people younger than 30 created them.

Yup, at 55 Savushkina Street in St. Petersberg!