Thank you Douglas for possibly the single most important software book I ever read! Not only did it teach me functional programming, it also showed me that a language (any language) can have good parts and bad parts.
Who's your daddy...Crockford's your daddy! But seriously, thanks to his book and vids I "opened up" to JavaScript a few years ago and haven't looked back! Always love his presentations; nice!
Well, here we are, 14ish years after this was filmed. JS is still going strong. es6 takes care of a lot of the bad parts, and TypeScript is a pretty good piece of tooling.
Here is a variant of aspects to solve the mashup problem. The building block is a component, and components are composed in packages. There is a notion of A being a subcomponent of B. One package may incorporate a parameterization of another. A package may declare an equality between two components. Syntax: "A for B" A is a subcomponent of B "A is B" A is the same component as B The algorithm for mashups is: If (A for B) is (C for D), first mash B with D If (A for B) is (C for B)... If (A for B) is abstract, set (A for B) = (C for B) If (A for B) and (C for B) are both concrete, mash A with C The definition of "mash" can be different for each type of component. E.g. it could mean, "take the union of the members." Packages can also be forced to obey additional properties, which the weaver must prove in order to complete a solution to a mashup.
Usually the msb is the sign bit. So if adding 0xx..xx to 0xx..xx overflows into the sign bit, the result.is negative unless the overflow is caught as an error.
Mashups are nothing new - they're a lesson that Unix taught us, the lesson that mashups are good and that dumb utilities working together can be very clever indeed.
Links: On the Criteria To Be Used in Decomposing Systems into Modules www.cs.umd.edu/class/spring2003/cmsc838p/Design/criteria.pdf The Lazy Programmer's Guide to Secure Computing The Lazy Programmer's Guide to Secure Computing
He says Threads are evil. I can mostly agree. However, if I have multicore machine and cannot create new threads through tasks how I will get benefit out of it? Will javascript use only single core forever?
i love how crockford says microsoft was blindsided by ajax after disbanding its web team after forrester's 2000 declaration, when in reality, microsoft's web team is who created ajax in 1999
+popasmuerf okay, name a company that you can't name dead initiatives from, and you just named a company that never took any initiatives. ooh, anti-microsoft hate. that's novel. i'll see you on slashdot
Microsoft was also the driving force in developing and promulgating XML. Further, it was IE's creation of a JavaScript XML document request that made AJAX possible. Other browsers adopted it before it was ever formalized as a standard, but they all copied the IE implementation. Don't mistake a marketing emphasis for their entire development. Much of what's gone wrong in the WWW is their fault, too, but give them their due. Microsoft is the single entity most responsible for AJAX. More so, even, than the W3C.
_new ActiveXObject("Microsoft.XMLHTTP")_ - ah, the good old days... see also: blogs.msdn.com/b/xmlteam/archive/2006/10/23/using-the-right-version-of-msxml-in-internet-explorer.aspx
I like everything he said except the one Java comment about bytecode. JVM startup time is slow, but not because of the intermediate bytecode. That's just silly.
Ioan190 Think jQuery. Back in 2009/2010, when this talk was given, there were a number of competing libraries with no clear "winner" in sight. These days, just about everybody uses jQuery (as opposed to things like YUI or raw Prototype). The selectors and searches and so forth in all of the AJAX libraries made more syntactic sense than the native versions (either MSIE, the W3C DOM interface or the old Netscape Navigator methods); the problem is that you need to force a download of something like jQuery to make a two-line call easier on a 10KiB page, and that's ridiculous. A native standard DOM API that looks something like jQuery would make pages a lot lighter. (People will tell you that cache handles it; sites all use different jQuery versions with different plugins and most users will only visit one page or a small number of pages on a site, so there really is no net download savings.)
I think that whoever is using IE as of today is disrespecting and spitting on the work of web developers. You can't do that damage to thousands of devs only because you don't give a damn fuck about installing a new browser (which actually takes one click and one minute) and be considered a nice person. Im sorry but if we don't stop supporting IE lazy people won't change browser ever. I am telling this from 2017 and IE is still lurking out there. Oh and FFS uninstall whatever windows
Efreitor Habibulin I learned this the hard way as meny before me :P. I was far too locked up thinking in the same way as i would if I was writing Java, C++ or C#. There is an unessesary amount of mindfucks in the language though. Getting OK att js was painfull to me, I like it a lot now but it took some time.
I disagree with the supporting IE6 comment Doug makes in this video. Unless you are targeting China there is no need to support that browser. And the reason so many people in China are still using IE6 is because they are also using older, more easily pirated versions of Windows. If you are selling a product it probably won't be these people purchasing it. developer.microsoft.com/en-us/microsoft-edge/ie6countdown/
Well IE is also gradually becoming obsolete. The current most popular browser in China is built based on Chrome (though many people just don't know) IE is used now usually due to legacy programs targeting the browser (and, occasionally, since it is the browser comes along with their pirated Windows XP. Seriously, XP)
Oh dear. I hate JavaScript because it is not type safe. It is a write-once language. Not even in his list. IE6 must die!? Well I have an old XP computer running an old version of IE. It runs fine and I'm no upgrading it so this chap can satisfy his wish list. "Like another language, then go program in it." - Well no, JavaScript has a monopoly. I cant. Java failed because the libraries were so huge. I remember trying to download an app and being told it would take 3 hours to download with the new libraries it needed. Very disconcerting that this chap is so out of touch with the real world.
Freddy Falcon Even Microsoft went to the "IE6 must die" route. They even had a web page to educate people that 12% of the web using IE6 was too much. Here is that page from over 4 years ago: web.archive.org/web/20110307020932/www.ie6countdown.com/ . Today, there are less than 1% of users who -- like you -- are still using IE6: www.modern.ie/en-us/ie6countdown
