3 ms·
I've been doing this for 15 years and it sucks more and more. Now we have complex as hell client-side frameworks like Angular. A framework on top of my framewor
by eldelshell 12y ago
I've been doing this for 15 years and it sucks more and more. Now we have complex as hell client-side frameworks like Angular. A framework on top of my framework, great! More and more screen sizes/devices/browsers, but not a freaking way of handling any of this information because, for some stupid reason, the User-Agent header is useless. CSS media queries are useless. JavaScript window.size is useless.
The problem is: HTML is not made for applications, it's made for documents, linked documents. The day someone put a form in HTML hell broke loose and even after 20 years, the web is seriously broken and things are just getting worst. For example, date input fields; supported by Chrome and Safari, but not by Firefox. You want to localize it? IT SUCKS! I thought Java's Calendar was crap, but JavaScript's Date is pure mayhem... And I could go on and on about why HTML/CSS/JS is all a bunch of crap which, instead of evolving, are making things harder.
And now they want to add Future/Promise to JavaScript... HAHAHAHA!!!