Saturday, 31 January 2015

Earlier I started the idea of learning the Durandal framework that Rob Eisenberg wrote.  Then last year he was brought onto the Google team for writing Angular 2.0 - and Rob gave the presentation at the ng-europe conference on the Routing framework - that was usable for both Angular 1.3 and Angular 2.0.


Rob Eisenbergs work on the Angular team gave me hope that the merger of Durandal and Angular had to be the best of the best working together. However shortly after that  ng-europe conference - Rob left the Angular team - and it seemed like nothing was going on -his lack of community presence was noticable - in fact the evening of Jan 26, 2015 - I was speaking to the .Net user group leader about volunteering to speak on a topic - maybe Durandal and Angular. We discussed that Robs lack of postings was odd - which turned out to be the same day that Rob Eisenberg posted his announcement of a new framework being available - Aurelia.


I have now picked this framework to study - and do a presentation on for the user group.  There are similarities to Durandal - which should be expected.


Aurelia is expecting the browser to support ES6 as the new ES6 classes form some of the basis of the architecture of this new framework - what Rob sees as the "direction of the web" - that he mentioned in his post of leaving the Angular team - he did not agree with their direction now.  Today - on the CanIUse site - that might limit the browsers to Chrome, Firefox, Opera - they are about 85-90% implemented in those browsers - I have not seen any numbers on the new Spartan browser for Windows 10.  (The leader of the local JavaScript user group made the statement that Firefox was the most compliant overall browser - it may refer to


I learned of Rob Eisenberg at the 2013 Orlando code camp - and have tried to follow what he is up to since - I consider him one of the best JavaScript developers I am aware of - and one to certainly learn from.


In order to learn - you have to teach - and doing a presentation will put me into that position - where you will retain 80% of what you learned - in order to teach the subject. That would be a win-win for me.  I am excited to get started.

Saturday, 31 January 2015 14:08:44 (Eastern Standard Time, UTC-05:00)
 Sunday, 25 January 2015
I was catching up on my podcasts and on HerdingCode -  heard Scott Koon say that Rob Eisenberg left the angular team - apparently back in November just after the NG conf post. Here is Rob Eisenbergs blog entry on his thoughts about it. The Herding code group talked about the way that Angular changes have really upset the prior users of the framework - and then hearing about Rob Eisenbergs leaving the team - felt like the right thing for him to do - not where he wanted to take the web.

So I may be renewing my efforts to dig into how Rob is going forward with his framework - he has a great standard of development and is extremely bright developer.

Podcasts are  a great way to catch up on the community when you have been doing other things that dont allow you to keep up directly.

Sunday, 25 January 2015 23:12:16 (Eastern Standard Time, UTC-05:00)
 Friday, 08 August 2014

I just listened to the JavaScript Jabber Podcast episode 115 with Guy Bedford.

This was an interesting podcast for me. It felt like I was hearing from someone who was working on the future design aspects of the browser environment and JavaScript language features we may find commonplace in 5 years. The spec process that determines all this is quite slow and in that line Guy Bedford mentioned the date of the
ECMAScript 6 (ES6) spec completion has now been moved into next year.

The tools that have been built  to validate the concepts of the spec, have impacted the way the spec is written - by seeing what works and what does not work - and corresponding changes get made based on testing of the concepts being proposed in the spec. The discussion also highlighted that the hooks that are built into the browser is going to be a different spec based on the completed ECMAScript 6 spec.

Guy Bedford has been working on some open source libraries to manage the modularity of JavaScript, which was the topic of my last post. ES6 will have modules; today there have been two competing formats - AMD and CommonJS.
The Projects that Guy has worked on build upon one another:

The SystemJS will load any of 3 styles of modules (ES6,AMD,CommonJS) which is designed to work with the ES6 Module Loader - and make them work together.

JSPM - a JavaScript Package manager built on SystemJS. (It sounded like you could load NPM modules with this too)

Inside of the SystemJS they provide a build process for production systems that will make the modules CSP-Compliant (Content Security Policy) so that the systems are less vulnerable to attacks.

There are Transpilers involved in getting the ES6 testing done here and may even work down to IE8.

The architecture of these ideas feels like a good direction. One of the comments in the podcast is that it will have to become more complicated before it becomes more simple. These ideas are being transpiled(Translating ES6 source to ES5 source), and not built into the browsers yet - but the browsers are changing so fast now that we may see these features in the next few years in all the browsers - which will also mean that most browsers(if not all) will be "evergreen" - self updating.

It has also become obvious that Node has become one tool that every web developer must learn.

Friday, 08 August 2014 05:17:36 (Eastern Standard Time, UTC-05:00)
 Monday, 26 May 2014
One of the talks that I attended at TechEd 2014 was on TypeScript and managing a Large JavaScript code base.
The developer speaking works for Microsoft on the "Monaco" project - that was converted to using Typescript for programmer safety - when the code base exceeded 100K LOC.  This is where TypeScript has a sweet spot - to give you the modularity from the intellisense and programming structures within Visual Studio.

I still agree that developers should know and understand the JavaScript language first before learning TypeScript - as you should know your language - and be able to explain the output that TypeScript is using.

Typescript can output the modularity as AMD or CommonJS (which is more prevalent with NodeJS).

Just as developers should know the language of JavaScript - understanding the basis of the Modularity and what ES6 is planning is very fundamental to having a broad basis of what your application is doing and why.

Addy Osamani's writeup on Modularity is a good start to that - and I would recommend it to developers needing to round out their understanding of JavaScript modularity concepts.

Monday, 26 May 2014 22:29:18 (Eastern Standard Time, UTC-05:00)
 Saturday, 19 April 2014

In looking over my twitter feed a few days ago - I saw the tweet by Rob Eisenberg  and read his post that Angular and Durandal will converge and he is working with Google to develop AngularJS version 2.0 - he did write a post on the angular website too.

Durandal 2.x will be supported and is not going away - however Rob's energy is going to the new version. The post he wrote explains how this came about and how these two projects converging will actually benefit developers by putting together some incredible minds in melding together two of the more impressive frameworks that I have looked at over last couple of years.

I just wonder how the AngularJS Manning MEAP book I ordered - due in the Fall - will handle this news - and hope that they change the basis of the book to be AngularJS version 2 - instead of the current version 1.

The learning that I have been doing with Durandal will still be good - which you can understand in reading his posts.

The learning that I have been doing will still be valuable. It sounds like the improvements to Angular with Rob Eisenberg working with them will be a nice team to create a great framework. I look forward to learning the result.

Friday, 18 April 2014 23:08:09 (Eastern Standard Time, UTC-05:00)
 Tuesday, 25 February 2014

The last month has been very busy. So, unfortunately I have not been able to do much research on BootStrap as I would have liked. Bootstrap is a good framework for getting workable HTML with CSS for a set of controls for a web UI that is very usable. The risk is that you could have a broken UI if they change the tags and CSS, on a later version. An advantage of using this framework is that you have a good basis to start from; you could bring in a true designer to re-skin your website/application by just updating the CSS.

Bootstrap as a combination of JavaScript, HTML with classes for CSS to style makes for a very powerful basic site.

CSS can be challenging and the use of a basic framework for a layout can be a time saver.

I hope to get some time to look into the use of FontAwesome and Bootstrap together.

Tuesday, 25 February 2014 22:44:47 (Eastern Standard Time, UTC-05:00)
 Tuesday, 14 January 2014
DurandalJS JavaScript Framework for Learning in 2014 - is a first post for 2014. I hope to use the framework for learning more about JavaScript, and Single-Page-Application approaches, and tools around the JavaScript community that are also used in the framework. JavaScript application Architecture, use of BootStrap, and Fontawesome, some NodeJS, and even some TypeScript - while using RequireJS, KnockoutJS, and jQuery. Overall it should be a good learning tool to exercise some tools that I have not experimented with. This post is how I came to decide on this framework.
Tuesday, 14 January 2014 18:12:55 (Eastern Standard Time, UTC-05:00)
 Wednesday, 17 August 2011
Firefox 6 came out during the last week. I then see a few tools that highlight using JavaScript to process what you would expect from something in native code via a plugin.
An MP3 decoder written within JavaScript

A PDF viewer written in Javascript - with footnotes, color, diagrams.

This ties back to the Hanselman interview with Erik Meijer -where he refers to JavaScript as the Assembly language of the web. The low level code that other tools are beginning to compile to -example Script# and other tools - that Hanselman followed up with in additional episodes.

All this makes me wonder what is coming in Windows 8. (maybe this is why the Build Conference sold out months ahead of the event?)

However - the MP3 player link above works in Firefox and not in IE9. So there is more work to be done in the browser area, but the efforts in this area of late are really noticeable. (IE8, IE9, beta of IE10 - Firefox 4, 5 and 6 were not that far apart .. maybe too close together for some). The rapid changes to the Google Chrome browser. This increasing pace and direction of standards in the browsers is interesting, and when tied to mobile phones, and tablets as the new devices, becomes more interesting and intriguing as to where computing in general is moving. Virtualization of computing resources, cloud integration, with those hardware changes,makes for a very dynamic landscape for the 2nd decade of the 21st century.

That dynamic element, for the computing world - in this decade, assumes the world economies can stay afloat...the force that will determine acceleration, or collapse at this point.

Wednesday, 17 August 2011 21:48:55 (Eastern Standard Time, UTC-05:00)
 Tuesday, 23 December 2008

I saw an article about Qooxdoo (pronounced like "cooks-doo") on the Ajaxian website this evening. A JavaScript Framework that has apparently been in develoment since 2005.

The Qooxdoo framework is open source, and has some RPC hooks for Java,Perl, and PHP from what I saw. I am posting this as a note to go look into that a bit more later on.  They make a point that this is not a Javascript Library - like jQuery or prototype it is a Framework.

There is a PlayGround that the article mentioned - so you can play around with the Javascript API.

More interesting software to look at.

Tuesday, 23 December 2008 18:11:17 (Eastern Standard Time, UTC-05:00)