Precisely the way to do it. Requiring backslashes in empty tags makes a lot of sense, because otherwise a parser has to do some gymnastics to figure out whether or not the tag was opened by not closed or actually empty. For HTML, it's not that much trouble, but XML changes a lot of things.
The trouble with this is when you start getting remotely complex dataforms passed to your application. Even plaintext has it's issues: did you know that the flagship PHP function for escaping text htmlentities() doesn't actually properly escape the text? It's blithely ignorant of encoding issues and will happily pass along control characters and malformed strings.
Combine that with HTML and you've got a formidable problem. Not one that can't be solved, take for example HTML Purifier, but it is extremely difficult to do well. Whitelists often butt heads with permissiveness.
No, but I've had it happen in a theater context (actors are playing video games in the back room, but the mikes aren't off so it's broadcasting into the auditorium).
Of course, you could assign multiple addresses to each machine, and get rid of the need for ports...
Yes, we ought to assign 65,535 IP addresses to every device that wants to connect to the Internet. (And yes, I know that it still won't solve our Too Many IP Addresses (TM) problem).
Well, if they are a certificate provider, then they should be self-signing. How weird would it be if they were using a Verisign cert?
The real problem, however, is convincing the major browsers to add cacert to their default trusted certificate authorities. Firefox already has a bug for this: https://bugzilla.mozilla.org/show_bug.cgi?id=21524 3
I think that the reason Java doesn't want forking is to make sure that a program one person writes will always work on all Java interpreters. Sounds familiar to Knuth's concepts about TeX. The way they achieved it was by prohibiting new derivatives from being released under the same name (see http://en.wikipedia.org/wiki/TeX#License) and those using TeX in their name must pass a rigorous test suite. The license is not GPL compatible, but perhaps Java could adopt something similar?
The ironic thing is that I made most of that information available when I registered for a domain name. I just don't like it when people fake information in Whois.
Don't forget part of the problem is that our connections are assymetric. 100+ kb/sec for downloads, but ~10 kb/sec for *any* uploading is the best you can hope for.
That's even worse! Whatever happened to Oboe, the instrument? And no, I was not being ironic, I seriously did not expect that. Idiots. PageRank wielding idiots. >:-(
As an oboe player, I ask you this: how does this have anything to do with oboes? Plus its such a generic term that they cannot realistically expect someone to Google oboe and have anything related to their service show up.
Oh, FAQ authors think they're so smart? One word: Nihilartikel. Serving dictionaries finely since 1887.
Re:My short experience with perl...
on
What is Perl 6?
·
· Score: 1
This was a bit of a put off for me to. I asked a friend about it and they said it was an artifact from the days when Perl didn't need to deal with complex multidimensional arrays. Basically, no one ever thought anyone would need to use it.
Slashdot Mirror
Precisely the way to do it. Requiring backslashes in empty tags makes a lot of sense, because otherwise a parser has to do some gymnastics to figure out whether or not the tag was opened by not closed or actually empty. For HTML, it's not that much trouble, but XML changes a lot of things.
So is it going to get pushed out via Automatic Updates this coming Tuesday?
The trouble with this is when you start getting remotely complex dataforms passed to your application. Even plaintext has it's issues: did you know that the flagship PHP function for escaping text htmlentities() doesn't actually properly escape the text? It's blithely ignorant of encoding issues and will happily pass along control characters and malformed strings.
Combine that with HTML and you've got a formidable problem. Not one that can't be solved, take for example HTML Purifier, but it is extremely difficult to do well. Whitelists often butt heads with permissiveness.
Precisely. Cordon off all the ambiguous stuff, and program the rest of it.
I have a feeling that it's a lot more than just two ISPs.
No, but I've had it happen in a theater context (actors are playing video games in the back room, but the mikes aren't off so it's broadcasting into the auditorium).
Yes, we ought to assign 65,535 IP addresses to every device that wants to connect to the Internet. (And yes, I know that it still won't solve our Too Many IP Addresses (TM) problem).
I imagine that they would attempt to lobby Microsoft to get themselves included.
Well, if they are a certificate provider, then they should be self-signing. How weird would it be if they were using a Verisign cert?
4 3
The real problem, however, is convincing the major browsers to add cacert to their default trusted certificate authorities. Firefox already has a bug for this: https://bugzilla.mozilla.org/show_bug.cgi?id=2152
Tell that to Wikipedia.
I'll give the parent post the benefit of the doubt. The article text is worded in a way that strongly suggests client-side.
Well, server-side applications and client-side applications are, quite arguably, different sorts of programs.
"And based on my own experience trying to write a long-running maintance daemon in PHP"
;-)
Maybe that's because PHP isn't supposed to be used for writing daemons.
I think that the reason Java doesn't want forking is to make sure that a program one person writes will always work on all Java interpreters. Sounds familiar to Knuth's concepts about TeX. The way they achieved it was by prohibiting new derivatives from being released under the same name (see http://en.wikipedia.org/wiki/TeX#License) and those using TeX in their name must pass a rigorous test suite. The license is not GPL compatible, but perhaps Java could adopt something similar?
The ironic thing is that I made most of that information available when I registered for a domain name. I just don't like it when people fake information in Whois.
Chinese Wikipedia was blocked, and not much response came from the tech atmosphere. Wikipedians even conjectured that China was preparing to launch their own version of Wikipedia... well, now, that has happened. See http://en.wikipedia.org/wiki/Blocking_of_Wikipedia _in_mainland_China and http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_S ignpost/2005-10-31/China_block
Christmas is a good instance of when this happens, through featured article removal.
Hey, remember, your toothbrush has flecks of feces on it. I'm sure a few oxidized organic compounds won't hurt you.
Don't forget part of the problem is that our connections are assymetric. 100+ kb/sec for downloads, but ~10 kb/sec for *any* uploading is the best you can hope for.
...
That's even worse! Whatever happened to Oboe, the instrument? And no, I was not being ironic, I seriously did not expect that. Idiots. PageRank wielding idiots. >:-(
Oboe? Oboe?!?!
As an oboe player, I ask you this: how does this have anything to do with oboes? Plus its such a generic term that they cannot realistically expect someone to Google oboe and have anything related to their service show up.
Oh, FAQ authors think they're so smart? One word: Nihilartikel. Serving dictionaries finely since 1887.
This was a bit of a put off for me to. I asked a friend about it and they said it was an artifact from the days when Perl didn't need to deal with complex multidimensional arrays. Basically, no one ever thought anyone would need to use it.
The extension is not listed at Mozilla Update yet. The home website has already been slashdotted. How do we know this is not just advertising?
> It's much faster and reliable than any of the others that I've tried.
Maybe that's why the private trackers are angry.