Comment by progx | Hacker News Reader

Comment by progx | Hacker News Reader

Starting a fresh new (internal) project in our company, no specs, no borders, we can use any JS lib, framework, tool, whatever.

Now we stay like a kid in front of a candy shop and don't know what to choose.

Anything has pros and cons, but nothing really convinces us. It seems that all candies look great but taste like spoiled fish.

We are a small team and we don't have the time to update the app with every new version of a framework.

We stepped back and looked at our internal tools, which needed the least time of work for updates etc. and we currently think we use no framework. Only a really really simple one. That would possible need more time to build an app, but saves a lot to maintain the app. This tool would be used for the next 10 years (ok 20 years in reality).

Our oldest internal tool is 22 years old (manages customers, projects, domains, servers, etc.), got a little update some months ago to work with newest browser, update to newer php-version and that all within only 2 weeks. 2 weeks! That is today not enough time for a modern build setup ;-)

10 years ago, non of the current JS frameworks exists, or you have to do so much upgrade work to maintain you apps. 20 years ago? OMG unbelievable. Now think 10 or 20 years in the future. I think none of the current frameworks will then exists.

The dilemma of choosing the right tool for a long-term project is understandable. We are running an open source React framework called refine for building Enterprise B2B apps like admin panels, internal tools and dashboard.

It's designed to be ensuring that projects remain maintainable even as time goes by. With its headless architecture, it can be used with custom styles or any UI library and data services. Maybe it helps you somehow

You can check the examples with source code: https://refine.dev/docs/examples/

Repository: https://github.com/refinedev/refine

Thanks, will have a look at it.

10 years ago I was creating apps with Ember.js, which is still a current JS framework.

And how many times you have to update your app? How many time you need for maintain?

I’ve been maintaining Ember apps since 2015 and there’ve been 4 new major versions I’ve worked through, but the project’s deprecation policy and migration tooling have enabled incremental migration over time so there’s never been a need to hard fork / rewrite the app in a way that has occurred with several other (once-)popular web frameworks.

Yes, the update politics of ember is a good example for all. But it comes normally with a cost (features, speed, better solutions, whatever.... don't know currently enough about ember to form a judgment there).

I used ember too for a little own project, when it was version 1 (ONE), but i can't remember today why i not used it anymore.

Respectfully Ember is not current at all. Might as well call BackboneJS or Marionette current as well.

Ember still has significant updates, it's still innovating alongside the best of them, it still has annual conferences, and the productivity a team gets by choosing Ember is still right alongside most popular frameworks for creating and maintain ambitious web applications. The same cannot be said for Backbone or Marionette.

Reply on news.ycombinator.com