Live data from Hacker News

Ask HN: Does HTML5 excite you? Why or why not?

news.ycombinator.com

61–70 of 74 posts

Re: Ask HN: Does HTML5 excite you? Why or why not?

#61
post #20

Earlier quoted context omitted.

Unless new features are added to CSS, I suspect and will behave exactly like s do today.

Uhm? Maybe you mean "unless browseres have predefined CSS rules for new elements"?

No, I don't mean that. If you want to have a design work across different browsers, one of the first things you have to do is find a common baseline. This is where things like reset.css come in, which overrides many predefined styles.

I'll try re-wording my post:

I suspect and will have the same styling possibilities as any other block level element for a particular version of CSS.

Re: Ask HN: Does HTML5 excite you? Why or why not?

#62
post #38

As a client- and server-side developer I'm extremely excited about HTML5. For the first time in a decade, browsers are getting new capabilities! HTML 5 is much more than just new tags - we're talking offline support, concurrency with web workers, canvas, geolocation, native audio and video, WebSockets, a supported method of making cross-domain API calls... HTML 5 is clearly aiming to bring the open web platform up to…

Could someone link to the error model spec? I hadn't heard of this and my Google-fu isn't picking anything up.

Re: Ask HN: Does HTML5 excite you? Why or why not?

#63
post #38

As a client- and server-side developer I'm extremely excited about HTML5. For the first time in a decade, browsers are getting new capabilities! HTML 5 is much more than just new tags - we're talking offline support, concurrency with web workers, canvas, geolocation, native audio and video, WebSockets, a supported method of making cross-domain API calls... HTML 5 is clearly aiming to bring the open web platform up to…

None of these things require HTML 5, and all of the worthwhile things had workable implementations before HTML 5.

Formal specifications for things that had de facto cross-browser support for multiple browser generations are nice, but not amazing.

"This is the first time our core platform has seen any serious evolution since HTML4.01 was published in 1999!"

And that's just simply untrue, but oh, well.

"I'm amazed to see so many web developers unexcited by HTML 5. This is the first time our core platform has seen any serious evolution since HTML4.01 was published in 1999!"

And I'm boggled to see such giddy fanboyism modded up so high.

Re: Ask HN: Does HTML5 excite you? Why or why not?

#64
post #56

Earlier quoted context omitted.

The Google HTML5 plugin for IE6 might not alienate your audience.

I don't get it, though - surely if you are capable of installing a plugin, you are capable of updating your browser, too?

I think part of the problem is MS encouraged people to write a bunch of ie6 specific sites. Thus, since ie doesn't AFAIK do side-by-side installs, the need to stay on ie6 for line of business apps.

Re: Ask HN: Does HTML5 excite you? Why or why not?

#66

Earlier quoted context omitted.

How does that affect you? Your HTML markup will work in HTML5, too. In any case, I keep reading no one will use it for years yet most of the leading developers and designers I know are using it today. And I'm joining them since all my markup is now HTML5 as of six months ago.

When you say that your markup is HTML5, do you just mean that you changed the doctype at the top (That's trivial, and its only real effect is saving a few bytes, though I suppose it's a nice symbolic gesture), or that you are now using all of the new semantic elements like and and , using instead of plugin-based video, including features like drag-and-drop, or offline use of data-heavy apps, &c. &c.?

Yes, using the newer elements. Haven't had a need for the others yet.

Re: Ask HN: Does HTML5 excite you? Why or why not?

#67
post #28

Earlier quoted context omitted.

How does that affect you? Your HTML markup will work in HTML5, too. In any case, I keep reading no one will use it for years yet most of the leading developers and designers I know are using it today. And I'm joining them since all my markup is now HTML5 as of six months ago.

That's interesting. Can you fill out your profile with sites you've worked on?

Because I speak my mind, and the truth that many don't wish to hear, I won't do that even though I'd like to.

Re: Ask HN: Does HTML5 excite you? Why or why not?

#68
post #37

Earlier quoted context omitted.

Not sure what you mean by that... V8 for example is a virtual machine that runs JavaScript.

I still have to use javascript as my programming language. I know there are cross-compilers to javascript, but it is really disappointing that we sorta standardized on a language instead of a bytecode.

IMHO, a single, simple, and flexible language has greatly helped the web become ubiquitous. I think that javascript has been a key ingredient to the web's growth and it might not have been the same if a more "powerful" or "standard" language/jvm was shoehorned in.

Re: Ask HN: Does HTML5 excite you? Why or why not?

#69

Earlier quoted context omitted.

1) Nobody moved away from XML syntax. You can still use it if you want. 2) In most cases XML syntax is pointelss. 3) HTML5 has nothing to do with CSS, and CSS is doing fine, far from being "massive failure".

It doesn't matter whether I can use XML. What matters is that some people will use a new syntax and all the integration hassles and incompatibilities will start once again. Why is it a good idea to invent yet another syntax that is almost the same but not quite compatible? Looking at the ridiculous guru culture that has formed around minor obscure CSS features is very telling. When that happens to a technology I call…

What new syntax are you talking about? There is no new syntax in HTML5.

Re: Ask HN: Does HTML5 excite you? Why or why not?

#70
post #61

Earlier quoted context omitted.

Uhm? Maybe you mean "unless browseres have predefined CSS rules for new elements"?

No, I don't mean that. If you want to have a design work across different browsers, one of the first things you have to do is find a common baseline. This is where things like reset.css come in, which overrides many predefined styles. I'll try re-wording my post: I suspect and will have the same styling possibilities as any other block level element for a particular version of CSS.

In this case, they do. As do and and any other element you can come up with.
Post reply on HN