News for hackers. Stuff that matters.
Re:Ember.js 2.0 Released by jacquesm on Thursday August 13, 2015 @05:57AM (#10053099)
> To be fair, Angularjs (since you are obviously talking about it) backpedaled their "second system" a bit(since users complained loudly) and there is now some level of compat between the v1 and v2.

Why is that obvious? I can think of several other frameworks that this would apply to. Drupal for instance, Yii is another and there are quite a few more.

Re:Ember.js 2.0 Released by SwellJoe on Thursday August 13, 2015 @10:26AM (#10054423)
The upgrade situation with Drupal is, frankly, a disaster. Every major revision from 6->7->8, breaks literally every module and every third party piece of code. I'm months into migrating our website from 6 to 7 (I'm the only person working on the migration, and my PHP experience is somewhat limited). Many common modules provide no usable upgrade path, even if there is a version for both 6 and 7 (which is often not the case). And, there seems to be no inclination on the part of Drupal core developers to alter this course, or even recognition that it's a horrible user experience.

According to some conversations I've had with folks, Drupal 8 seems to be even worse than Drupal 7, and Drupal 7 is literally the worst upgrade experience I've ever had. Piles of new jargon and new APIs get introduced in every new release, and often replaces or subsumes entire swaths of similar functionality in previous releases (e.g. nodes -> entities), and Drupal was already ridiculously jargon-heavy to the point of documentation making no sense to someone without extensive experience with the specific ways they use terminology, and googling generic terms like "node" and "entity" is a laughably unhelpful process.

I have, at many points in this process, thought: "Fuck everything about this, I'm migrating to WordPress." I probably should have done so the first time I thought that, as it would be done by now. But, every time I made it over another hump in the upgrade, I thought, "Surely that was the worst of it." and kept slogging along. Upgrading WordPress is literally a no-brainer, now...you just get emails every week or two saying, "Your website has been updated to the latest version of WordPress." Sometimes, you click the "upgrade database" button.

Sorry to rant. But, I happen to be working on my Drupal upgrade again today, so I'm grumpy.

Re:Ember.js 2.0 Released by johnatwork on Thursday August 13, 2015 @12:12PM (#10055245)
The biggest gripe I've had with Drupal was when moving from 6 to 7, they had module writers pledge that their modules would be ready on the release day of 7, which a lot of folks broke the promise or worse, abandoned the project all together without letting anyone know.

So some folks were caught not being able to upgrade due to a crucial module being abandoned at 6.

Re:Ember.js 2.0 Released by SwellJoe on Thursday August 13, 2015 @02:12PM (#10056130)
I have that problem, as well.

But, the biggest problem I have is that even when there was a pledge to do so and when they actually eventually produced a D7 module (Drupal 7 is several years old...I spent most of this time waiting for the modules we rely on to become stable on Drupal 7), there wasn't a pledge to provide an upgrade path...so, you've got data in some module in Drupal 6, and no way to get that data into the same module in Drupal 7. Often there are bizarre workarounds, like using the Migrate module, which is designed to handle all sorts of migration tasks and is thus endlessly complex, and requires custom migration code (and comprehension of a huge swath of even more new jargon and convoluted, baroque, APIs).

It begins to remind me of Zope/Plone from many years ago, which had many of the same problems. Lots of jargon, lots of new ideas in each version before the old ideas were stable or fully implemented, painful upgrades, tight coupling of interfaces making changes in one part of the system require changes in every part of the system. A modular system is nearly meaningless, if every module has to be rewritten with every new release.

Re:Ember.js 2.0 Released by BillyParadise on Thursday August 13, 2015 @10:33AM (#10054486)
Software brings out the best in people :)

(now if I can get this damned rails gem to work properly....)

Re:Ember.js 2.0 Released by aikah on Thursday August 13, 2015 @06:03AM (#10053111)
Because both Ember and Angular are front-end frameworks AND competitors.

The issues with Yii and Drupal are a bit different. Yii is a serverside framework. And Drupal a CMS. I'd say the case with Drupal is way more problematic than Yii's though.

Re:Ember.js 2.0 Released by sbarre on Thursday August 13, 2015 @06:58AM (#10053293)
I think the more generalized point that was being made was for any framework, front-end, back-end, middleware, CMS, whatever..

Properly handling deprecations and providing a clear and reasonable migration path for your users will keep them happy and will keep them upgrading instead of either sticking to old versions or jumping ship.

These are not concerns that apply only to front-end frameworks.

Re:Ember.js 2.0 Released by jacquesm on Thursday August 13, 2015 @06:07AM (#10053120)
GGP said framework, not front-end framework.
Re:Ember.js 2.0 Released by andyfleming on Thursday August 13, 2015 @07:08AM (#10053325)
I think both meanings are implied and definitely both percieved. The first have "every framework should take note" is more general, and I would mostly agree. The ember team has seemed to manage their project very well. Though I don't like the style of Ember itself, personally. There are often times with projects though where breaking changes are necessary for evolution of the software. I'm not sure if there were any major trade-offs with Ember. That may be because of good planning, but good planning like anything else takes resources, and often that resource is time.

The "that's how you avoid creating another framework and fragmenting community" comment is pretty clearly about the angular mess last year, and rightly so. I have a love-hate relationship with Angular. It's been a complicated journey and at times handled poorly. They seem to be on a better track now.

Regardless, I don't think there was any malintent in nercury's post. They are all good lessons learned.

Re:Ember.js 2.0 Released by nercury on Thursday August 13, 2015 @07:43AM (#10053430)
No, I did not actually had Angular in mind when writing this. We often hear talks how new major version should handle deprecation gracefully. It was more the reaction of actually seeing it happen.
Re:Ember.js 2.0 Released by pbowyer on Thursday August 13, 2015 @01:26PM (#10055804)
To list a few more:

- The switch from symfony 1.4 to Symfony 2.0 requires a complete rewrite. Support for symfony 1.4 stopped fairly quickly; there seemed no understanding that companies wouldn't pay to rewrite their messy-but-working systems onto a 'cleaner' framework.

- MODX Content Management System. There is no upgrade path from 1.X to 2.X. Good luck to you if you've invested years developing your site on 1.X...

Re:Ember.js 2.0 Released by mattwad on Thursday August 13, 2015 @08:40AM (#10053658)
Been a while, but from what I remember, upgrading Drupal itself usually worked okay, but you couldn't because most sites relied on 3-4 contributed modules, and it would take another half year-year for them to also upgrade, if ever.
Re:Ember.js 2.0 Released by dubcanada on Thursday August 13, 2015 @09:41AM (#10054050)
I've had the same experience as you. I've never had a problem upgrading a Drupal site because of the core modules. Everything in the core upgrades fine. It's always a contributed module that breaks stuff.