HTML5

N

Neredbojias

Neredbojias said:
Bollocks back. The constraint of the timeframe you mention is
artificially established and exists only in the reality of our
fantasies.
[snip]

...only as we approach the speed of light (in theory).

For all *practical* purposes, time, and what it is physically
possible to do *within* that time is finite, and therefore a
constraint.

One's own lifespan is a time constraint and is absolute, if
imprecise. How one chooses to use up that resource (lifespan) per
problem, defines time constraints for that problem.

See, that is just my point. Sure, you're not going to be able to go
clubbing in 2202, but you can go clubbing now anytime you want. The
number of the year is established by man; the year itself, by God.
You've already had some years and, hopefully, will have many more.
Don't waste them by fretting over false barriers.
 
D

dorayme

"Roy A. said:
Isn't Quantum physics/theories more like a thesis than a theory?

No. It is an established part of science.
Can
we do any experiment or gartering data to prove that it is true?

By and large, very little of anything big and significant be proved true
by gathering data or doing *an* experiment.
And
can anyone make sense of it without mathematic explanations? To me
it's plain nonsense.

Fair enough. The point of the context which you lifted my remarks from
was that it might be the way of the future for some other sciences
beside fundamental physics. To leap forward and baffle everyone in its
successful wake.

I agree that at some point an imaginative grasp, a way of interpretation
that feels satisfying to humans would be more than nice and I believe it
will come when we accept new models of thinking that would look strange
*now* to us with our mechanical pictures. We will get to accept as
natural many things other than how billiard balls work.
 
G

Ganesh

which is missing the type attribute that was required even in HTML 4.01,
and despite the XHTML attributes in the <html> tag, they have unclosed
<input> and <img> tags. So can you please stop telling us that these
companies are implementing HTML 5 on their websites when they aren't
implementing ANY one version of HTML but have a mix of constructions
from a variety of versions?

I did not tell anything. I was only providing information about the
results I was getting. What they are doing is only known to them. So
far the websites are getting rendered on common browsers without
getting any errors no body is going to be bothered as well.
 
H

Harlan Messinger

Ganesh said:
I did not tell anything. I was only providing information about the
results I was getting. What they are doing is only known to them. So
far the websites are getting rendered on common browsers without
getting any errors no body is going to be bothered as well.

Your original question was whether it's a good idea to switch over to
HTML 5. No, it isn't, no purpose is served by it, especially since it
hasn't been finally defined yet. The fact that some functioning websites
are an absolute mess in regards to the markup they are using isn't
exactly a justification or motivation to do the same.

Lots of websites misspell words. Can people still read them? Yes. Is
that either a justification or a motivation to duplicate those
misspellings? No.
 
R

Roy A.

I did not tell anything.

Yes you did. You was saying "That's the very reason google.com's
implementing it".
I was only providing information about the
results I was getting.

No you where suggesting that Google had implemented html 5.
What they are doing is only known to them.

No, we can all examine the code we get from the server. And as far as
I can tell, they don't use any *new* html 5 elements or attributes,
just some old backwards compatibility stuff. So what results are you
getting?
So
far the websites are getting rendered on common browsers without
getting any errors no body is going to be bothered as well.

HTML don't have any procedure to handle errors, so what you're saying
don't make sense. If your page is rendered as "html 4.01" and you are
using html 5 elements, you don't get errors. If you're saying to the
browsers to use html 5, by adding <!doctype html>, you want get any
reports of errors. By using HTML 5, you're just saying, fix these
errors, but don't tell me about it. No really, even if it was plenty
of errors.

In IE 6 you can have a doctype like this: "<!DOCTYPE anyting that
contains 'html' is rendered as 'almost' html 4.01.>" The 'almost' just
means that you will have problem if you are use tables for layouts.

HTHM 5 have some rules to handle errors, but they would not report
back.
 
R

Roy A.

Your original question was whether it's a good idea to switch over to
HTML 5. No, it isn't, no purpose is served by it, especially since it
hasn't been finally defined yet. The fact that some functioning websites
are an absolute mess in regards to the markup they are using isn't
exactly a justification or motivation to do the same.

Google and Apple might "misspell" some words, but they both carefully
make sure that the elements is structured in the same way in the DOM
(Document Object Model).
 
H

Harlan Messinger

Roy said:
Google and Apple might "misspell" some words, but they both carefully
make sure that the elements is structured in the same way in the DOM
(Document Object Model).

The same way as what?
 
R

Roy A.

In the same way from browser to browser.

If you validate the code for those sites you're getting error like: no
attributes named that, no elements named that; but not errors like:
missing end tag or any errors concerning the structure of the DOM. In
most cases, anyway.
 
H

Harlan Messinger

Roy said:
If you validate the code for those sites you're getting error like: no
attributes named that, no elements named that; but not errors like:
missing end tag or any errors concerning the structure of the DOM. In
most cases, anyway.
All that means is that their garbage is well formed. That's hardly an
accomplishment.
 
G

Ganesh

On Sep 21, 4:02 pm, Harlan Messinger
Your original question was whether it's a good idea to switch over to
HTML 5. No, it isn't, no purpose is served by it, especially since it
hasn't been finally defined yet. The fact that some functioning websites
are an absolute mess in regards to the markup they are using isn't
exactly a justification or motivation to do the same.

Lots of websites misspell words. Can people still read them? Yes. Is
that either a justification or a motivation to duplicate those
misspellings? No.

I am at the very start of implementing things. I am allowed to make
mistakes at this level. Also, it is good to experiment things with
personal websites which I am doing with http://seashell.co.in. I would
not do that with my clients though. With them I would only stick with
what's already proven.

You are right about not following misspellings. Again, it is "OK" to
compare HTML5 with misspelling?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
474,079
Messages
2,570,574
Members
47,207
Latest member
HelenaCani

Latest Threads

Top