Comments on: WSG London Meetup http://wildfalcon.com/archives/2006/07/16/wsg-london-meetup-2/ Thinking and developing in everything - by Laurie Young Sat, 17 Jul 2010 13:42:45 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Laurie http://wildfalcon.com/archives/2006/07/16/wsg-london-meetup-2/comment-page-1/#comment-3755 Laurie Thu, 21 Sep 2006 14:45:47 +0000 http://blog.wildfalcon.com/archives/2006/07/16/wsg-london-meetup-2/#comment-3755 Then you would have very strange conversations about the difference between java, which supports dynamic typing and closures, and java, which does not. Then you would have very strange conversations about the difference between java, which supports dynamic typing and closures, and java, which does not.

]]> By: Bryan http://wildfalcon.com/archives/2006/07/16/wsg-london-meetup-2/comment-page-1/#comment-3750 Bryan Tue, 19 Sep 2006 23:58:59 +0000 http://blog.wildfalcon.com/archives/2006/07/16/wsg-london-meetup-2/#comment-3750 OO javascript could be called, oh I don't know, Java? Bryan OO javascript could be called, oh I don’t know, Java?

Bryan

]]> By: Laurie http://wildfalcon.com/archives/2006/07/16/wsg-london-meetup-2/comment-page-1/#comment-3407 Laurie Mon, 17 Jul 2006 09:30:53 +0000 http://blog.wildfalcon.com/archives/2006/07/16/wsg-london-meetup-2/#comment-3407 Hi Chris, good to know that my site is turning up in the search engines :-) Your comment about not dwelling on the OO aspects because of the mix of the audience made me realise that its probably true that while many of the things you were saying are not new, they are not necessarily accepted by everyone who uses JS. This is for a couple of reasons I guess. Some JS developers are not computer scientists in the traditional sense, so they might be new ideas for them. And JS has often been seen as a bit of a languages to do hacks in, so many people who know better don't bother to spend the time for good coding. PS i have now also linked the main post to your slides Hi Chris, good to know that my site is turning up in the search engines :-)

Your comment about not dwelling on the OO aspects because of the mix of the audience made me realise that its probably true that while many of the things you were saying are not new, they are not necessarily accepted by everyone who uses JS. This is for a couple of reasons I guess. Some JS developers are not computer scientists in the traditional sense, so they might be new ideas for them. And JS has often been seen as a bit of a languages to do hacks in, so many people who know better don’t bother to spend the time for good coding.

PS i have now also linked the main post to your slides

]]> By: Chris Heilmann http://wildfalcon.com/archives/2006/07/16/wsg-london-meetup-2/comment-page-1/#comment-3403 Chris Heilmann Mon, 17 Jul 2006 06:34:07 +0000 http://blog.wildfalcon.com/archives/2006/07/16/wsg-london-meetup-2/#comment-3403 HI Laurie, good that you enjoyed the meeting. As to your comment: Yes, none of this is nothing new and they are best practices of old programming languages. It was not my idea to invent something new, the idea is to remind ourselves of these steps instead of following down the same whizz-bang path we've trod in the DHTML boom days. Right now we have JavaScript/Ajax rather nailed, and it is time to get some code quality and interoperability ideas in instead of just achieving the same task with 12 different libraries. As to the OO question: I didn't want to dwell on it too long as it is a complex dilemma (and I said so) and the mix of the audience would have meant half of the hall would have tried hard not to fall asleep as it would go well over their heads. It is a discussion for a more JS centric meeting or mailing list. The DOM scripting Task Force of the WaSP is starting a mailing list soon that is dedicated to "modern" JS and this will be a good place to get real results rather than just the view of one guy on a stage. HI Laurie,

good that you enjoyed the meeting. As to your comment: Yes, none of this is nothing new and they are best practices of old programming languages. It was not my idea to invent something new, the idea is to remind ourselves of these steps instead of following down the same whizz-bang path we’ve trod in the DHTML boom days.

Right now we have JavaScript/Ajax rather nailed, and it is time to get some code quality and interoperability ideas in instead of just achieving the same task with 12 different libraries.

As to the OO question: I didn’t want to dwell on it too long as it is a complex dilemma (and I said so) and the mix of the audience would have meant half of the hall would have tried hard not to fall asleep as it would go well over their heads. It is a discussion for a more JS centric meeting or mailing list.

The DOM scripting Task Force of the WaSP is starting a mailing list soon that is dedicated to “modern” JS and this will be a good place to get real results rather than just the view of one guy on a stage.

]]>