mudbutt

Google abandons open source projects all the time, I don't see how that is a strong argument. Facebook actually uses React, IMO Angular 2+ was built for the sole purpose of consulting, thus more breaking changes and magic DSL.

I code in Ruby everyday and I think JS is a far superior language. Javascript has closures, modules and hoisting that complies and stores functions and variables before executing.

In Ruby code starts executing before everything is initialized making it unpredictable. Also JS is just so much smoother is composable. It's far superior to RUBY IMO

I would argue that it is by far the worst Framework one could possibly choose.

It drives me crazy when I hear things like Angular4+ is better for "Large Ambitious Applications with large teams" when in reality Angular4 suffers from the same slow down/performance problems as Angular 1.x.

https://github.com/angular/angular/issues/14041 https://www.airpair.com/angularjs/posts/angularjs-performanc...

I mean it's like they ignored all of the lessons and knowledge the industry has learned and produced a Framework that has issues built in! But I guess the Framework was designed with consulting in mind.

Yeah when I first saw the headline an image of a Chinese Erlich Bachman sprang to mind. Although the absurdity of the whole thing is pretty humorous for some reason it made me sad.

dunno why.

I think it's the fact LinkedIn uses Ember. Anything built with Ember is sluggish and bloated

I can't imagine any smart developers using Ruby anyone, I know because I unfortunately work with Rails and anyone with a brain cell has already left. To me deciding to use Rails isn't a very smart decision

Sorry for being an idiot, but when you reducers you don't mean the native .reduce do you?

Finding bugs for something you wrote yourself is easy because you WROTE it and can easily reason about what each method does, what data/methods does it have access to etc. etc.

Anyways, I unfortunately work with Rails and I hate it. To me Rails stresses and encourages bad practices, everything has an implicit environment inherited from a massive hierarchy of classes with their own implicit environment that will only work if the current state of the app matches what each classes assumes it will be.

Data changes and morphs during the initialization and creation of class instances causing shitty bugs. EVERYTHING needs careful consideration of all of these relations and class hierarchies before writing simple things.

Everything is highly coupled and interwoven making a change one place break something somewhere else. Rails should be taught in Universities as a case study in the pitfalls of Object Oriented Design

Also essentially all of the major players have left and moved on to new things. Most Ruby Gems haven't been updated in years!