Don't sugarcoat your failures to 'lazy'. You do yourself no favours.
I’m too lazy to be a HTML developer
61–70 of 89 posts
Re: I’m too lazy to be a HTML developer
#62I panicked about 2 years ago, thought the web was the only future. Quit my job and became a web programmer. Lasted 9 months, absolutely hated it. Dealing with multiple browsers, guess and check methodology drove me nuts. I lasted 9 months and quit before I was fired.
I'm back to doing firmware and control software now. Much happier. It's all about what you know and how it fits your style of working.
Re: I’m too lazy to be a HTML developer
#63I'm really surprised to read this article. For all the frameworks out there, I would think the barriers to learning HTML couldn't be any lower right now.
I actually had a conversation with our team at my company about this very problem. The idea was there are SO many frameworks, it already has become a crutch for developers. It takes the thinking out of coding for you. Then what happens when you need to build something from scratch? You'll be totally lost.
IMHO, This person is on another level of lazy.
Re: I’m too lazy to be a HTML developer
#64CSS is a declarative language, not an imperative language, so there is no concept of a breakpoint in CSS, because there is no concept of one thing occurring before another. There is a chain of inheritance of course, but Firebug will show you that. A web browser + Firebug/Web Inspector is effectively a giant REPL, what more could you want?
The order of evaluation matters. If the browser finds 2 declarations that are in conflict, then only the last one is taken into account. And that's not inheritance.
The order in which declarations are written does indeed matter, but that's not the same as evaluation. If I assign some color attribute to black, then red, then black, the color in the DOM will never actually be red, so itsnstill meaningless to talk about a breakpoint.
Re: I’m too lazy to be a HTML developer
#65Earlier quoted context omitted.
The order of evaluation matters. If the browser finds 2 declarations that are in conflict, then only the last one is taken into account. And that's not inheritance.
There is more to it than just that. For example you can have a class and an id for a div. The id attributes will overwrite the class ones. And some other fun rules too!
That's inheritance.
Re: I’m too lazy to be a HTML developer
#66Stop conflating your non-understanding of something with inherent difficulty. You might find the code (defmacro unless (cond &body res) `(if (not ,cond) ,@rest)) rather opaque; but it's actually pretty darn simple. You might find body { width: 800px; position: relative; left: 50%; margin-left: -400px; } impossible to pull out of one's ass; it's not, you're just unused to negative margins. To you, TeX macros or M4 or…
You've also got to make a distinction between necessary and accidental complexity. That example would be better written as: body { width: 800px; margin: auto; } (This also has the benefit that the left hand side of the body does not disappear off the side of the screen in small browser windows.) There's a similar problem with the css in the article he links to - it is more complicated than it needs to be, which just…
Negative margin as used in pavpanchekha's example centers the box also in browsers that do not support margin:auto. It's not complex if you know why it's done that way.
Re: I’m too lazy to be a HTML developer
#67Earlier quoted context omitted.
You've also got to make a distinction between necessary and accidental complexity. That example would be better written as: body { width: 800px; margin: auto; } (This also has the benefit that the left hand side of the body does not disappear off the side of the screen in small browser windows.) There's a similar problem with the css in the article he links to - it is more complicated than it needs to be, which just…
Negative margin as used in pavpanchekha's example centers the box also in browsers that do not support margin:auto. It's not complex if you know why it's done that way.
The latest browser which doesn't support margin:auto is IE5.5, and even there the text-align:center hack is a better option. There are cases where you might want to use negative margins, but for horizontally centering block level elements, it is at best outdated.
Re: I’m too lazy to be a HTML developer
#68HTML is so simple it's retarded, you just have tags and attributes.
CSS is making it interesting & I can understand you find javascript not easy, but HTML, really?
No offence, my little sister also doesn't understand HTML, but then again, I don't see a blog post written by my little sister on HN.
Re: I’m too lazy to be a HTML developer
#69Did it bother anyone else that he didn't use 'an' in the title?
Re: I’m too lazy to be a HTML developer
#70HTML is so simple it's retarded, you just have tags and attributes. CSS is making it interesting & I can understand you find javascript not easy, but HTML, really? No offence, my little sister also doesn't understand HTML, but then again, I don't see a blog post written by my little sister on HN.
The idea of an XML document is pretty goddamn easy. The basic tags of HTML are a breeze.
The way html, css and js interact with eachother are a fucking kludge. The only way it makes any sense is with the understanding that css and js are tacked-on technologies that have influenced the evolution of all of them for a while now.
If we were to recreate the language(s) of the web from scratch at square one now, knowing what we know now about what we want from it, but without our minds being influenced by the tech structures that we do have, it would be a completely different beast.
We're still stuffing applications into a document format, when I build for the web I feel the pain of design decisions meant to conform with the realities of what came before.