vmware513

Unfortunately, the type support is still useless. I abandoned Ruby for the same reason, and it is still relatively slow and eats a lot of memory.

These are great suggestions: 1. Clean up your component structure 2. Document with machines in mind 3. Sync with your dev team on structure 4. Start small with one component

It is Ember.js, beautifully solving this problem since 2012.

The best change detection framework is missing from the article. It is obviously Ember.js. It is just so elegant and simple.

Luckily, there is Ember.js, which provides the best developer and user experience for a decade now, with smooth and consistent update and improvements.

Still the best choice for huge, corporate frontend projects.

Ember - Ember Data live together nicely. If you would prefer an independent modern Data library, try out Orbit.js. https://orbitjs.com/

Agree, a good library on frontend level simplify the whole development process.

Ember Data solves almost everything so you can focus on features and deliver the app in no time.

Never update. Always wipe and clean install from USB sticky. Trigger nvram and smc reset after install. Your machine will be perfect.

Actually you can use the whole attribute name as selector, like data-test-user-name-input, and if you need a dynamic id, you can add as a value: data-test-product-item="book" ;)

Why you didn't considered Ember.js? It is modern, great community support, opinionated and easy to use.

How do you manage subroutes and direct deeplink to a subpage?

I actually really like to debug Ember.js code. Because of the source map, I always see my code as I wrote it and I know when I'm in the framework's code.

Clean, well written and modern framework, like Ember.js, which supports the developer and help to implement features much faster are great choice and you won't have those problems what were mentioned in the article.

Use great tool not the hyped one...

https://emberjs.com

It changed a lot and you don't have to use all the feature if you don't need it. React with data support, router, etc can be super big... and latest Ember without Ember Data and tree shaking is small, so you win a lot of developer time and money and you end up with a well maintainable code, which can be understand by others in the first day, because of conventions over configurations. ;) IMHO Ember.js is still the best option for frontend, especially if you build a serious Web Application.

If you mainly backend dev, you should just install Ember CLI, create a new Ember app and start building.

Super simple, super modern and easy to use. You will love it and forget those hyped madness what others do...

Additionally, Ember.js devs get the highest salary in frontend world. ;)

https://emberjs.com | https://yoember.com

What is OKR?

React.js is a library, so you don't get any magic and support from this tool... you have to be very advance in programming to develop a nice app with React.

Angular and Ember are real frameworks, they support all aspect of a Frontend Application, so you can learn more concept if you start using them.

One of the best tutorial for Ember.js is https://yoember.com where you can learn it from scratch.

Actually, Ember.js gives you the same experience for frontend development than Rails for backend. So you can stay happy and productive. ;)

Hey Microsoft, please move your Data Centers to New Zealand. ;)

I started here back in time and helped to became a pro quickly.

https://www.railstutorial.org/book

If you would like to focus on frontend dev, this is a great place to start also:

https://yoember.com

Same question here. Is this the honest reality nowadays, that only one frontend library/framework became "the standard"? It looks to me, that React is "the winner" and most of us should focus on this, because others just come and goes... Is that true?

I'm a big fun of the latest GMail and of the modern Google Map. I think, their changes are usually based on thorough UX research. It is normal, there are a strong minority, who cannot get used to new user interfaces and cannot accept changes... Luckily there are alternative services, so they can use something else. ;)

Ember.js follows similar principals than Rails. Modern, matured, great ecosystem. You can move really fast with a Rails API and Ember.js frontend. Really, really fast.

Why you had to rewrite Ember.js to React? Ember.js is fast, modern and easy to work with. The Ember ecosystem is matured and reliable. It doesn't really make sense.

The best if you learn and practice the following four libraries and frameworks: React, Ember.js, Angular, Vue. You will see different concepts and you gonna be a real professional frontend dev. For example, you can create a simple interface or widget with React, but if you have to develop a complex big web application, Ember or Angular is a better choice. Most of these frameworks have great support, community and matured. Learning Ember is so easy as React: http://yoember.com

You can build a complex application with zero configuration if you follow this tutorial: http://yoember.com

Glimmer.js faster and more elegant than react. https://github.com/glimmerjs

I just don't understand this hype around vue.js. People say, one of the best feature of vue that it is somehow opinionated, howevever it has weird templating syntax.

The conclusion is simple again. There is only one framework left which is "rule them all", opinionated, super easy to use, with beautiful templating language, an fast. Fast rendering, fast for building apps, and the only with continous consistency. It is Ember.js. Obviously.

I am actively running this experiment. I will comment back 50 years later to share my experience. ;)