The computed digits number doesn't even matter anymore since we can calculate the value of a given byte of PI without having calculated any of the previous ones.
As a side note, the current record by the Kanada lab is 1.2411 trillion digits, their previous record was a bit above 200 billions.
For god's sake, RTFP, Rusin didn't complain about the fact that he couldn't merge the patches on the trunk, he is annoyed by the fact people think it is, and think Apple is all great and mighty and actually cooperates with the KHTML team, which is not true.
They had basically been trying to forget about that it seems, until everyone (and I admit i was one of them before i read rusin's post) started singing that K-Linux users would benefit from Dave's work...
From Rusin's post and links, it looks like the KHTML guys did quite a lot for Apple's sake (creating specific mailing lists and such).
They don't look like they're asking for much, basically they'd like access to the Safari team's changelogs (and internal CVS I think) in order to see how the changes happened, why the modifications were made (because knowing that a modification was done but having no damn clue about why it was done can be quite useless) and where, and which internal of external features the modification uses.
From what i understood, in a nutshell, the KHTML guys merely used to ask for a documentation that was supposed to exist instead of big webcore tarballs, that was more or less denied and the KHTML guys stopped asking for it.
But they're quite annoyed about the buzz over Safari's change getting back to KHTML, which is something that they're not able to do.
On a side note, it should be reminded that KHTML is only part of the K distribution, which means that they can't afford to put more work in KTHML engine alone that on KDE for example.
From Rusin's post, these patches are not useable (mainly because they often rely on previous Safari specific implementations that don't exist in KHTML trunk, or for the worse ones because they rely on OSX features itself and thus can't be ported to KHTML without a full rewrite)
No, it seems like they're doing everything they're legally bound to do.
And that only, nothing more at all, which is the part that annoys the KHTML team.
Also makes me wonder why in Spanish, Germany is called Alemania.
I guess it could be because spanish is a latin language while english has both germanic and celtic origins (mainly germanic, supposedly). As a proof, in French (strong latin roots) Germany is called "Allemagne".
As for why no one uses the simple way of calling people by the name they gave themselves, bites me, guess it'd be too complicated, or people like being bitches to others. Or more than likely there are problems with prononciation (sp?) and people don't want to make the effort of learning the right ones...
Doesn't really matter, does it?
Who cares about first person shooters, they're probably the most uncreative genre of computer games anyway.
The gaming industry being uncreative is old news, it was already uncreative as hell when 486 hit the shelf for god's sake, and 95% of the "gamerz" populations ain't asking for creativity anyway, they care for l33t FPS, l33t v3rt3x & sh4d3rz, they don't ask for gameplay they care for graphics, they don't want scenario they want T&L. In a word, they care for useless shit.
Try giving them Colonization or the good ol' Lucas Arts age adventure games (Day of the Tentacle, Sam&Max Hit the Road) and see them shiver in pain and wither as they see screens without any vertex tesselation and 3D real time light rendering...
Have you seen which game is arguably the most popular ATM? the fucking sims for god's sake, who cares about creativeness when you can make millions out of "Reality Shows" on computers?
Re:Just a proposal, hopefully...
on
Dutch Pass iPod Tax
·
· Score: 1, Insightful
Good idea.
Dammit, english is tough
Re:Just a proposal, hopefully...
on
Dutch Pass iPod Tax
·
· Score: 2, Insightful
The levy system is the opposed measure set up to make this legal.
Since it's already legal, i guess you meant "to extort some money without getting raped trying to mess with the current laws".
If this tax comes live, I guess the Belgian and German MP3-player markets will suddenly flourish while the neder??? (how do you spell "something from Nederlands"?) will drop to death.
And if that leads to a browser that cannot adequately render 99% of the web, is that acceptable?
What part of "if a page declares a doctype" did you miss?
AFAIK, these 99% of the web usually don't have W3C's doctype, therefore don't trigger standard mode in the browsers where it's avaible, therefore are rendered in quirk mode.
And if they have the doctype and ain't valid, then let them break, they're supposed to, if a webmaster has enough knowledge of his job to put a doctype (every webmaster should, but...) then he should have enough to make a valid page per the specifications of the used doctype.
Actually, ignore me. I'm wrong and so is the article poster.
The patches are available on the website for all to download.
You're partially (heck, I'd even say "mostly") right, since I don't think you can build Safari yourself (I doubt Apple users get to get Safari's source), so as of now Safari users can't get their hands on it indeed.
Konqueror users can.
But since you can't build your own version of Safari it's not avaible in Safari.
It's avaible to Konqueror users though, of course, if they can go through applying the patch to the KHTML engine's source and recompile (or they'll just wait for the next Konqueror version that'll implement these patches)
It won't, Mozilla devs are far behind schedule and have quite a lot of important bugs to fix with Gecko 1.8 (rendering engine for Firefox 1.1).
Sadly, Acid2 won't be high priority before Gecko 1.9, which means that firefox won't be fully CSS2 compliant before at least version 1.2.
Please do read the Acid2 page, there are lots of invalid/incorrect codes in the text that shouldn't be parsed by the browsers.
Acid2 page is not supposed to validate because it tests both compliance with how things should be rendered and with what shouldn't be rendered at all.
We have the same problem with javascript, only that is 10 times more disturbing because if javascript was actually the same all other the place web surfing could be enhanced so much. The only reason people don't like javascript is because the popups, and that's not everything in javascript.
I beg to disagree, popups is not the only reason why people hate JS (one could even say that they fear it).
General misuses and abuses of JS is, and in this general abuses are:
Popups, of course
Stupid effects (shitty animated gifs following cursors anyone?)
Messing with browsers (resizing, changing parts of the global UI, alert boxes)
Code design so bad that browsers grind to a halt (oh, i so love seing my CPU usage skyrocket to 100% and stay there because i opened a bugged page)
Slowing the browsing
Disabling the browsing altogether because of non standard or stupid scripts (mmm, yummy Javascript links, I mean anchor tags are certainly not hip enough for a damn link are they?)
Probably many other i can't think of right now
"Modern" javascript and the usage of DOM scripting allow wonderful flexibility, and applying the priciples of graceful degradation and progressive enhancement while fully decoupling Javascript from HTML/CSS (by putting JS in a separate file and associating it via the Event Handlers, layering a behavioural javascript on top of an existing fully functionnal JS-less website) allows improving every JS-enabled's navigation while not degrading at all JS-disabled's navigation.
Apple doesn't, Dave Hyatt does.
And you can see (on his blog) the patch that should be applied to the KHTML engine, which means that KHTML users will soon benefit from these (while the release date of these patches in Safari is unknown, since 1.3 and 2.0 just went live with OS 10.4)
It's been proven that the concordski was a ripoff of one of the early designs of Concorde, it was unstable (which is why that draft was trashed/reworked in the first place), concordski never made it to production status and was promptly dropped while Concorde actually got to carry passengers (until Gonesse, that is)
Even if that hadn't been a ripoff thanks to industrial spies, a plane that never managed to fly reliably couldn't be branded 'first supersonic passenger jet', at best it could be the 'first supersonic passenger jet failure'
It's not, which is why you get the UglyGreen background when you've just installed your computer and the UglyBlue version when you've installed the drivers.
It's just low resolution (which is why it lacks... well... resolution)
Slashdot Mirror
The computed digits number doesn't even matter anymore since we can calculate the value of a given byte of PI without having calculated any of the previous ones.
As a side note, the current record by the Kanada lab is 1.2411 trillion digits, their previous record was a bit above 200 billions.
My ass, try ADA for that one
If Java was truly "designed for safety at the start", you just wouldn't need that kind of project
Dammit, borked link, really sorry...
here should be a valid one
I just can't understand how Slashdot manages to break these links that way...
For god's sake, RTFP, Rusin didn't complain about the fact that he couldn't merge the patches on the trunk, he is annoyed by the fact people think it is, and think Apple is all great and mighty and actually cooperates with the KHTML team, which is not true.
They had basically been trying to forget about that it seems, until everyone (and I admit i was one of them before i read rusin's post) started singing that K-Linux users would benefit from Dave's work...
From Rusin's post and links, it looks like the KHTML guys did quite a lot for Apple's sake (creating specific mailing lists and such).
They don't look like they're asking for much, basically they'd like access to the Safari team's changelogs (and internal CVS I think) in order to see how the changes happened, why the modifications were made (because knowing that a modification was done but having no damn clue about why it was done can be quite useless) and where, and which internal of external features the modification uses.
From what i understood, in a nutshell, the KHTML guys merely used to ask for a documentation that was supposed to exist instead of big webcore tarballs, that was more or less denied and the KHTML guys stopped asking for it.
But they're quite annoyed about the buzz over Safari's change getting back to KHTML, which is something that they're not able to do.
On a side note, it should be reminded that KHTML is only part of the K distribution, which means that they can't afford to put more work in KTHML engine alone that on KDE for example.
Come back when you'll actually have seen code
From Rusin's post, these patches are not useable (mainly because they often rely on previous Safari specific implementations that don't exist in KHTML trunk, or for the worse ones because they rely on OSX features itself and thus can't be ported to KHTML without a full rewrite)
No, it seems like they're doing everything they're legally bound to do.
And that only, nothing more at all, which is the part that annoys the KHTML team.
As for why no one uses the simple way of calling people by the name they gave themselves, bites me, guess it'd be too complicated, or people like being bitches to others. Or more than likely there are problems with prononciation (sp?) and people don't want to make the effort of learning the right ones...
Doesn't really matter, does it?
Who cares about first person shooters, they're probably the most uncreative genre of computer games anyway.
The gaming industry being uncreative is old news, it was already uncreative as hell when 486 hit the shelf for god's sake, and 95% of the "gamerz" populations ain't asking for creativity anyway, they care for l33t FPS, l33t v3rt3x & sh4d3rz, they don't ask for gameplay they care for graphics, they don't want scenario they want T&L. In a word, they care for useless shit.
Try giving them Colonization or the good ol' Lucas Arts age adventure games (Day of the Tentacle, Sam&Max Hit the Road) and see them shiver in pain and wither as they see screens without any vertex tesselation and 3D real time light rendering...
Have you seen which game is arguably the most popular ATM? the fucking sims for god's sake, who cares about creativeness when you can make millions out of "Reality Shows" on computers?
Good idea.
Dammit, english is tough
If this tax comes live, I guess the Belgian and German MP3-player markets will suddenly flourish while the neder??? (how do you spell "something from Nederlands"?) will drop to death.
Good for germans & belgians, I guess...
And there do I stand corrected, thanks a lot sir
AFAIK, these 99% of the web usually don't have W3C's doctype, therefore don't trigger standard mode in the browsers where it's avaible, therefore are rendered in quirk mode.
And if they have the doctype and ain't valid, then let them break, they're supposed to, if a webmaster has enough knowledge of his job to put a doctype (every webmaster should, but...) then he should have enough to make a valid page per the specifications of the used doctype.
Konqueror users can.
But since you can't build your own version of Safari it's not avaible in Safari.
It's avaible to Konqueror users though, of course, if they can go through applying the patch to the KHTML engine's source and recompile (or they'll just wait for the next Konqueror version that'll implement these patches)
It won't, Mozilla devs are far behind schedule and have quite a lot of important bugs to fix with Gecko 1.8 (rendering engine for Firefox 1.1).
Sadly, Acid2 won't be high priority before Gecko 1.9, which means that firefox won't be fully CSS2 compliant before at least version 1.2.
Please do read the Acid2 page, there are lots of invalid/incorrect codes in the text that shouldn't be parsed by the browsers.
Acid2 page is not supposed to validate because it tests both compliance with how things should be rendered and with what shouldn't be rendered at all.
None of them, the Acid2 compliance currently only exists on Dave Hyatt's dev version.
It'll probably become avaible sometime in the future for Safari version 1.3 and 2.0 (later being the one bundled with 10.4) as patches, or updates.
Mac users now have to pray that it'll be sooner than later.
General misuses and abuses of JS is, and in this general abuses are:
- Popups, of course
- Stupid effects (shitty animated gifs following cursors anyone?)
- Messing with browsers (resizing, changing parts of the global UI, alert boxes)
- Code design so bad that browsers grind to a halt (oh, i so love seing my CPU usage skyrocket to 100% and stay there because i opened a bugged page)
- Slowing the browsing
- Disabling the browsing altogether because of non standard or stupid scripts (mmm, yummy Javascript links, I mean anchor tags are certainly not hip enough for a damn link are they?)
- Probably many other i can't think of right now
"Modern" javascript and the usage of DOM scripting allow wonderful flexibility, and applying the priciples of graceful degradation and progressive enhancement while fully decoupling Javascript from HTML/CSS (by putting JS in a separate file and associating it via the Event Handlers, layering a behavioural javascript on top of an existing fully functionnal JS-less website) allows improving every JS-enabled's navigation while not degrading at all JS-disabled's navigation.As Douglas Crockford put it, Javascript is the most misunderstood programming language, and I'd add that it's the one with the most extensive yet qualitatively (sp, more than likely) worst documentation ever.
And yet, finding good javascript tutorials and stunning Javascript reference websites is possible. People just don't bother looking for them...
Apple doesn't, Dave Hyatt does.
And you can see (on his blog) the patch that should be applied to the KHTML engine, which means that KHTML users will soon benefit from these (while the release date of these patches in Safari is unknown, since 1.3 and 2.0 just went live with OS 10.4)
It's quite far from a spanking, and you can buy tens of russian fighters for the price of a single F-22...
It's been proven that the concordski was a ripoff of one of the early designs of Concorde, it was unstable (which is why that draft was trashed/reworked in the first place), concordski never made it to production status and was promptly dropped while Concorde actually got to carry passengers (until Gonesse, that is)
Even if that hadn't been a ripoff thanks to industrial spies, a plane that never managed to fly reliably couldn't be branded 'first supersonic passenger jet', at best it could be the 'first supersonic passenger jet failure'
It's not, which is why you get the UglyGreen background when you've just installed your computer and the UglyBlue version when you've installed the drivers. It's just low resolution (which is why it lacks... well... resolution)