Now if only all developers took some notice of that and start to use it.
Unfortunately this will never happen. The big projects you mention (that are the source of most of the security flaws) can't migrate to PDO because most providers still only run some ancient version of PHP 4. And the providers won't migrate because there is no need--most applications are still written with PHP 4 in mind...
The problem is that it will take years for all the commonly-used PHP applications to be rewritten to use these new interfaces, if they ever are at all. And in the meantime all the other criticisms of PHP will still continue to apply.
OpenID seems rather complex. There are already decentralised systems for authenticating a user's identity. But, if it gains momentum I would be happy to use it. One thing I can't work out is how I can create an identity. I have my own domain name and web site; I don't want to rely on Livejournal or another third party to maintain the notion of my identity. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux)
You will only have to pay tax when you recieve _real_ money in the _real_ world. Just as if it came from any other source.
If you found someone mad enough to buy your monopoly money, then the _real_ money you just recieved counts towards your yearly income and so it will be taxed.
When you recieve income from the sale of a virtual good or service, then the money you recieve is yours and so you'll be taxed. It really doesn't seem like such a terribly complicated idea!
Whoa, that software looks pretty neat. Annoying that it requires its own VirtualHost however, and that the calendar URLs end up with index.php in their paths [and that it is written in PHP!;)].
We get by with a simple WebDav share served by Apache. Unfortunately Evolution doesn't understand WebDav--you either need a full CalDav implementation, or you are stuck with read-only calendars via plain http.
It depends on your operating system. The "standard" way is to hold Ctrl+Shift and then type the hexadecimal representation of the unicode code point that you want, but that conflicts with a lot of keyboard shortcuts that people use and so implementors often alter it a bit (for example, with GTK+ you press Ctrl+Shift+U and then type the code point).
If your keyboard has a compose key then you can often compose a glyph from two similar looking glyphs. For example, for an o with an umlaut, " o -> ö (though I expect Slashdot will filter that character out).
Macintosh users have an Option key that they can use to make weird glyphs (option-8 for the infinity symbol, option-g for the copyright symbol, etc). On most operating systems, various other combinations of the Ctrl/Shift/Meta/Alt/AltGr modifier keys and regular keys will allow you to type more glyphs. Most desktop environments also have an on-screen keyboard type program that ease experimentation in this area.
Users of complex (e.g, Asian) scripts have a host of input methods to choose from and configure.
Finally, if all else fails, create a text file full of your faviourite non-ascii characters and resort to the tried and tested method of copying and pasting!:)
Until it goes to court, it's up to those who want to try their luck to get away with going against MySQL Inc's wishes/license. :)
Apply the metaphor to PHP and I will agree with it wholeheartedly.
The problem is that it will take years for all the commonly-used PHP applications to be rewritten to use these new interfaces, if they ever are at all. And in the meantime all the other criticisms of PHP will still continue to apply.
People would then complain that it is too different from the standard of MS Office...
Xen
VMWare
linux-vserver
UML
OpenVZ
Plex86
Qemu
Bochs
lhype
and now
KVM
http://linuxvirtualization.com/ has some good linux to recent announcements regarding virtualisation software on Linux.
Are there any more?
Someone should tell IANA about that...
Rather, he wants someone who *passed* *elementary school maths*. Or have standards slipped on your side of the pond, too? :(
OF WHAT CIPHER!
Damnit!
Why doesn't the uevent consumer (e.g., hotplug or udev) load the appropriate kernel module automatically when the dance mat is plugged in?
Nah, I'm a sword, not an AI.
:)
http://en.wikipedia.org/wiki/Curtana
Sadly Bungie and I picked the same mythos, and now everyone mistakes me for that purple bimbo!
You're telling me! -curtana
Thank you both for this information. I feel silly for not looking hard enough to find it myself!
-----BEGIN PGP SIGNED MESSAGE-----
f xLrtlKGDHcrIp7jidODlrTQCgqCPxr rPJA=
Hash: SHA1
OpenID seems rather complex. There are already decentralised systems for authenticating a user's identity. But, if it gains momentum I would be happy to use it. One thing I can't work out is how I can create an identity. I have my own domain name and web site; I don't want to rely on Livejournal or another third party to maintain the notion of my identity.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFdYQlshl/216gEHgRAk00AJwLvC
czXJO4lwp5Znr+A7sS
=MeMH
-----END PGP SIGNATURE-----
CFLAGS += -lgc
Internet link of the year. Congratulations. :D
You will only have to pay tax when you recieve _real_ money in the _real_ world. Just as if it came from any other source.
If you found someone mad enough to buy your monopoly money, then the _real_ money you just recieved counts towards your yearly income and so it will be taxed.
When you recieve income from the sale of a virtual good or service, then the money you recieve is yours and so you'll be taxed. It really doesn't seem like such a terribly complicated idea!
Which makes the spectre of Vista+1 a truely horrifying concept.
Ok, that sounds great. I look forward to being able to swap out my current WebDAV share with RSCDS!
Whoa, that software looks pretty neat. Annoying that it requires its own VirtualHost however, and that the calendar URLs end up with index.php in their paths [and that it is written in PHP! ;)].
We get by with a simple WebDav share served by Apache. Unfortunately Evolution doesn't understand WebDav--you either need a full CalDav implementation, or you are stuck with read-only calendars via plain http.
Your summaries of the patents are far too broad. In addition, none of them have anything to do with Linux.
Encore!
It depends on your operating system. The "standard" way is to hold Ctrl+Shift and then type the hexadecimal representation of the unicode code point that you want, but that conflicts with a lot of keyboard shortcuts that people use and so implementors often alter it a bit (for example, with GTK+ you press Ctrl+Shift+U and then type the code point).
:)
If your keyboard has a compose key then you can often compose a glyph from two similar looking glyphs. For example, for an o with an umlaut, " o -> ö (though I expect Slashdot will filter that character out).
Macintosh users have an Option key that they can use to make weird glyphs (option-8 for the infinity symbol, option-g for the copyright symbol, etc). On most operating systems, various other combinations of the Ctrl/Shift/Meta/Alt/AltGr modifier keys and regular keys will allow you to type more glyphs. Most desktop environments also have an on-screen keyboard type program that ease experimentation in this area.
Users of complex (e.g, Asian) scripts have a host of input methods to choose from and configure.
Finally, if all else fails, create a text file full of your faviourite non-ascii characters and resort to the tried and tested method of copying and pasting!
Snail mail. If you pay in a lot of cash, Smile/Cahoot and similar banks are not for you.