lennel

11 ms·

91.
by lennel 14y ago
I think as mobile becomes more dominant angular will have to find a way to work tighter with the closure compiler in advanced mode (or something akin) to remain relevant.
92.
by lennel 14y ago
I honestly just don't agree with this. any templating language you use should work equally well on the client or the server and you should be able to get anywhere. we obviously consider other types of constraints than you do.
93.
by lennel 14y ago
this is bad advice imo. in a good system you should render what people requested and then go from there, if the system does not cater for it then the system is not good enough.
94.
by lennel 14y ago
why not at least at bolin's google io video on building javascript in the large?
95.
by lennel 14y ago
no mention of the closure compiler. pretty insane in my opinion, tis like static analysis and tree shaking is a bad thing.
96.
by lennel 14y ago
Out of curiosity, what kind of protection does the system offer against companies in certain markets patenting against potential innovations in these markets by inventors?
97.
by lennel 14y ago
The HUD makes no sense on a desktop environment and since I have not tried it on a mobile device I cannot make a final judgement. My gut instinct is that the HUD will work on a mobile device and as the platform matures it will become better
98.
by lennel 14y ago
ClojureScript convertes a subset of clojure to google closure javascript which then gets compiled.
99.
by lennel 14y ago
and ParEdit
100.
by lennel 14y ago
Most single page javascript apps that don't prerender are the biggest sinners in a multitude of ways. 1) with the amd loading system you spawn multitude http requests, where 2) none of the code went through a tree shaking to remove dead cod