Re:Ask HN: Should HTML5-based websites be more expensive?
by napolux on Monday May 13, 2013 @10:38AM
(#5698873)
Should a PHP script be more expensive than a Ruby script that does the same thing?
What are you trying to achieve using HTML5 instead of xHTML? Are you using specific HTML5 apis? Did your client asks for a special feature that it's only available in HTML5?
I would usually do my works in the best technology available and acceptable to my client, but it really depends on your client needs.
I would for sure ask more money to make a website IE7 compatible, for instance.
Re:Ask HN: Should HTML5-based websites be more expensive?
by ch0wn on Monday May 13, 2013 @10:37AM
(#5698867)
What exactly do you mean by HTML5-based? The term is way too loose to make assumption about the effort or price. Do you mean using new APIs? Just changing the doctype and removing some slashes?
Re:Ask HN: Should HTML5-based websites be more expensive?
by Annet on Monday May 13, 2013 @11:00AM
(#5699022)
When a client asks for new APIs and more complex HTML5 specific features, it's clear and it's easy to explain why it could be more expensive. But if he/she asks "Develop me a website in HTML5 because I think XHTML is obsolete and has no future", the answer isn't so evident.
What are you trying to achieve using HTML5 instead of xHTML? Are you using specific HTML5 apis? Did your client asks for a special feature that it's only available in HTML5?
I would usually do my works in the best technology available and acceptable to my client, but it really depends on your client needs. I would for sure ask more money to make a website IE7 compatible, for instance.