|
A look at JavaScript's evolution around an expanding ecosystem of superset languages, libraries and frameworks and the coming impact of ECMAScript 6underlying the browser-centric shift in Web development.
JavaScript today. JavaScript tomorrow. JavaScript forever.
|
|
|
|
|
Use jQuery! 
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
The hackopalypse is upon us.
|
|
|
|
|
Duncan Edwards Jones wrote: The hackopalypse is upon us.
So true! mega-upvotes!!
|
|
|
|
|
Io.js 2.0 makes accommodations for ECMAScript 6 and Google's V8 JavaScript engine
It's a V8 world; we're just living in it.
|
|
|
|
|
Let's go behind the specs and find out everything you need to know about getting Windows 10 running on a PC, but were too afraid (or confused) to ask. The fine-print edition
|
|
|
|
|
How amusing. It says Windows 8 purchase is not available in the country that I'm in. Checked my region settings, and it says "United States". I guess I should have voted Republican last election. 
Marc
|
|
|
|
|
Wouldn't it be better simply to let the public version come out and then try installing it? We will definitely know whether our machine supports it or not!
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
One of the differences between a great programmer and a bad programmer is that a great programmer adds logging and tools that make it easy to debug the program when things fail. Measure twice, code once
|
|
|
|
|
If you’re 40 or older, you’ve probably seen cases where younger developers were picked over older ones. "Age is strictly a case of mind over matter. If you don't mind, it doesn't matter."
|
|
|
|
|
Yep, I left my previous organization because the top managers were running their mouths that they weren't going to promote anyone over 40. They will learn that these kids that know how to copy and paste all of the JQuery tools don't know how to implement a solid solution and it will cost the organization in the long run.
I will say in their defense, there are a lot of "legacy" IT personnel that don't pull their weight. Their problems seems to be a lack of education and resistance to learn new technologies.
|
|
|
|
|
It's not just IT, if your over 40 you are more of a liability in terms of medical issues / insurance everywhere. Also everyone that is clawing their way up the career ladder gets to they're personal top rung and realizes that journey sucked and there is nothing really up here. So it's really hard to buffalo the over 40 crowd into working really long hours and being abused like the younger who haven't found out it may not be worth it.
Don't believe me? just wait till you get here.
Party on.
|
|
|
|
|
Ron Anders wrote: Also everyone that is clawing their way up the career ladder gets to they're personal top rung and realizes that journey sucked and there is nothing really up here. So it's really hard to buffalo the over 40 crowd into working really long hours and being abused like the younger who haven't found out it may not be worth it.
Well said!
Marc
|
|
|
|
|
Ron Anders wrote: Don't believe me? just wait till you get here.
I believe you, and, yes, I'm there age-wise; I have not had a personal experience of "rejection because of age" that I am aware of, and it has been many years since I have "worked" for anyone but myself.
I have, however, fired myself frequently for various causes: usually, laziness, or not showing up.
cheers, Bill
«To kill an error's as good a service, sometimes better than, establishing new truth or fact.» Charles Darwin in "Prospero's Precepts"
|
|
|
|
|
jgakenhe wrote: because the top managers were running their mouths that they weren't going to promote anyone over 40.
Except themselves.
Marc
|
|
|
|
|
Oh no!
It has over 4000 improvements, dropped support to old (IE only) technologies, like ActiveX and VBScript, no more document modes to support older IE anomalies...
So what?!
For those are looking from the developers point of view:
Microsoft Edge has the exact same support for HTML5/CSS3 as IE11 (390 out of 555/45%)...
(So no support for new, but dropping support for old - what we have left?)
I think renaming a product line is just not enough - you should change the brains!!!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Wrong forum? BTW if you're referring to HTML5test[^], the latest version of IE 11 (11.0.18) only scores 348, not 390.
|
|
|
|
|
Maybe wrong forum...I'm not always sure...
My version of IE11 is 11.0.10011.0 - it suns on Windows 10 , build 10074 and scores 390...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I'm far from being a HTML/CSS expert, but along the few months I faced some web programming, I realized the Htlm5Test site (and others similar) are kinda crappy stuffs. Most of the claimed features aren't officially standardized yet, but for some (censored) reason Chrome put them inside itself.
That's a very bad practice, IMHO, from the programming perspective. However, from the browser-war perspective, is the perfect way to kill the enemies...
Happy to hear from who's more involved than me!
|
|
|
|
|
It is true that most test sites are checking for features that are still in pre-recommendation state at W3C, but I do not see it as a problem - W#C works way too slow, and implementing proposed features gives the community a great tool to provide feedback...
As for IE11/Edge, you should look for the unsupported features that ARE in recommendation state!
Or for the open-source video/audio formats that Microsoft refuses to support!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
The "too slow" is a relative assert: someone states "too slow" when he/she wants to beat the concurrency, even paying a lot more after in terms of not-standardization.
There were tons of examples in the past where the ability to push a product than another leaded to a mediocre/obsolete product...I'd call it as "speculation", not good practice.
Pardon my words, but I'm working for a very small lab where the quality is very important and there's no rooms for speculation: either we perform a good product, or we'll die.
Thank you for your answer.
|
|
|
|
|
I agree with you about pushing-to-hard (speculations you called it?) but in the case of W3C it took 15 years to update HTML - I think it is still too slow...
In the case of Microsoft - I'm talking about HTML5 features that ARE recommended, but still not getting Microsoft's attention...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Mario Vernari wrote: I realized the Htlm5Test site (and others similar) are kinda crappy stuffs. Most of the claimed features aren't officially standardized yet, but for some (censored) reason Chrome put them inside itself. That's a very bad practice,
I totally agree. 
You have just been Sharapova'd.
|
|
|
|
|
And as a pointed out somewhere else a few days ago; about 2 years ago Google and Mozilla both realized that prefixed feature implementations were creating a cluster-elephant across the web and stopped doing so for new development. Instead anything new is hidden behind a setting flag that must be explicitly turned on by the user.
HTML5Test isn't loading right for me ATM; but IIRC it does call out the handful of cases where FF/Chome/Etc are still relying on prefixes for something they launched experimentally years ago and never standardized; but that's a small fraction of what IE is getting crushed on.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Dan Neely wrote: HTML5Test isn't loading right for me ATM; but IIRC it does call out the handful of cases where FF/Chome/Etc are still relying on prefixes for something they launched experimentally years ago and never standardized; but that's a small fraction of what IE is getting crushed on.
It finally started loading correctly for me again. It took the highest scoring Edge build I saw in the search tab and compared[^] it with Chrome 39. Chrome is a net 99 points ahead. Of those a net 81 came from categories that weren't marked with prefixes; meaning Chrome has a fully standard compliant implementation but Edge doesn't. The full total is likely a bit worse, since in the categories where there were a few prefixes Chrome generally also lead on non-prefix items. But not knowing what the scoring breakout was I didn't count any of that toward the 81. I did the same with FF35: FF has a net edge of 47 points, net 32 for non-prefixed implementations. This comparison was more interesting because there were more cases where Edge either had more points, a different subset implemented, or in two cases had a standard compliant implementation for something FF only had as a prefix.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
