The last version works also well on MacOSX. (on my iBook & MacOSX 10.4.4)
A couple of clones of the game are also available (use your favorite search engine of course) and some of them are quite fun and at least one is multiplayer (LAN/WAN).
Sorry for repeating this post, it was mangled when I first submitted it...
As a Web developer I can tell you that there is 90% chance that XHTML 2.0 will never be used by anyone.
First, it does not add anything really useful that you could not do with XHTML 1.0. Well, there are things that are useful (in related standards actually), but there are too complicated to be implemented in current browsers (XForms, XML Events, add all of SVG to that). <section> and <l> are great, but you could do similar things with <div class="section"> or even "gasp" <nobr> (I know, nobr as only a visual meaning, but you could infer a real semantic meaning if you really wanted to).
Now, if it added something that would really change something for the Web developer, like in XAML (I don't know a lot about it, it seems interesting) I would eagerly wait for the implementations. What the WHATWG does seems a lot more interesting.
The next real web standard will be to HTML/XHTML what client server computing is to dumb terminal / mainframe computing. Anything that does not go in that direction will not be accepted by the industry. XHTML 2.0 is completely uninteresting in that regard.
And for crying out loud, I know <br/> is evil, but it is still neaded. <l> does not replace it. <l> encapsulates, <br/> separates. <hr/> as been changed to <separator/>... good. But please, change <br/> to something else. <wsp/> maybe ? (weak seperator, word seperator....). With style sheets, it could be ignored when it is not important (audio). (It could be a pause in audio, why not?). The people that creates those standards (I know there are a lot more intelligent than me) definitly never had to work with people descendant from the Golgafrincham B ship (lucky them). They want <br>s everywhere. And, there are the ones that pay's the web developpers. I know, I can, and will, do everything that's possible to make my web pages validate to web standards and have the best semantic HTML that is possible relative to everything else (incompatible CMS, marketing divisions, Flash, tight schedules, fellow web developer that don't test except in IE). But leaving <br> just takes the biscuit!
Sorry for the rant, the awful english and the bad Hitch Hicker's to the Galaxy references.
As a Web developer I can tell you that there is 90% chance that XHTML 2.0 will never be used by anyone.
First, it does not add anything really useful that you could not do with XHTML 1.0. Well, there are things that are useful (in related standards actually), but there are too complicated to be implemented in current browsers (XForms, XML Events, add all of SVG to that). <section> and <l> are great, but you could do similar things with <div class="section"> or even "gasp" <nobr> (I know, nobr as only a visual meaning, but you could infer a real semantic meaning if you really wanted to).
Now, if it added something that would really change something for the Web developer, like in XAML (I don't know a lot about it, it seems interesting) I would eagerly wait for the implementations. What the WHATWG does seems a lot more interesting.
The next real web standard will be to HTML/XHTML what client server computing is to dumb terminal / mainframe computing. Anything that does not go in that direction will not be accepted by the industry. XHTML 2.0 is completely uninteresting in that regard.
And for crying out loud, I know <br/> is evil, but it is still neaded. <l> does not replace it. <l> encapsulates, <br/> separates. <hr/> as been changed to s everywhere. And, there are the ones that pay's the web developpers. I know, I can, and will, do everything that's possible to make my web pages validate to web standards and have the best semantic HTML that is possible relative to everything else (incompatible CMS, marketing divisions, Flash, tight schedules, fellow web developer that don't test except in IE). But leaving
just takes the biscuit!
Sorry for the rant, the awful english and the bad Hitch Hicker's to the Galaxy references.
I have a kid and the first thing (she/he) will find on your computer is the reset button.
It is extremely important to buy a child proof case for your computer, especially if your child can reach it (which should be the case if your computer is on the floor).
My daughter started playing with the keyboard at 3 months. Buy yourself a spare keyboard your child can play with. PCjr chicklet keyboards are great for that (and easy to clean).
Don't leave your laptop on the floor, unless your company can afford to replace it.
No flat pannel monitors and always clean your monitor!
That reminds me, I have to buy two new computers for my unborn twins. I have until february...;)
Slashdot Mirror
The last version works also well on MacOSX. (on my iBook & MacOSX 10.4.4)
A couple of clones of the game are also available (use your favorite search engine of course) and some of them are quite fun and at least one is multiplayer (LAN/WAN).
Sorry for repeating this post, it was mangled when I first submitted it...
/> is evil, but it is still neaded. <l> does not replace it. <l> encapsulates, <br /> separates. <hr /> as been changed to <separator />... good. But please, change <br /> to something else. <wsp /> maybe ? (weak seperator, word seperator....). With style sheets, it could be ignored when it is not important (audio). (It could be a pause in audio, why not?). The people that creates those standards (I know there are a lot more intelligent than me) definitly never had to work with people descendant from the Golgafrincham B ship (lucky them). They want <br>s everywhere. And, there are the ones that pay's the web developpers. I know, I can, and will, do everything that's possible to make my web pages validate to web standards and have the best semantic HTML that is possible relative to everything else (incompatible CMS, marketing divisions, Flash, tight schedules, fellow web developer that don't test except in IE). But leaving <br> just takes the biscuit!
As a Web developer I can tell you that there is 90% chance that XHTML 2.0 will never be used by anyone.
First, it does not add anything really useful that you could not do with XHTML 1.0. Well, there are things that are useful (in related standards actually), but there are too complicated to be implemented in current browsers (XForms, XML Events, add all of SVG to that). <section> and <l> are great, but you could do similar things with <div class="section"> or even "gasp" <nobr> (I know, nobr as only a visual meaning, but you could infer a real semantic meaning if you really wanted to).
Now, if it added something that would really change something for the Web developer, like in XAML (I don't know a lot about it, it seems interesting) I would eagerly wait for the implementations. What the WHATWG does seems a lot more interesting.
The next real web standard will be to HTML/XHTML what client server computing is to dumb terminal / mainframe computing. Anything that does not go in that direction will not be accepted by the industry. XHTML 2.0 is completely uninteresting in that regard.
And for crying out loud, I know <br
Sorry for the rant, the awful english and the bad Hitch Hicker's to the Galaxy references.
As a Web developer I can tell you that there is 90% chance that XHTML 2.0 will never be used by anyone.
/> is evil, but it is still neaded. <l> does not replace it. <l> encapsulates, <br /> separates. <hr /> as been changed to s everywhere. And, there are the ones that pay's the web developpers. I know, I can, and will, do everything that's possible to make my web pages validate to web standards and have the best semantic HTML that is possible relative to everything else (incompatible CMS, marketing divisions, Flash, tight schedules, fellow web developer that don't test except in IE). But leaving
First, it does not add anything really useful that you could not do with XHTML 1.0. Well, there are things that are useful (in related standards actually), but there are too complicated to be implemented in current browsers (XForms, XML Events, add all of SVG to that). <section> and <l> are great, but you could do similar things with <div class="section"> or even "gasp" <nobr> (I know, nobr as only a visual meaning, but you could infer a real semantic meaning if you really wanted to).
Now, if it added something that would really change something for the Web developer, like in XAML (I don't know a lot about it, it seems interesting) I would eagerly wait for the implementations. What the WHATWG does seems a lot more interesting.
The next real web standard will be to HTML/XHTML what client server computing is to dumb terminal / mainframe computing. Anything that does not go in that direction will not be accepted by the industry. XHTML 2.0 is completely uninteresting in that regard.
And for crying out loud, I know <br
just takes the biscuit!
Sorry for the rant, the awful english and the bad Hitch Hicker's to the Galaxy references.
I have a kid and the first thing (she/he) will find on your computer is the reset button.
It is extremely important to buy a child proof case for your computer, especially if your child can reach it (which should be the case if your computer is on the floor).
My daughter started playing with the keyboard at 3 months. Buy yourself a spare keyboard your child can play with. PCjr chicklet keyboards are great for that (and easy to clean).
Don't leave your laptop on the floor, unless your company can afford to replace it.
No flat pannel monitors and always clean your monitor!
That reminds me, I have to buy two new computers for my unborn twins. I have until february...