-
Not enough

-
@blowdart: what did you expect, ritual suicide?

-
31 minutes ago, Blue Ink wrote
@blowdart: what did you expect, ritual suicide?

Probably still not enough

-
1 hour ago, Blue Ink wrote
@blowdart: what did you expect, ritual suicide?

I should make a joke about closures here ....
-
Interesting video. I think Eich gives up too quickly on the standard bytecode for the web idea. Google expressed a lot of desire for doing stuff like that, and I wouldn't be surprised if Microsoft was open to the idea too. And regarding the IPR issues, I think the idea of bytecode is old enough that there won't be any IPR issues, and even so, if it was something big like a redesign of the web it might even be possible for the US government and other governments to indemnify new web technology from submarine IPR issues (I know the POTUS has this power, anyway).
-
About a year ago, I really hated working with javascript. After a while, you learn to stay away from the bad parts. Unfortunately, you have to deal with code that you wrote prior to learning about the bad parts. It takes a lot of time to master promises, but they make life easier down the road.
-Josh
-
4 hours ago, Blue Ink wrote
@blowdart: what did you expect, ritual suicide?

"Seppuku" sounds like cool name for a programming language, especially for one like JavaScript.
-
2 hours ago, JoshRoss wrote
About a year ago, I really hated working with javascript. After a while, you learn to stay away from the bad parts. Unfortunately, you have to deal with code that you wrote prior to learning about the bad parts. It takes a lot of time to master promises, but they make life easier down the road.
-Josh

-
I've been force-feeding JS into my brain for the last few weeks, and I started with 'the good parts'. It was kind of sad how much of the good parts also came with warnings about how they could be abused easily.
So far "JavaScript Patterns", also from O'Reilly, seems to be illuminating some promises of code that doesn't completely suck.
I'd still rather just code in C#/.Net.
My suspicion is that the reason JS code is so reviled is that there isn't a robust framework, so wheels get reinvented again and again...each one more clever than the last.
I f*cking hate clever.
-
The JS "limitation" I fall for most often - lack of block-level scoping.
I'll be interested how that gets implemented into the next version, and not "break the web".
-
Microsoft needs to showcase apps like these if they want to convince people that HTML5 + JavaScript can really be used to create rich user experiences for Metro.
http://www.theverge.com/2012/5/16/3022699/tizen-developer-conference-HTML5-galaxy-S-II-HD-LTE
The response to gestures in the first demo was pretty impressive, but in the second demo you could clearly see a lag between gesture and the response on the screen.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.