Hacker News Reader

Comment by paulddraper | Hacker News Reader

Funnily enough, I did all that.

And it made me want to claw my eyes out.

Browser idiosyncrasies, horrendous security vulnerabilities, the blood sacrifices to do basic things with CSS, trying to debug in IE, the daily “maybe Flash isn’t that bad” introspection.

There are many good things about this world.

2005 web dev is not among them.

View on HN

There really aren't browser idiosyncrasies to worry about today. In fact, if you're concerned about rendering differences between Chrome and Safari, you're probably worrying too much about the exact presentation details.

I very often find websites broken in Safari that work in Chrome.

> Browser idiosyncrasies, horrendous security vulnerabilities, the blood sacrifices to do basic things with CSS,

...

> There are many good things about this world. 2005 web dev is not among them.

Maybe, but the 2005 process will work better now, because the current process was started as a way to paper over all those

> Browser idiosyncrasies, horrendous security vulnerabilities, the blood sacrifices to do basic things with CSS,

Now that those things are smaller issues, "Write JS, copy it to the server" is not so stupid. Especially if you've got mostly web components.

You can pry flexbox out my cold dead hands.

Go and vertically center a div in whatever way you see fit.

That was my point, with the tech improvements we now have in frontend many of the reasons for abandoning the 2005 process becomes moot.

New tech makes the old process more viable, not less.

The article is about CSS properties.

Is that new tech or new process?

New tech.

Reply on news.ycombinator.com