Live data from Hacker News

I’m too lazy to be a HTML developer

polygeek.com

11–20 of 89 posts

Re: I’m too lazy to be a HTML developer

#11
That's funny. I used to do backend stuff in C# but about 1.5 years ago switched to front-end development. To me it's so much nicer. I really enjoy using JavaScript, even after C# got all that handy functional/dynamic stuff added to it.

Anyway, maybe it's just a shitty tutorial, there are a lot of those out there. Doesn't necessarily say anything about HTML.

Regarding the specific point about breakpoints -- yes, you can set them. That's really not an issue at all. Come on, it's almost 2012.

Re: I’m too lazy to be a HTML developer

#15
post #2

From 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.

Why is using a solid platform not a good plan?

It may be technically solid but still a bad bet. Flex/Air are essentially deadend platforms as Adobe jumps on the HTML5 bandwagon with its toolset. If he puts his effort into developing his Flex/Air skills, he's targeting a shrinking install base and future market for jobs. If he puts it into HTML/JS/CSS instead, he's targeting a large and growing install base, for mobile, browser and Win8 desktop apps.

Re: I’m too lazy to be a HTML developer

#17
Actually, this criticism is true when you use HTML for what it was not intended to do : Make pretty renderings. The core functionality of HTML is to provide hyperlinked data. It does that concisely and efficiently. CSS and DIVs are a mere kludge added on top of a language that is supposed to transmit mainly semantical data.

I really wish xhtml would have won in place of HTML/CSS. This kind of things would have been far more easy

Re: I’m too lazy to be a HTML developer

#18
For me, web development seems like the exact opposite of desktop development.

In desktop development, you learn the underlying foundations first (the programming language, files, networking, graphics, GUIs, etc), then weave them together to build your application. It's slow, but worth it -- often the concepts are universal. How many times do you have to re-learn file IO?

In web development, it's really easy to build the finished application quickly but not understand any of the foundations. Look at how many "rapid development" frameworks there are out there; most of then are fast to install, and the result is usually awesome. And plugins! There are plugins for everything, and they work so well! But the foundations are intimidating -- especially because there are so many layers of abstraction piled on top of each other. Where would you start? The browser DOM? How JavaScript is interpreted? How your database implements transactions? The more web development I do, the more I realize how freakin' tall the stack is...and how little I really know about it. Kind of scary.

Re: I’m too lazy to be a HTML developer

#19
post #17

Actually, this criticism is true when you use HTML for what it was not intended to do : Make pretty renderings. The core functionality of HTML is to provide hyperlinked data. It does that concisely and efficiently. CSS and DIVs are a mere kludge added on top of a language that is supposed to transmit mainly semantical data. I really wish xhtml would have won in place of HTML/CSS. This kind of things would have been f…

I believe that is the first time I have ever seen anyone say XHTML would make something easier. (Just one example: http://mathiasbynens.be/notes/minimal-html )

Re: I’m too lazy to be a HTML developer

#20
post #17

Actually, this criticism is true when you use HTML for what it was not intended to do : Make pretty renderings. The core functionality of HTML is to provide hyperlinked data. It does that concisely and efficiently. CSS and DIVs are a mere kludge added on top of a language that is supposed to transmit mainly semantical data. I really wish xhtml would have won in place of HTML/CSS. This kind of things would have been f…

Same here. I think the return to "do whatever you want and we try to interpret it correctly" was wrong. Code in XHTML is way more readable, maintainable and easier to learn (IMO).

I still write my HTML5 in correct XHTML Syntax.

Post reply on HN