31–40 of 133 posts
By low-level code, they mean… JavaScript, right? In what sense is this "close to the metal"?
Earlier quoted context omitted.
With Glimmer as a standalone library, I think ember's going in the right direction. There's been some excellent work on Fastboot and Engines in the last year or so and I really like the approach ember's team is taking with this. React, for me, still offers better composability. You deal in plain JS objects, pass them around, and can build really complex UIs on top of that. I also really like redux. I still use ember…
I think Ember is really good at marketing the stuff they work on, but it is usually overhyped. Fastboot, for example, was announced what, 3 years ago? The readme says it's still not ready to use: > The bottom line is that you should not (yet) expect to install this add-on in your production app and have FastBoot work. https://github.com/ember-fastboot/ember-cli-fastboot I find this is often true of Ember projects (li…
While the Ember devs talked about stuff like Fastboot and Glimmer, while other frameworks just had all this out of the box.
Their whole approach seems to be rather concept heavy and back in the days (2014/2015) the docs where horribly outdated and you had to check stackoverflow for basic things.
I had to use Ember 2 years on a project and found it clunky, but okay. I switched to React 2 years ago. And after I met a few hardcore Ember devs from back in the days, who said they switched to Angular2 or React I think this was the right decision. It's nice that the existing projects get so good support, but I wouldn't recommend anyone to start something new with Ember :\
Close to the metal: Glimmer is one of the fastest DOM rendering engines, delivering exceptional performance for initial renders as well as updates. Architected like a virtual machine (VM), Glimmer compiles your templates into low-level code so it can run as fast as possible—without sacrificing ease of use. By low-level code, they mean… JavaScript, right? In what sense is this "close to the metal"?
Earlier quoted context omitted.
I think Ember is really good at marketing the stuff they work on, but it is usually overhyped. Fastboot, for example, was announced what, 3 years ago? The readme says it's still not ready to use: > The bottom line is that you should not (yet) expect to install this add-on in your production app and have FastBoot work. https://github.com/ember-fastboot/ember-cli-fastboot I find this is often true of Ember projects (li…
At the end of the day, the Ember team takes a lot of time to not just build things the right way, but also make it as painless as possible for teams to upgrade along the blessed path. This has been a learning process to understand how much more time that takes, and has caused some past announcements to feel like they weren't delivered on, when in fact they simply just took more time to get right.
Earlier quoted context omitted.
With Glimmer as a standalone library, I think ember's going in the right direction. There's been some excellent work on Fastboot and Engines in the last year or so and I really like the approach ember's team is taking with this. React, for me, still offers better composability. You deal in plain JS objects, pass them around, and can build really complex UIs on top of that. I also really like redux. I still use ember…
I think Ember is really good at marketing the stuff they work on, but it is usually overhyped. Fastboot, for example, was announced what, 3 years ago? The readme says it's still not ready to use: > The bottom line is that you should not (yet) expect to install this add-on in your production app and have FastBoot work. https://github.com/ember-fastboot/ember-cli-fastboot I find this is often true of Ember projects (li…
As for Fastboot, it has its edges but there are people using it in production (DockYard is one, if I'm not wrong). ember-engines also says it's experimental and it does have some missing stuff (from my experience) but what is there works well.
Some of the things perhaps needed a rewrite of the underlying architecture. One great thing about ember (apart from v 1.13) has been just how painless it has been to upgrade. All the major changes they have made have largely been drop-in. Getting to that kind of backward compatibility is also a pretty impressive feat considering how big it is.
So, all in all, I agree that some of the things were overhyped and unrealistic but it seems they have learned from it, and I think that's just fine.
Earlier quoted context omitted.
I think Ember is really good at marketing the stuff they work on, but it is usually overhyped. Fastboot, for example, was announced what, 3 years ago? The readme says it's still not ready to use: > The bottom line is that you should not (yet) expect to install this add-on in your production app and have FastBoot work. https://github.com/ember-fastboot/ember-cli-fastboot I find this is often true of Ember projects (li…
At the end of the day, the Ember team takes a lot of time to not just build things the right way, but also make it as painless as possible for teams to upgrade along the blessed path. This has been a learning process to understand how much more time that takes, and has caused some past announcements to feel like they weren't delivered on, when in fact they simply just took more time to get right.
The other lesson to take is to be more cautious about announcing stuff before its really ready. But they don't seem to have learned that here. Here we have a project with its own logo, a marketing video with a nice electronica beat behind it, and a YouTube Live announcement...
... For something they are telling you to install from their master branch.
Earlier quoted context omitted.
I used Ember for about 2 years and thought so too. Now I'm using React and I think it's approach is much better. The API is tiny compared to Ember and there aren't much concepts, still it accomplishes everything Ember did. I feel bad to say this, but in the modular, library heavy, NPM based JS world of today, React (and other component frameworks like Cyclejs or hyperapp) fits just in. While Ember feels like a anachr…
Why would you want to build a bespoke React-based framework for every app you make? Why not simply have everything you need out of the box, plus the ability to easily integrate any npm library into your app via first-class build tooling that is miles easier to use than something clunky like Webpack?
Now I rather prefer solutions that have customisation in mind from start, so it's always easy to switch things.
"fastest DOM rendering engines, delivering exceptional performance for initial renders as well as updates." I read this every time new fw pops up. Usually those kind of claims are exceptionally exaggerated.
What's the benefit vs just writing your templates in JavaScript in the first place?
Glimmer is smaller and faster than React, with TypeScript supported natively. This is a game-changer for people who are looking for a lightweight rendering library that ships with great tooling support and a larger framework ecosystem behind it.
I wonder how it'll stack up to React Fiber. I love when libraries compete on performance, since it can end up benefiting everyone.