<p dir=ltr> Sam from Google addresses many points to optimize the mobile web. This goes into many directions from compressing to javascript usage. It actually advocates to get more control of the HTML and CSS layer. One argument more for investing in base technologies instead of generated code.
Features ish, a viewport tester to make your apps correctly responsive to various media.
Think about battery APIs.
It wasn't obvious that controlling directly the html/css/js is important?
ReplyDeleteOh well, maybe it's a cultural problem on the java side and their architecture astronauts.
Lets just add another layer over it for solving a problem, I am right?
Don't be so rude with architecture. Everything you use has many many layers, this is a primary concept in software. The thing is to get the appropriate abstractions.
ReplyDeleteI don't want every developer to master CSS optimization, compression, etc. If a good framework provides this for me, I take it and do not reinvent the wheel and do the "low-level" things again by myself.
I don't say that I never need/want to intervene on lower layers, I have coded in assembler and C and I sometimes need to leverage this knowledge but it is more rare because today's abstractions over them are often powerful enough. Which is good, i can then focus on my main goal.