Hacker News new | past | comments | ask | show | jobs | submit login

This is exactly why I am a huge fan of ember.js

Unfortunatelly it fell behind in popularity mostly due to some unimportant reasons (eg not being able to render 1M rows faster than react) and some important ones (load times), but boy did they build a stable ecosystem! I haven't seen such a commitment to stability and guardrail upgrades to this day on any other piece of front end library.




Ember is one of those frameworks that isn't as "flashy" as the latest and greatest javascript frameworks, but it just keeps quietly working and adopting new techniques from the more popular frameworks on a consistent and easy to follow schedule. They even make upgrading to the latest way of doing things relatively painless by providing scripts to automate many upgrades for you.

> 1. Before removing a feature in a major version, it lands as a deprecation in the previous major. A deprecation is only enabled by default once we have a clearly documented migration strategy that covers the use-cases of the old feature.

> 2. When we ship a new major, the only thing it does it flip deprecations targeting that new major into errors.

https://bsky.app/profile/wycats.bsky.social/post/3lg2p5dwuzk...


I'm thinking of building a long term living app (say an app that I will use the next 30 years).

It has to be a web app so I was thinking of going pure JS. With that requirements in mind would you recommend ember.js?


I know this is kind of the contrarian opinion and I'm not trying to be "that guy", but if you want a web app that works in 30 years you would probably be best off building a server-side rendered application. You need a server, HTTP, HTML, and CSS for any web application, but you don't always need a lot of client side javascript.

The fewer things you have in your stack, the fewer things can change under your feet.


Go for web components. It's guaranteed to last 30 years


If you MUST use a framework, then yes i would go with ember because they have a prooved commitment to following the web standards rather than creating their own custom standards that they throw away the next year.

Having said that, 30 years are very VERY long time in web development. Maybe pure js isn't a bad call, but it depends on how large it is going to be. Someone else mentioned considering sever rendering, not a bad cinsideration either.


If you are designing for that kind of long term I suggest looking into SmallTalk. A lot changes in 30 years.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: