3 ms·
the shit actually works. Seriously, this is not expected behavior when dealing with html/css/js libraries. People learning html/js/css today have no idea how i
by sillysaurus2 13y ago
the shit actually works. Seriously, this is not expected behavior when dealing with html/css/js libraries.
People learning html/js/css today have no idea how incredible they have it. They don't even have to think about IE compatibility!
I used a lazy evaluation strategy for my life: in 2007 after it became clear to me how ... well, awful ... the webdev technologies were, I switched fields for a few years. And hey, presto, now in 2013 everything works. And works well! I can be a web developer with about 1/3rd of the effort it would've taken me in '07.
EDIT: Actually, after spending a few minutes remembering what those times were like, I'd say nowadays it's a lot more than 3x easier. It's now at least 10x easier to write webapps, if not 30x.
The vast majority of one's time was spent hacking around various unexpected behaviors and incompatibilities.
- james-skemp 13y agoAjax calls ... I remember how painful that was before jQuery. I wonder too if being around before jQuery took the prize has something to do with why I hesitate with new technologies, especially when so many try to fill the same need. Had I not picked jQuery I would have had to rewrite everything in whatever had caught on. So yes, you're absolutely right; they are so lucky to have missed those dreary times.
- crazygringo 13y agoFor sure, certain things have gotten a lot better. Supporting IE8 (still for a bit) is far better than supporting IE6/7. But there are new areas that inspire a kill-me-now reaction. If you've tried to do anything serious with controlling HTML5 audio via JavaScript, for example -- it's a nightmarish maze of different commands and event names and varying functionalities and crashing bugs that vary from browser to browser and version to version.
- deleted 13y ago[deleted]