Slashdot Mirror
Yahoo Stops New Development On YUI
First time accepted submitter dnebin writes Yahoo announced that they will cease new development on their javascript framework YUI, bowing to industry trends towards Node.js, Angular, and others. The announcement reads in part: "The consequence of this evolution in web technologies is that large JavaScript libraries, such as YUI, have been receiving less attention from the community. Many developers today look at large JavaScript libraries as walled gardens they don't want to be locked into. As a result, the number of YUI issues and pull requests we've received in the past couple of years has slowly reduced to a trickle. Most core YUI modules do not have active maintainers, relying instead on a slow stream of occasional patches from external contributors. Few reviewers still have the time to ensure that the patches submitted are reviewed quickly and thoroughly."
YUI 2.x was stable and great, and it wasn't until YUI3 when there's a change of leadership. Too many screwups and wannabe with AMD style loading trying to mimick Dojo.
A drastic change of architecture like that with barely compatibility layer surely pissed of a lot of people.
Dumbass wannabe solution architect?
I'm curious how long Microsoft will continue improving Internet Explorer for Windows 7. Microsoft has historically ended development of new IE features once a particular version of Windows goes into extended support. This means Windows Vista is stuck on IE 9, and unless IE 12 comes out before January 2015, Windows 7 will be stuck on IE 11. In any case, even IE 9 supports enough of the W3C DOM that you might not need jQuery or any other monolithic framework in your site's JavaScript. People who can't give up IE might end up having to upgrade from Windows 7 to Windows 8.1 with Classic Shell.
I'm sure someone will point out that jQuery is more of a library and YUI more of a framework, but they solve many of the same problems and people don't usually use both. I imagine jQuery's popularity is one of the reasons for YUI's decline, but no mention of it in the announcement.
az0
Anything? AOL?
If I didn't maintain burner email accounts with them out of sheer inertia, they wouldn't even be on my radar.
'The Economy' is a giant Ponzi scheme whose most pitiable suckers are the youngest among us and the yet-unborn.
So popular in fact, this was the first time I've heard of it.
I have no signature
A million deaths were not enough for YUI.
Silence is a state of mime.
If you maintain an email account, it's not a burner.
lucm, indeed.
UI's define both product and web sites.
For instance, take ESRI's "fabled" ArcGis. Bloated, a labyrinth of confusion and almost un-functional. Compare to ITT's ENVI. Intuitive, simple, elegant.
ESRI get their money through quantum licensing, i.e. turn any javascript code into a module, however obvious, and demand a license for it.
Of course ITT has followed suit to some extent with ENVI and now IDL, but the the hallmark is usability. ESRI is just a Geographic garbage collection.
That the company in charge of creating the library will simply close up shop like an ADHD addled kid, JUST as yahoo did.
Staying away from unreliable short sighted developers makes good sense.
http://dojotoolkit.org/ "Dojo starts with a minimal loader (less than 4KB gzipped) with thousands of loosely coupled lightweight modules and plugins available when you need them that are tested and maintained together for the best quality possible."
A few things I like about it are:
* internationalization
* accessibility
* modules
* support for making your own widgets
The first two (especially the second, accessibility) are examples of really important things that many developers leave for later when you are locked into a framework and discover they are not there.
Example:
"jQuery UI Accessibility Analysis"
https://www.ssbbartgroup.com/b...
"To summarize, the public jQuery UI library widgets as of July 1, 2013, are mostly inaccessible for both screen reader and keyboard only users."
Dojo is used in some IBM projects, so that is probably a big reason for the emphasis on accessibility and internationalization.
Of course, there are various things I don't like about Dojo (to begin with, the documentation leaves a lot to be desired when you are starting out). However, in general, so far, it is supporting us in doing everything we want to do... For example, I was very pleasantly surprised when the back button "just worked" when I used the URL "hash" module to navigate between virtual "pages" in a single page app (at least in FireFox, still need to test elsewhere).
Although I still have a fondness for the brilliance of Knockout.js for hooking up widgets to models...
A 21st century issue: the irony of technologies of abundance in the hands of those still thinking in terms of scarcity.
Almost all of the Flickr webpages are based on YUI.
And the Flickr team just got done the 2nd or 3rd rehash since the May 2013 disaster (when they made the site unuseable for millions of people).
I just wonder how long (if ever) it will take to change Flickr pages over to some new system. And how badly they'll screw it up again.
YUI and Node.js are juxtaposed here, whereas YUI (as far as I knew) was client-side and Node.js is server side javascript.
Never used either (use PHP and pure Javascript), so the confusion may be mine.
Yahoo announced that they will cease new development on their javascript framework YUI, bowing to industry trends towards Node.js, Angular, and others.
That's like when people used to talk vaguely about "talk radio" while somehow studiously omitting Rush L.
Just querying, ya know ...
I was a member of the YUI team until a few months ago. I'm still at Yahoo now, just on a different team, but just wanted to give my own thoughts on this (I don't represent the company or the YUI team).
My software engineering career started with the YUI team - I actually joined as an intern at Yahoo because of a Reddit post on /r/javascript. I was pretty new to engineering in general back then, and as a biology major with no real professional experience, I didn't have an easy time getting internships. Jenny, the manager of the YUI team back then, really took a chance on me, and that really changed my entire career path. I solved a bunch of YUI bugs, added a few features here or there, and I always tried to help other folks on #yui on IRC, the mailing list, or in-person here at Yahoo, which I really enjoyed. I learned a crazy amount of JavaScript, some pretty advanced debugging / performance profiling techniques, and even gave some talks. Eventually, a lot of people always came to me first whenever they had a question about YUI, which was pretty cool.
From the view of some people in the JavaScript community, YUI was always considered a huge, monolithic framework that was only good for widgets. I never thought that was the case - YUI pioneered a lot of the techniques that are popular in advanced JavaScript development today, like modules, dynamic loading, and creating logical view separation in your code. A lot of the influence in RequireJS / CommonJS / ES6 modules can be seen from what YUI did first, which people used to consider "over-engineering".
With a lot of new development in JavaScript though (data-binding, tooling like Grunt / Yeoman, promises and other async handling techniques), it was always hard for YUI to keep up with new features while still being able to maintain backwards compatibility with the constantly deploying products that people were building at Yahoo. We had to support product teams while also building out the framework at the same time, and making sure the user-facing products were the best was more important. Eventually, it was hard when developers who were familiar with newer JavaScript tools tried to use YUI, but ended up having to spend quite some time with the framework just to get it working with the rest of the JS ecosystem.
In the end, I wasn't involved with this decision, but I think it was the right thing to do. A lot of the YUI (now YPT) team and other front-end teams at Yahoo are now working on helping out with more cutting-edge core JavaScript work, like internationalization and ES6 modules, as well as building out components for newer frameworks like React and Ember. Yahoo still has a lot of really strong front-end developers, and working on these more important core components is more beneficial to both Yahoo and the JS community as a whole, than continuing to maintain a framework that's a walled garden.
The one thing to take away from this is that no technology lasts forever, and in the end, what the user sees is the most important, whether it's JavaScript, Android / iOS, or holographic smartwatches.
I'll be a bit melancholy today, but I'll raise a glass to YUI tonight. Cheers to all the folks who worked on YUI, and everyone in the YUI community as well - I made a lot of friends there. RIP.
You better plan to support IE 8 until 2019
Why, when Microsoft itself will stop issuing security updates for IE 8 in January 2016?
You trusted the summary instead of reading the article. It's relatively brief, and it took me less than 10 seconds to roughly grasp the confusion.
Node.js is a very tiny part of the whole explanation.
Fuck it, you're not going to click so here's the relevant bits. I'm assuming Node.js injects script into the pages it creates, meaning those developers don't need script libraries (other than Node.js)
Chrome is is just like IE for more operating systems, no thanks I won't touch the stuff. Rating things on a combination of user security and functionality, Opera is hard to beat with Firefox in a close 2nd. I don't care how fast Chrome can load pages, I don't sit and watch memes flash by all day.
-The wise argue that there are few absolutes, the fool argues that there are no probabilities.
maybe they'll get that shit off flickr, and i dunno, return it to a simpler, faster, easier layout and site ui?
I code all of my javascript entirely from scratch
pussies
Bet on Yahoo supporting YUI for longer than Google is gonna support GWT? Sorry, I tried to tell you.
People still use node.js?
Yeo, I thought he was the doctor that was the traitor in the Atreides camp because the Harkonnens had his wife hostage.
Million dollar+ projects avoid third party libraries and tools for the reason that extra moving parts leads to project breakage/stoppage after 2-3 years.
The first question after 'Is it BSD/MIT equivalent licensed?' is 'Will there be anyone supporting it with meaningful new features after 1.5 years?' Last stable automated nightly build of sources updated long ago are excluded.
Simply, up front purchasing/procurement considerations are being applied to free/OS tools/libraries including the fitness of use verification.
Sounds to me like the kids are bored with last year's toys and have become envious of the cool kids' new toys. Strange, because overall the old toys are still more popular than the new toys.
Maybe they can turn their attention back to some of their existing code. I'm the owner of a Yahoo group that is receiving spam. There is a spam folder but not all of the emails are marked as spam. I can find no way to mark them as spam. Doh!
What about ExtJS? It was forked from YUI and seems to have a large corporate following complete with decent documentation and dual licenses.