News for hackers. Stuff that matters.
Re:Yahoo stopping all new development of YUI by Rygu on Friday August 29, 2014 @02:41PM (#8243847)
FUD. Backbone is nothing but a bootstrap. It really just means that you evetually rely on literally twenty or thirty other "micro" JS libraries to get the same shit done that one framework could singlehandedly provide. Those micro libraries have a higher abandonment rate than anything.

Personally I'd go for company-backed projects.

Re:Yahoo stopping all new development of YUI by shangxiao on Friday August 29, 2014 @02:50PM (#8243908)
Just a note about company backed projects. I backed Google Web Toolkit a few years back. Big mistake.
Re:Yahoo stopping all new development of YUI by spankalee on Friday August 29, 2014 @04:26PM (#8244361)
GWT is still being maintained, and I hear GWT 3.0 is on they way with a lot of great features.

The problem with GWT is that newer Google-associated projects are perceived by some people as better (and the comparison is not always apt): Web Components, Polymer, Dart, Angular, etc.

But that doesn't somehow make GWT any _worse_ than it was before, and it's still improving. The compiler is faster, they're adding Java 8 features like lambdas, the JS interop is better, they're tracking web APIs closer, and I think they have a even plan for web components integration.

I used to use GWT extensively, and I would be one of the ones to argue that it's approach was great at one time, and probably a bit outdated now, but it's not abandoned and it's evolving to fit better with today's modern browsers. I might not choose it today, but I wouldn't regret choosing it a few years back, or be in a huge rush to move off of it if I had a large codebase.

Re:Yahoo stopping all new development of YUI by shangxiao on Friday August 29, 2014 @04:39PM (#8244405)
It's funny because although I regret using it to deliver products, I don't regret having been exposed to it as a developer. I learnt a lot about how to build well structured front end code by using it.

I still believe it's doomed though just because I don't believe they can match the pace of the JS world.

Re:Yahoo stopping all new development of YUI by peterb on Friday August 29, 2014 @03:06PM (#8244017)
Why? This is not a troll, I'm very interested in your reasons.
Re:Yahoo stopping all new development of YUI by gknoy on Friday August 29, 2014 @03:34PM (#8244177)
As someone who has been working with GWT, and since moved to JS, I can elaborate on why I agree. GWT was an excellent tool when I started using it, but has been eclipsed (no pun intended) by substantially nicer frameworks (IMO). I am extremely thankful to be using it as little as possible, and am migrating as many of our GWT apps over into Javascript apps as soon as workload allows. (I'd LOVE to hear from someone who is currently using GWT, and has compelling reasons that it's a great tool that are not driven by the inertia of a large codebase.)

The main reason I'm glad not to use GWT is that I enjoy developing in Javascript a lot more than I do in GWT (Java). I have found that I can implement, modify, or troubleshoot a UI roughly an order of magnitude faster than I used to be able to do it with GWT. This is due to a combination of being able to reload by refreshing my browser (no slow re-compilation steps), as well as being able to inspect elements/styles directly in the Chrome dev tools.

There are about an order of magnitude (or more!) people who write about Javascript, or $FrameworkOfChoice (Angular, Backbone, etc) than there are that write about GWT. This includes both blogs and Stack Overflow, not to mention examples on JSFiddle or the like.

GWT doesn't easily let me integrate other Javascript libraries or components, so you have to implement your crappy version of Chosen (or similar) yourself. There's no JQuery or Underscore or similar, because it's all Java (basically).

The Chrome Dev Tools or Firebug are >>> the GWT debugger. The GWT Dev Mode plugins required for debugging, is also no longer supported in Chrome, and soon in Firefox. (I discovered this last week, the first time I've touched GWT in half a year. There's a newer Dev Tools alternative, but I've been unable to actually get it working.)

Javascript testing tools (Jasmine, phantomJS, etc) and build tools are now a MUCH more mature ecosystem than they were when GWT was first invented. We used to use a combo of JUnit + Watir/Selenium to test our UI, and now we can do similar with Javascript frameworks in a less fragile way.

In summary, GWT was awesome, but I see no reason to use it today. It helped me find my current job, so I'm grateful for that. However, if you were looking for a web framework, you would be much better served (IMO) if you chose React, Angular, or Ember rather than GWT.

Re:Yahoo stopping all new development of YUI by calebrichardson on Friday August 29, 2014 @05:29PM (#8244603)
I have used GWT on two from scratch front ends within the last 8 months.

All of your points are true and well written, but at the end of the day, I don't want to write and maintain large apps in JavaScript (or really in any dynamically typed language for that matter). GWT is still the best way to avoid that.

Re:Yahoo stopping all new development of YUI by lmm on Friday August 29, 2014 @11:14PM (#8245500)
Have you touched on Angular in Dart? I agree with the value of typing, but full GWT just feels very clunky.
Re:Yahoo stopping all new development of YUI by skybrian on Friday August 29, 2014 @05:29PM (#8244600)
Sorry to hear you couldn't get it working. We're seeing about 5x compile time improvements in Super Dev Mode on trunk, but setup is not as easy as it could be. (It's being worked on.)
Re:Yahoo stopping all new development of YUI by shangxiao on Friday August 29, 2014 @03:24PM (#8244120)
Well it's no longer "Google" Web Toolkit, it's now just "GWT"; they've handed it over to a steering committee.

At the time I loved using it as it had many nice features. But sadly it's very hard to migrate from. Most importantly is the vendor lock-in with the 2 framework specific RPC mechanisms used to communicate to the server.

Re:Yahoo stopping all new development of YUI by Rygu on Friday August 29, 2014 @03:10PM (#8244044)
Past bad decisions stay that's hindsight. In this case not so much the project but technology has become irrelevant. Technology changes every few years or even evey year. Nothing to do about that. Software is difficult.
Re:Yahoo stopping all new development of YUI by apalmer on Friday August 29, 2014 @03:19PM (#8244096)
'Company-backed' is a very nebulous term. If Microsoft was backing Angular I would have every confidence that it would be supported at least for security fixes for the next 10 years even if microsoft had to add a whole compatibility layer on there next 3 OSs to do so. Google backing an open source project on the other hand has a whole different level of support expectations in a 3 year timeframe.
Re:Yahoo stopping all new development of YUI by darkmarmot on Friday August 29, 2014 @08:04PM (#8245088)
just like Silverlight! :)
Re:Yahoo stopping all new development of YUI by apalmer on Friday August 29, 2014 @09:47PM (#8245301)
yeah exactly MS gave up in silverlight however they will continue to provide security fixes for it probably for the next decade
Re:Yahoo stopping all new development of YUI by mythz on Friday August 29, 2014 @02:48PM (#8243890)
> Those micro libraries have a higher abandonment rate than anything..

> Personally I'd go for company-backed projects.

You mean company-backed projects like YUI?

Re:Yahoo stopping all new development of YUI by Rygu on Friday August 29, 2014 @02:58PM (#8243967)
Yes, when it was still relevant and heavily developed. So for a long time now I would've said chosen something else, more relevant to and convenient for modern-day web development.

Of course if you chose YUI a few years ago and you're still using and relying on it, that means it is still serving you well. Was a great past decision ay?

Re:Yahoo stopping all new development of YUI by Igglyboo on Friday August 29, 2014 @02:47PM (#8243883)
Yea but those microframeworks can also easily be replaced or re-written if they are abandoned.
Re:Yahoo stopping all new development of YUI by Rygu on Friday August 29, 2014 @03:07PM (#8244026)
That's true, but most companies need to spend at least some of their time on writing their own code and features too. So we pick third party code that serves us and saves us time.

Analogy if the goal is to go for a smooth car drive, why would you want to stop and be replacing/reinventing wheels every few minutes?

Re:Yahoo stopping all new development of YUI by Igglyboo on Friday August 29, 2014 @03:32PM (#8244167)
Obviously it's not black and white and you'll probably have to do a little of both.
Re:Yahoo stopping all new development of YUI by rubiquity on Friday August 29, 2014 @04:59PM (#8244482)
I've been using Backbone for years without any micro libraries. I only recently started using React with Backbone, which is an awesome pair.
Re:Yahoo stopping all new development of YUI by angersock on Friday August 29, 2014 @02:44PM (#8243863)
At the same time, a lot less is being abandoned--and your team is more likely going to be able to fight bitrot on a small microframework than on a huge thing like Angular.
Re:Yahoo stopping all new development of YUI by Rygu on Friday August 29, 2014 @02:52PM (#8243922)
Not having tons of libraries means that my team doesn't have to fight bitrot regularly though. Also bug reports / PRs are actually handled adequately by the bigger frameworks and their bigger pool of contributors, so code quality, which I find an important aspect of the software I deliver, is very much guaranteed.
Re:Yahoo stopping all new development of YUI by encoderer on Friday August 29, 2014 @03:20PM (#8244101)
I don't see much point fretting about bit rot. That's a murky future problem and there is little to guarantee the code we're writing today will outlive the libraries we're using. Instead what I care about is productivity and my experience as an engineer and engineering manager is that the simple, small, annotated source of libraries like Backbone and Underscore will beat the monolithic uber frameworks 9 times out of 10.

The trouble is that people often use examples of what you can accomplish with a framework if you follow the common path. But we've all been there -- a 20 hour feature where you build 90% of it with heavy framework support in the first 10 hours, then spend the next 10 fighting the framework for whatever it is that you need done differently than the framework prescribes. This blunts that seemingly-huge time save that a framework appears to provide when you watch a 5 minute build-a-blog screencast. So in the end, it comes, as it usually does, to mastery. The guy who has developed mastery over his tools will outperform, and I think it's a lot easier to master these small libraries with accessible source code.