I’m too lazy to be a HTML developer
polygeek.com
I’m too lazy to be a HTML developer
1–10 of 89 posts
Re: I’m too lazy to be a HTML developer
#2Not a good plan; then again, not a good general attitude from a technologist.
Re: I’m too lazy to be a HTML developer
#3This question has always bugged me.
Re: I’m too lazy to be a HTML developer
#4It has been so pleasurable to not have to worry about HTML / JS - if I want a dialog box, I can have one very simply with no messing about.
Re: I’m too lazy to be a HTML developer
#5From the article: "Flex/Air seem pretty solid [work venues] for the next three or four years at least." Not a good plan; then again, not a good general attitude from a technologist.
Re: I’m too lazy to be a HTML developer
#6off topic: Which is correct grammar -- "an HTML" or "a HTML" ? This question has always bugged me.
Re: I’m too lazy to be a HTML developer
#7As for HTML and CSS, I agree that they're difficult to debug and that it takes a lot of experimentation to become comfortable with. Developer tools like Firebug and those included with Chrome can take a bit of the mystery out of HTML and CSS.
Since breakpoints don't exactly make sense to apply to markup and style sheet languages, I'll assume the author was complaining about the lack of breakpoints in JavaScript. In fact, you can use breakpoints in Firebug.
When the author talks about the apparent complexity of various languages and platforms, he should know that this is entirely subjective. I've been goofing around with HTML/CSS/JS since I was very young, so by this point most lightbox tutorials and similar articles look fairly simple to me. Step 2 in the tutorial he mentions looks quite simple to me. The only things that I suspect would be confusing to a newcomer would be the weird vendor prefixes.
Re: I’m too lazy to be a HTML developer
#8When I was ten I thought HTML was too complicated because I tried to read a tutorial in one go, then make a website. Turns out you can't do that.