Ember.js 7.0

https://blog.emberjs.com/ember-released-7-0/

by satvikpendem • 2 months ago

79 27 2 months ago

blog.emberjs.com

roxolotl• 2 months ago

I love that ember is still going. It’s obviously not the number one choice these days, might never have been, but it represents approaches to frontend web dev that are very different from the standard so it’s always great to see the diversity of ideas out there.

triyambakam• 2 months ago

Since an agent could write all the boilerplate needed, I wonder if that offers any more reason to choose Ember over other frameworks/libraries now

kordlessagain• 2 months ago

not much probably.

atonse4• 2 months ago

I loved ember for years. Even attended EmberConf in portland around 2015. In fact, I'm just weeks away from retiring my last ember codebase that was in production and worked great for a decade (but I haven't updated in 5 years, since I was unable to keep up with all the changes). But after years of the community dying the most slow and boring of deaths, and having an absolute nightmare needing to hire Ember consultants, I really soured on it.

It is the main reason I completely stick to the boring mainstream (like react) now, so I'm never again stuck between "nobody knows Ember" and "this one consultant is charging $28k a month cuz I'm competing with LinkedIn, Netflix, and Apple" and then am stuck with them implementing engines for fun and then I don't have the time to undo it months later - all left me wanting to flee.

Basically, left it for non-technical reasons, just practical "literally nobody except billion dollar companies use this, I've painted myself into a corner" reasons.

But I do have fond memories of building things with it, personally.

sergiotapia• 2 months ago

Kudos for sticking it out. But man EmberJS is basically CakePHP at this point. A relic of days gone by. May as well use Marionette or Backbonejs.

HatchedLake7212• 2 months ago

Ember is not Backbone or Marionette, both of them are stagnant. Ember’s actively maintained and improved with 6 week release cycles and LTS versions.

Ember on frontend is what Rails is on backend: less fashionable, opinionated, mature, and still useful when you value long-term app consistency over ecosystem hype and new JS framework of the month.

rohitpaulk• 2 months ago

Same here. Loved the LTS thinking and Ember data being built in but hiring was a pain and ecosystem packages were often out of date.

HatchedLake7212• 2 months ago

We had the same issue hiring 8 years ago in the UK.

Since then I realized I’ll never require a react/vue/angular/ember/svelte/etc experience, just go for good JavaScript developers with frontend experience, framework doesn’t matter.

Took them a week or two to understand the Ember patterns that’s it.

I think we overcomplicate, all these frameworks are just slightly different ways how to build web apps, the core patterns are the same. Anyone experienced can pick any of these frameworks in matter of days or weeks.

Same on the backend, great if you’ve have experience with any of the express/hapi/koa/nest/fastify/hono, but if you don’t have experience with the one we use, it’s still fine. Hire good engineers, not good “framework” engineers.

atonse4• 2 months ago

You’re so right. I had the same experience early on finding elixir developers so I just thought, I don’t care anymore, I’m just going to try to hire smart people.

And so the 2-3 devs we had working on elixir learned on the job just fine.

But it’s sometimes also the flip, where some candidates don’t really want to learn a tech that isn’t attractive on a resume. But those are probably the wrong candidates anyway (only saying this with experience)

ksec• 2 months ago

I wonder when will Discourse move to Ember 7.0?

And Apple is still using Ember? I seems to remember they moved off it some years ago.

atonse4• 2 months ago

I think Apple Music (the web version) runs on ember.

I thought the main LinkedIn website runs on ember? I can't tell anymore cuz so much of it is obfuscated.

mrcwinn• 2 months ago

Backbone if you’re a real engineer.

steve_adams_86• 2 months ago

We could have just stopped at Backbone. It had everything you needed, if you were a real engineer.

xaxfixho• 2 months ago

GWT still rocks!!

jauco• 2 months ago

Before backbone there was already knockout.js which was based on signals. Which is what all the hip frameworks are converging on now anyway. You could have bypassed all the drama.

BilalBudhani• 2 months ago

Backbone written in CoffeeScript if you're an OG engineer

unsungNovelty• 2 months ago

I've been waiting for their Polaris edition for a while now. It looks like it is still not released. But am gonna learn Emberjs one of these days. It will be my secondary framework for projects.

We need more LTS versions of dev tools like emberjs, django, node etc. And am a fan of their RFC process as well. It looks like this is the framework you use if you want to incrementally improve stuff without having to go through radical shifts between versions.

ErunamoJAZZ• 2 months ago

Cool, just in time for the maintenance contract in the old legacy project I worked on like 10 years ago.

pjmlp• 2 months ago

This brings back memories, I thought it was long gone in the magpie attention world of frontend frameworks.

winrid• 2 months ago

I remember my first full time frontend job I applied to in like 2013 the job listing said I should know ember, backbone, and angular. I was kind of living out of my car so I just studied up a bunch on Ember at the time at random Starbucks.

It turns out they didn't use any of those and didn't ask questions about them in the interview. :) After a year or so they did start using Angular though.

Anyway, I did end up playing with ember and backbone around that time. Cool to see it's still developed.

SwiftyBug• 2 months ago

I don´t get the design choice for Glimmer components:

  export default class CounterComponent extends Component {
    <template>
      <p>0</p>

      <button type="button">+1</button>
      <button type="button">-1</button>
    </template>
  }

This is obviously not valid JS. If they already had to create a DSL for components, why not embrace it fully and introduce a different keyword instead?

    export default component CounterComponent < Component {
        <template>
            <p>0</p>

            <button type="button">+1</button>
            <button type="button">-1</button>
        </template>
    }

JSX class components, even though not technically valid JS (render method returns HTML-like syntax), resemble a JS class much more as it requires methods to declare the template and handle component lifetime.

HungSu• 2 months ago

I'm glad to see Ember is still in development. There are a lot of good architectural decisions in there that I miss when I'm in React, and there's a lot that casual React developers could learn from it and other opinionated frameworks. It was sad to see that Ember was held back by obsolete design choices for so long (Vite took years!! And AMD modules are only being deprecated now in this release)

dzonga• 2 months ago

ember was well made but the api was just way too complex.

they tried to bring the convention over configuration thought from rails to js.

it worked for people that had crazy engineering resources such as Addepar & Heroku.

but react & angular were just easier to get started with. Angular with their early typescript support in angular 2 then just took the fire out of ember. React with its earlier simple model shifted all the hipsters & newcomers.

Ember.js 7.0

Related Stories