Echo JS 0.11.0

<~>

TheSisb comments

TheSisb 3691 days ago. link 3 points
I really have to say that I really agree with:
"Right now, people comment when they *really* have something to say, and I think is better this way."
TheSisb 3697 days ago. link 1 point
This is really well designed, like it a lot.  Tried using it with a co-worker but it didn't notify either one of us when we tried to initialize a transfer.  Not sure if the port (?) was blocked on the work network or something else.
TheSisb 3850 days ago. link 1 point
A world where anything becomes the new IE is a scary thought.  It seems that the "new IE" will always be the browser lagging furthest behind the competition in terms of state-of-the-art technology features.  In this case, the examples of window.performance, WebGL, and SPDY are used.  All three of those technologies are indeed wonderful, but so few people use them that I can see why they'd be on the low priority list.
TheSisb 3850 days ago. link 2 points
This is great.  I've been looking for an angular tutorial that leads you through the process of building an application.  I learn by doing and the angular tutorial on the official website has way too many 404 links to keep my interest level high.  Please continue!
TheSisb 3851 days ago. link 1 point
I really liked your choice of examples and how they progressed.  Great article.
TheSisb 3852 days ago. link 5 points
I work on an Enterprise grade application that uses makefiles extensively.  We recently rolled Grunt into the loop for the development process because of grunt-watch.  If you have many js files and you're working on the front-end, your process goes something like this:
1- Type code and save
2- Alt tab to the cygwyn / terminal
3- [up > enter] to send "make" again
4- Wait for n seconds, where n scales based on your code size (really long wait times)
5- alt tab to browser and test
6- repeat.

Grunt-watch can automatically detect modified files in folders and run operations on them.  Process then becomes:
1- type code and save
2- alt tab to browser and test

You might be thinking this process is just as slow because no part of what I've described solves the long compile process.  The secret to it is that make simply does a bulk operation, whereas with a watcher knows which file was modified.  We have the compressed version of each file individually resting in another folder and only update newly modified files into that folder. Whenever update happens, all we need to do is concat the prebuilt files with the new file and that process only takes milliseconds.
[comment deleted]
TheSisb 4057 days ago. link 1 point
I like seeing these kinds of stances.  I wish Firefox OS the best of luck.
[more]