What makes PHP nice is that, language-wise, it is basically C plus a subset of C++ wrapped up in a scripting language. Almost any code written in C (or C++ without templates/exceptions/other icky stuff) can be trivially ported to PHP by replacing the type names with "var" and adding dollar signs in the right places. (I'm exaggerating slightly, but not much.)
PHP5 can actually handle exceptions, and has your normal public, private, etc. modifiers available for class properties. The var syntax is only necessary in PHP4 and has only been retained for compatibility reasons. I would be in support of removing var in PHP6 if the developers so chose.
The purpose of the article was improving performance and response times. This means trading in practices which one should be doing to optimize for what works best. While DOM manipulation may be the standards compliance way of going it is dramatically slower than innerHTML. It is only recently that Safari and Opera have been able to increase the speed of DOM manipulation, but sadly IE and Firefox (the two more used browsers) show better results for innerHTML. In my own testing Firefox 3 was closer to the Opera timing, only with the innerHTML and DOM method results reversed.
And future proofing isn't really an argument because the prevalence of innerHTML is so vast that dropping support for such a feature is equivalent to market share suicide. It would break so many sites that it would kill any base said browser had.
DOM manipulation is a useful tool, but one needs to know when to use it and when not to. I typically start with DOM manipulation when writing a JavaScript application using createElement for new nodes. If new nodes need to be created within a loop, I first create one node outside of the loop, and then clone a newer second node for each iteration (as mentioned in my first link). It is only after that that if performance is lacking AND I am lucky enough that I did not need to append any event handlers to said elements that I resort to innerHTML.
They are using HTML, not XHTML. Per the specification, omitted end tags are valid. The if an end tag is missing the element is closed at the end of the parent element or the start of the next block level element.
What makes you think that Google Analytics should only be used for sites that have ads? Google Analytics has a ton of features: page hits, landing pages, bouncing pages, average time on site, average hits, top keywords, 404s, etc. I admit it's been a bit since I've used it, but from what I remember it's a very damned useful tool.
I realize this is Slashdot, but I still have to ask if you even bothered to read the post before hitting Reply? The OP wasn't saying that the people at W3C aren't responsible, he was saying that webmasters aren't responsible, and he's right. The problem here is with badly-written programs constantly requesting something they neither need nor use. Webmasters write web sites, not applications that render HTML (or any of the other standards that require a DTD published by the W3C).
Yes, when virtually no one turns out to be 36.84% of all users, or roughly 47.6% of all users using some version of IE (4-7, including pocket), I'd say that no one has moved over.:p
Since I've talked to the Swift developer (singular), I can say that Swift is technically still alive (or at least it was a few weeks ago, even if every link he ever sent me is now dead). I believe that he said that he expected that Swift 0.4 to be available by the time Safari 3 gets out of beta.
I don't know where he plans on hosting it, but because of his comment about version 0.4 it seems that Safari being released on Windows did not deter him from releasing his browser. For a low version number release by a single developer, it was an ok browser.
Honestly I'm surprised that the community didn't offer him better help on maturing his product (I believe it was GPL, but I do not recall and I only have the 0.2 source at home) or at least help him with bandwidth. Having a Webkit based browser on Windows is pretty damned useful for developers. Sadly, thanks to Apple's release of Safari on Windows I doubt this will ever happen.
Actually the spec says that the only properties that apply to columns are border, background, width, and visibility. The fact that IE6/7 support for other properties (e.g. text-align, and color) on this element is a bug.
The MPI_Wait statement does not prevent it from being asynchronous (in fact, I don't even think it'd even compile if a synchronous send/receive call was used here). The example that was given merely simulated a synchronous call by calling having MPI wait for the send to complete before continuing. A better example would have been:
if(pid==x) { MPI_bISend(z[0]); MPI_bISend(z[n-1]); /* some computation that only needs z[1] through z[n-2] */ MPI_Wait(Until request struct matches data); MPI_bIRecv(a);/* a = z[0] from pid = y */ MPI_bIRecv(b);/* b = z[n-1] from pid = y */ /* some computation that needs a and b */ }
if(pid==y) { MPI_bISend(z[0]); MPI_bISend(z[n-1]); /* some computation that only needs z[1] through z[n-2] */ MPI_Wait(Until request struct matches data); MPI_bIRecv(a);/* a = z[0] from pid = x */ MPI_bIRecv(b);/* b = z[n-1] from pid = x */ /* some computation that needs a and b */ }
I think that people here are confusing parallel programming with concurrent programming. Parallel = multiple processors, concurrent = multiple processes. When apache forks a new child to handle requests that is an example of concurrent programming. When p2-pNumproc sends data from p1 in a hypercube in order to compute a standard deviation then that is an example of concurrent programming.
A directory accessible by URL-chopping is a public place. Anyone with knowledge of semantics of URLs understands how to construct chopped URLs and use them to find information on a wwebsite.
What if I was viewing some flash file at www.foo.com and the flash file loaded an mp3 file 'bar.mp3' located in www.foo.com/asdka9823jcsaosjoda/ . Now, it's possible one could guess that their would be a folder of this name that would load the data, but it is more likely that they inspected the HTTP headers and saw www.foo.com/asdka9823jcsaosjoda/bar.mp3 existed, and then chopped the URL to find all of the mp3s. That's not really much more work than what was being done in this case. Does it matter that the folder was named 'asdka9823jcsaosjoda' rather than 'mp3' or 'music' or something similar?
I guess I'm an oddball that never watched it when it first came out and never planned on buying the DVD, but have found Josh Whedon's run on Astonishing X-Men over at Marvel to be entertaining (though not great, like so many fanboys claim). I made it my intention to watch it and Baboylon 5 (thanks to JMS' runs on Amazing Spider-Man, Book of Lost Souls, etc.) if I ever was informed of a network airing either series from the beginning. Given that I already have Mondays off, it looks like I'm going to have my day planned for the 18th.
Odd. Because I run as a non-administrator on Windows and I am not only informed of updates, but also able to install them (which would bother me if it was for any software besides Mozilla software). The same thing applies to Thunderbird too. I can't install new versions of them, but I can update them.
Yes well, the courts have previously ruled that ADA does not apply to the web. Sure, there are other laws out there that cover similar topics, but not the ADA.
The talking point is to not use table tags for non-tabular data. Tabular layout on the other hands is something that many would still like to have, and is a part of CSS2 (display: table/table-row/table-cell/etc.). There have been literally thousands of articles written on how to achieve a table-like column structure using CSS that would never have been written if IE had support for any of the table related values for the display attribute.
Re:OMG!? "Opera-specific extensions"!?
on
Opera 9.0 Released
·
· Score: 1
Another extension that Opera recently added is that it now supports the DOMContentLoaded event. This means that now every popular browser (IE, Mozilla/Firefox/Netscape, Opera, and Safari/Konqueror) can now call scripts once the DOM has been loaded, but before the page has finished loading (i.e., before images are done downloading).
Since the article does not discuss this, does anyone know how well these browsers do on the Acid2 Test. I remember Slashdot reporting on Safari and Konqueror passing the test. Were those changes ever rolled out into the latest versions of those browsers?
Am I the only one that noticed that their stock was going down on the screenshots page as an example of the stocks option for GDS? That doesn't look like very good marketing to me....
It also should produce valid HTML. Heck, valid HTML sans the DOCTYPE would be acceptable (though, it should get rid of the xml:lang attribute on the HTML tag if it is not striving for XHTML). H1's do not belong inside p tags!
By any chance does anyone know if the Google Web Accelerator might use this on XHTML pages when viewed in Firefox? I installed both the GWA and NS8 at work, and found that when I visited a page in Firefox with invalid XHTML it would no longer display, but instead pointed to where the breakage in the XHTML occured (in the case that I had seen an img tag was not properly closed so it broke at the closing p tag).... I thought that seemed to be fairly odd for Google to release a product that couldn't handle invalid trivial XHTML breakage, but if these are some how tied together it makes a bit more sense to me.
If security is such a concern, how come I keep clicking the "Check now" button for updates on my plain old 8.0 install and it hasn't informed me of an 8.0.1 update?
I installed Netscape 8 the day it came out for testing purposes. I saw this story, went to Netscape with their default skin and found they had nothing similiar to the Firefox's red ! to alert me that updates were necessary. I went to Tools->Advanced->Software Update and found Automatically Download and install updates was checked by default, so I checked my UA string to find it was still Netscape 8.0. Went back to Software Update and ran Check Now and it did not find any updates. Switched to their other theme (I do appreciate it coming with two themes provided for users to choose from) and found no icon next to that throbber either (as one might expect). Will this be turned on/fixed in the future, or was the functionality for this in the 17 MB minimum hard drive space system requirements difference between it and Firefox?
This coupled with the fact that Firefox themes/extensions do not work and the fact that it has twice the recommended system requirement for processor speed and memory (which seems accurate as it seems slower than Firefox and I am somewhere in between Firefox and Netscape's recoomended CPU speed) are just a few of the reasons I will not switch back.
What makes PHP nice is that, language-wise, it is basically C plus a subset of C++ wrapped up in a scripting language. Almost any code written in C (or C++ without templates/exceptions/other icky stuff) can be trivially ported to PHP by replacing the type names with "var" and adding dollar signs in the right places. (I'm exaggerating slightly, but not much.)
PHP5 can actually handle exceptions, and has your normal public, private, etc. modifiers available for class properties. The var syntax is only necessary in PHP4 and has only been retained for compatibility reasons. I would be in support of removing var in PHP6 if the developers so chose.
The purpose of the article was improving performance and response times. This means trading in practices which one should be doing to optimize for what works best. While DOM manipulation may be the standards compliance way of going it is dramatically slower than innerHTML. It is only recently that Safari and Opera have been able to increase the speed of DOM manipulation, but sadly IE and Firefox (the two more used browsers) show better results for innerHTML. In my own testing Firefox 3 was closer to the Opera timing, only with the innerHTML and DOM method results reversed.
And future proofing isn't really an argument because the prevalence of innerHTML is so vast that dropping support for such a feature is equivalent to market share suicide. It would break so many sites that it would kill any base said browser had.
DOM manipulation is a useful tool, but one needs to know when to use it and when not to. I typically start with DOM manipulation when writing a JavaScript application using createElement for new nodes. If new nodes need to be created within a loop, I first create one node outside of the loop, and then clone a newer second node for each iteration (as mentioned in my first link). It is only after that that if performance is lacking AND I am lucky enough that I did not need to append any event handlers to said elements that I resort to innerHTML.
They are using HTML, not XHTML. Per the specification, omitted end tags are valid. The if an end tag is missing the element is closed at the end of the parent element or the start of the next block level element.
What makes you think that Google Analytics should only be used for sites that have ads? Google Analytics has a ton of features: page hits, landing pages, bouncing pages, average time on site, average hits, top keywords, 404s, etc. I admit it's been a bit since I've used it, but from what I remember it's a very damned useful tool.
Yes, when virtually no one turns out to be 36.84% of all users, or roughly 47.6% of all users using some version of IE (4-7, including pocket), I'd say that no one has moved over. :p
Since I've talked to the Swift developer (singular), I can say that Swift is technically still alive (or at least it was a few weeks ago, even if every link he ever sent me is now dead). I believe that he said that he expected that Swift 0.4 to be available by the time Safari 3 gets out of beta.
I don't know where he plans on hosting it, but because of his comment about version 0.4 it seems that Safari being released on Windows did not deter him from releasing his browser. For a low version number release by a single developer, it was an ok browser.
Honestly I'm surprised that the community didn't offer him better help on maturing his product (I believe it was GPL, but I do not recall and I only have the 0.2 source at home) or at least help him with bandwidth. Having a Webkit based browser on Windows is pretty damned useful for developers. Sadly, thanks to Apple's release of Safari on Windows I doubt this will ever happen.
Actually the spec says that the only properties that apply to columns are border, background, width, and visibility. The fact that IE6/7 support for other properties (e.g. text-align, and color) on this element is a bug.
So what you're saying is that those bits were intelligently designed?
Don't know how 'informative' became troll exactly... killing moderation by posting.
Conditional comments were first implemented in IE5.
What if I was viewing some flash file at www.foo.com and the flash file loaded an mp3 file 'bar.mp3' located in www.foo.com/asdka9823jcsaosjoda/ . Now, it's possible one could guess that their would be a folder of this name that would load the data, but it is more likely that they inspected the HTTP headers and saw www.foo.com/asdka9823jcsaosjoda/bar.mp3 existed, and then chopped the URL to find all of the mp3s. That's not really much more work than what was being done in this case. Does it matter that the folder was named 'asdka9823jcsaosjoda' rather than 'mp3' or 'music' or something similar?
I guess I'm an oddball that never watched it when it first came out and never planned on buying the DVD, but have found Josh Whedon's run on Astonishing X-Men over at Marvel to be entertaining (though not great, like so many fanboys claim). I made it my intention to watch it and Baboylon 5 (thanks to JMS' runs on Amazing Spider-Man, Book of Lost Souls, etc.) if I ever was informed of a network airing either series from the beginning. Given that I already have Mondays off, it looks like I'm going to have my day planned for the 18th.
Odd. Because I run as a non-administrator on Windows and I am not only informed of updates, but also able to install them (which would bother me if it was for any software besides Mozilla software). The same thing applies to Thunderbird too. I can't install new versions of them, but I can update them.
The NoScript extension covers this for JavaScript (and Java, Flash, more) at least.
Yes well, the courts have previously ruled that ADA does not apply to the web. Sure, there are other laws out there that cover similar topics, but not the ADA.
The talking point is to not use table tags for non-tabular data. Tabular layout on the other hands is something that many would still like to have, and is a part of CSS2 (display: table/table-row/table-cell/etc.). There have been literally thousands of articles written on how to achieve a table-like column structure using CSS that would never have been written if IE had support for any of the table related values for the display attribute.
Another extension that Opera recently added is that it now supports the DOMContentLoaded event. This means that now every popular browser (IE, Mozilla/Firefox/Netscape, Opera, and Safari/Konqueror) can now call scripts once the DOM has been loaded, but before the page has finished loading (i.e., before images are done downloading).
Since the article does not discuss this, does anyone know how well these browsers do on the Acid2 Test. I remember Slashdot reporting on Safari and Konqueror passing the test. Were those changes ever rolled out into the latest versions of those browsers?
Am I the only one that noticed that their stock was going down on the screenshots page as an example of the stocks option for GDS? That doesn't look like very good marketing to me....
It also should produce valid HTML. Heck, valid HTML sans the DOCTYPE would be acceptable (though, it should get rid of the xml:lang attribute on the HTML tag if it is not striving for XHTML). H1's do not belong inside p tags!
By any chance does anyone know if the Google Web Accelerator might use this on XHTML pages when viewed in Firefox? I installed both the GWA and NS8 at work, and found that when I visited a page in Firefox with invalid XHTML it would no longer display, but instead pointed to where the breakage in the XHTML occured (in the case that I had seen an img tag was not properly closed so it broke at the closing p tag).... I thought that seemed to be fairly odd for Google to release a product that couldn't handle invalid trivial XHTML breakage, but if these are some how tied together it makes a bit more sense to me.
If security is such a concern, how come I keep clicking the "Check now" button for updates on my plain old 8.0 install and it hasn't informed me of an 8.0.1 update?
I installed Netscape 8 the day it came out for testing purposes. I saw this story, went to Netscape with their default skin and found they had nothing similiar to the Firefox's red ! to alert me that updates were necessary. I went to Tools->Advanced->Software Update and found Automatically Download and install updates was checked by default, so I checked my UA string to find it was still Netscape 8.0. Went back to Software Update and ran Check Now and it did not find any updates. Switched to their other theme (I do appreciate it coming with two themes provided for users to choose from) and found no icon next to that throbber either (as one might expect). Will this be turned on/fixed in the future, or was the functionality for this in the 17 MB minimum hard drive space system requirements difference between it and Firefox?
This coupled with the fact that Firefox themes/extensions do not work and the fact that it has twice the recommended system requirement for processor speed and memory (which seems accurate as it seems slower than Firefox and I am somewhere in between Firefox and Netscape's recoomended CPU speed) are just a few of the reasons I will not switch back.