Thomas Fuchs, creator of script.aculo.us, writes about JavaScript, HTML5, CSS and shipping web software.
HN commenters cite it for practical web advice, such as how image dimensions relate to file size and a post on shipping software that works.
I will miss color transform filters…
If it's vector, it can be done with SVG/CSS3
…drop shadow filters…
box-shadow?
…and blur filters
Canvas?
http://www.quasimondo.com/StackBlurForCanvas/StackBlurDemo.html
I will miss masks (of any arbitrary shape)
PNG with alpha?
…rather than having to worry about preloading all of my UI images
Something like this may work:
$("#blob").bind("load", function () {});
or even:
body { display: none; }
<body onLoad="$("body").fadeIn();">
But most of all, I will miss performance. Yeah, Flash is buggy/slow/memory hog blahblahblahblah. But have you tried doing anything graphically complex in HTML5? Holy shit, your processor will scream. Things that Flash used to laugh at will bring Chrome to its knees. Don't get me started with IE.
Not on a Mac. Even a freaking side banner will make the CPU spike. There are a few cases where it is slower, but it's rare and we can all help optimize.
HTML5 is particularly not ready on mobile. For example...don't use gradients, since they kill performance. Oh, and don't use opacity either, since that also kills performance. Seriously? I need to build a UI that doesn't use opacity animations? FFFfffuuuu--
Android or iOS? I'm actually pretty impressed with the hardware accelerated effects I can get in iOS if I don't do much stuff at the same time.
Check this link:
http://mir.aculo.us/2010/06/04/making-an-ipad-html5-app-making-it-really-fast/
I'm also about to publish my first book (about a guy called Elon Musk). Here are some links I've saved that were interesting to read:
Selling my e-book on Amazon (http://snook.ca/archives/writing/selling-ebook-on-amazon)
How you can make a million writing your own e-book (http://www.dailymail.co.uk/home/moslive/article-2040044/Kindle-How-make-million-writing-e-book.html#ixzz2ZDvfiNPB)
How to Write and Promote New York Times Bestsellers: Tim Ferriss and Jack Canfield (http://www.fourhourworkweek.com/blog/2012/09/01/how-to-write-and-promote-new-york-times-bestsellers-tim-ferriss-and-jack-canfield/)
How to (Really) Make $1,000,000 Selling E-Books – Real-World Case Studies (http://www.fourhourworkweek.com/blog/2013/04/04/how-to-make-1000000-selling-e-books-tactics-and-case-studies/)
How I Used Hacker News to Sell My eBook (http://rubysnippets.com/2013/04/26/how-i-used-hacker-news-to-sell-my-ebook/)
An eBook pricing model that resulted in $100,000 in sales (http://blog.asmartbear.com/selling-ebook.html)
5 rules to sell thousands of copies of your ebook (http://mir.aculo.us/2012/10/20/5-rules-to-sell-thousands-of-copies-of-your-ebook/)
Thomas Fuchs is a troll. He has posted before on the alleged complexities of React. Yet, he has never posted a coherent argument against the view framework. Even this attempt was thwarted by Blake Newman:
https://twitter.com/blakenewman/status/811142762368221184
However, Thomas had nothing to say in response. He only patted himself, and others, on the back both before and after that tweet as he continues to ignore any retort to his claims.
Oh. And if you're wondering why he's mad, consider that he's the author of Zepto.js. That jQuery compatible drop-in library that essentially no one uses as jQuery is hardly relevant anymore. But that's fine, he's busy with his own business: Slash7 LLC.
http://slash7.com/company/
Where the overwhelming majority of his client work links are dead and his biggest triumph seems to be an early 2000's era JavaScript animation library on par with Scriptaculous. In fact, the website is even a rip off:
http://scripty2.com/ vs. http://script.aculo.us/
Even his own site uses the same type of vanity domain:
http://mir.aculo.us/
Sad ...
The title and some of the critics are unfortunate but this post nevertheless is hitting a soft spot for me. I've been through backbone & angular and I'm starting to question the necessity of a full blown framework when all I want is some structured js for each page/resource.
More fundamentally it seems the offer on js libraries are either tailored to eye-candy widgets or the big SPA. Nothing has popped in my radar as proposing an incremental step from server side HTML to MV([A–Z]) Dom/json manipulation which entices you to almost build the app twice.
What I'd really like to see rather than a client-side-solution is a server/client migration path from html to spa without being tide to one or the other
The links he included (see below) bring up the same concerns....
http://mir.aculo.us/2013/02/26/client-side-mvc-is-not-a-silver-bullet/
http://www.shopify.com/technology/15646068-rebuilding-the-shopify-admin-improving-developer-productivity-by-deleting-28-000-lines-of-javascript
There's a lot of practical things people can do to make their JS code faster, and a bunch of impractical things too (like unrolling loops). But based on our research/experience, a huge percentage of JavaScript-related web app slowness is actually caused by inefficient DOM structures and CSS styling. Believe it or not, simple DOM mistakes can dramatically slow down insertions, event handlers (like on-click), any kind of iteration (obviously) as well as animations.
That's why we open sourced our DOM performance inspection bookmarklet, DOM Monster:
http://mir.aculo.us/2011/01/09/the-dom-monster-is-now-open-source/
If you liked this presentation, you might enjoy the book I co-wrote with Thomas Fuchs (of Scriptaculous, Prototype.js, Emile, Zepto, & Microjs fame): http://jsrocks.com
We have a native app that is similar in that it makes extensive use of css transforms to animate content on the iPad (Zite, btw. I believe it is smoother and less crashy than the OnSwipe pages I have seen).
The biggest issue we've come across is limiting the total screen area (in pixels) of elements having "-webkit-transform: translate3d(0,0,0);" (this is the declaration you use to force the browser to use 3d acceleration to animate this element). Once it goes beyond a certain size, there isn't enough memory on the iPad to handle it and you get jerky animation and crashes.
This will help:
http://mir.aculo.us/2011/02/08/visualizing-webkits-hardware-acceleration/