The hyoid bone has a role in speech production? What planet are you from?
The most it could do is provide support for the larynx. The larynx has four functions in speech: providing silence, providing a buzzing noise or else letting air flow without noise (the difference between s and z), and creating the English h sound.
As long as H. neanderthalis had a similarly-shaped mouth, it would have been able to whisper in any language that you can speak. If it had a larynx similar to ours, it could speak as well. (Provided it had the mental capacity--speech is pretty specialized. Apes could speak English, too, if they had the appropriate brain structures.)
Evolution has no purpose, clod. Otherwise men wouldn't have nipples; it'd be more efficient to make that a sex-linked trait. (For males, at least.) And no creature until now could alter its own evolution.
The nasty thing about creationism is that it can't be tested. You can't disprove it, and lacking a time machine, you can't prove it.
On the subject of the flounder, its design didn't impair its survivability enough to cause its extinction, so we have flounders. Simple as that. And since it could burrow in sand (as other types of fish do, including many rays) while keeping an eye out for predators, it had slightly better survivability than other fish. Only slightly, or we'd have fewer types of fish.
I've gotten a lot of errors in GNOME that require either remote login (and I disable sshd for security) or a hard reset to fix. (Yes, sometimes that's necessary; what happens when you can't get to a terminal and the GUI's sitting on your commands to get to the console?) Mainly problems with media players, but not always. Also minor annoyances that require issuing a kill command from a terminal or console to close a malfunctioning window.
If Mandrake 9.2 fixed one reliable instability issue, then it would be more stable than 9.1, right?
E17 already features real transparency. Just check out the drop shadows on the epplets. Majorly cool, but it doesn't work for actual applications yet--a design decision, no doubt, and one I hope they'll correct (or at least give options for).
I've been using E17 for the past few days. It's beautiful, and it's as stable as any desktop environment I've used--perhaps more so. Not all the features have been implemented; it still needs a menu editor to be really useful (or just tell me which config file to modify, and put one there by default), and I'd like to see an e17 terminal.
Still, it's lightweight, beautiful, features real transparency, and is unusually stable for being in heavy development.
Depends on the Linux. Ubuntu gets decent after about three hours (add universe and multiverse repositories; add mp3 support, abiword, autoconf, automake, etc); Gentoo takes two or three days.
On the other hand, Windows...you have to install nLite and make another install disk, then reinstall with only the features and services you want or need, then reinstall, then add applications.
Gaim reported a read error and wouldn't let me sign back on. Probably did.
They'll probably start allowing select people to join at first, as they did with gmail (perhaps based on gmail account seniority?) for feature reduction / addition requests. Whoever these people add to their buddy lists, gets an invitation.
But if you have a company that's producing and marketing a Linux, $200 is probably the least of your expenses. You probably spend as much on pens in a year.
As has been pointed out, the restriction is only for people who use the word "Linux" in a product name. End users aren't affected.
I'd like a free trademark for Linux, but really, not even many Linux distributions need the word "Linux" in their name. Red Hat, Gentoo, Ubuntu, Yellow Dog, Source Mages...they all function well enough without the word "Linux" in their names. It's pretty much a moot point.
I'm sorry, I didn't see any reason why someone would switch to Solaris in that editorial. It was mainly minor bitching about the details of installation and Sun's GUI choices.
Reading Perl is a problem, when you're learning it. Reading Python is easier than reading C.
The grandparent is looking for a fast solution--one that he doesn't have to spend a lot of time on. Debugging something that looks like line noise isn't easy, especially since his experience is probably focussed on C-style syntaxes. So it's probably better in his case to use Python.
If you're implementing a large-scale program that involves heavy text manipulation, then you'll want to use Perl. But this project isn't a major thing--it's just there to automate a portion of a sysadmin's work.
The research for the AIDS cocktail has been done, and it's making companies somewhere between five and fourteen thousand per patient per year. That was the GP's point.
A one-time cure for AIDS would net a biotech firm maybe as much as a year on the cocktail. Worse, it could provide immunity, and at the least it'd give the person a strong incentive to practice safe sex. Compare that to ten or fifteen years per patient, and you're talking about a 90% reduction in profits (after a temporary boom).
"Security flaws have a way of coming out, code or no code."
This is true for popular products. Note that the article was asking about a framework over existing libraries; it probably isn't too vulnerable, no more so than its components, and his company obviously isn't a top software company. The chances that there will be a targeted attack on it that probes deeply enough to find flaws in that...well, by then, the company's pretty much screwed anyway; the attacker will find a way in.
On the other hand, if there's a flaw and the code is published, with references, any script kiddie who sees the exploit will think it's fun to go to the originating organization and haxx0rz their b0xx0rz.
So the sane way of GPLing the work, if it's obscure (and it is), is to do so without being traceable to the originator.
Why? The intent of the grandparent was clear: the President is too powerful, and the frequent transitions between Presidents, especially combined with the vast policy differences, are destabilizing.
Like Machiavelli said, each new ruler must prove himself*, usually in battle, so other rulers won't try to take over. So we get a war every eight years or so. If we didn't have a head of government, or if we removed our head of government's military authority, we'd probably be a much more stable country.
*Or herself. It's easier not to write both each time, and I'm lazy. I'm not a misogynistic bastard.
Then they'd guarantee support for KHTML/Safari, nothing else.
I know of at least one website that has three standards-compliant versions, one for each of Opera, Mozilla, and MSIE. If the code is _simple_ and standards-compliant, it'll render usefully in all browsers. If you want a certain look or you use obscure functions, you might have to write multiple versions.
That said, a simple JavaScript form such as the USCO probably needs should be easy to implement consistently with only one version of each page. USCO doesn't need anything that's terribly pretty or arcane.
Further evolution on Mars is much easier if we can provide a similar environment to ours and populate it. There's not much chance of any Earth organism larger than a microbe surviving native Mars conditions; after a serious terraforming effort, most Earth organisms will be able to settle on Mars with varying effectiveness. (I wonder how cheetahs would adapt to the lower gravity...)
Slashdot Mirror
The hyoid bone has a role in speech production? What planet are you from?
The most it could do is provide support for the larynx. The larynx has four functions in speech: providing silence, providing a buzzing noise or else letting air flow without noise (the difference between s and z), and creating the English h sound.
As long as H. neanderthalis had a similarly-shaped mouth, it would have been able to whisper in any language that you can speak. If it had a larynx similar to ours, it could speak as well. (Provided it had the mental capacity--speech is pretty specialized. Apes could speak English, too, if they had the appropriate brain structures.)
Yes, I am a linguist.
Evolution has no purpose, clod. Otherwise men wouldn't have nipples; it'd be more efficient to make that a sex-linked trait. (For males, at least.) And no creature until now could alter its own evolution.
The nasty thing about creationism is that it can't be tested. You can't disprove it, and lacking a time machine, you can't prove it.
On the subject of the flounder, its design didn't impair its survivability enough to cause its extinction, so we have flounders. Simple as that. And since it could burrow in sand (as other types of fish do, including many rays) while keeping an eye out for predators, it had slightly better survivability than other fish. Only slightly, or we'd have fewer types of fish.
In e17, you should be able to centre-click for a list of open windows, whether shaded, unshaded, or hidden.
Right you are. Thank you muchly.
I've gotten a lot of errors in GNOME that require either remote login (and I disable sshd for security) or a hard reset to fix. (Yes, sometimes that's necessary; what happens when you can't get to a terminal and the GUI's sitting on your commands to get to the console?) Mainly problems with media players, but not always. Also minor annoyances that require issuing a kill command from a terminal or console to close a malfunctioning window.
If Mandrake 9.2 fixed one reliable instability issue, then it would be more stable than 9.1, right?
How did I get modded troll? It was four years between minor releases of DR16.
Naah, it'll be 2007 before it's actually released.
True, though.
E17 already features real transparency. Just check out the drop shadows on the epplets. Majorly cool, but it doesn't work for actual applications yet--a design decision, no doubt, and one I hope they'll correct (or at least give options for).
I've been using E17 for the past few days. It's beautiful, and it's as stable as any desktop environment I've used--perhaps more so. Not all the features have been implemented; it still needs a menu editor to be really useful (or just tell me which config file to modify, and put one there by default), and I'd like to see an e17 terminal.
Still, it's lightweight, beautiful, features real transparency, and is unusually stable for being in heavy development.
Depends on the Linux. Ubuntu gets decent after about three hours (add universe and multiverse repositories; add mp3 support, abiword, autoconf, automake, etc); Gentoo takes two or three days.
On the other hand, Windows...you have to install nLite and make another install disk, then reinstall with only the features and services you want or need, then reinstall, then add applications.
Gaim reported a read error and wouldn't let me sign back on. Probably did.
They'll probably start allowing select people to join at first, as they did with gmail (perhaps based on gmail account seniority?) for feature reduction / addition requests. Whoever these people add to their buddy lists, gets an invitation.
It'd make sense, though.
LMI hasn't set foot in Swaziland.
Swaziland has trademark laws, apparently, but I can't find information about them online.
So if you have a Swazilandish company, feel free to trademark its name, even if it contains "Linux".
But if you have a company that's producing and marketing a Linux, $200 is probably the least of your expenses. You probably spend as much on pens in a year.
As has been pointed out, the restriction is only for people who use the word "Linux" in a product name. End users aren't affected.
I'd like a free trademark for Linux, but really, not even many Linux distributions need the word "Linux" in their name. Red Hat, Gentoo, Ubuntu, Yellow Dog, Source Mages...they all function well enough without the word "Linux" in their names. It's pretty much a moot point.
Off topic...
Anyone else get 503 errors when trying to reach Slashdot?
Where do you go to talk about Slashdot being Slashdotted?
MD5sums are expressed in base-17. You get values from 0 to 9 and from a to f. So if you l33t it carefully and only use letters a-f, sure.
I'm sorry, I didn't see any reason why someone would switch to Solaris in that editorial. It was mainly minor bitching about the details of installation and Sun's GUI choices.
Writing Perl isn't a problem.
Reading Perl is a problem, when you're learning it. Reading Python is easier than reading C.
The grandparent is looking for a fast solution--one that he doesn't have to spend a lot of time on. Debugging something that looks like line noise isn't easy, especially since his experience is probably focussed on C-style syntaxes. So it's probably better in his case to use Python.
If you're implementing a large-scale program that involves heavy text manipulation, then you'll want to use Perl. But this project isn't a major thing--it's just there to automate a portion of a sysadmin's work.
The research for the AIDS cocktail has been done, and it's making companies somewhere between five and fourteen thousand per patient per year. That was the GP's point.
A one-time cure for AIDS would net a biotech firm maybe as much as a year on the cocktail. Worse, it could provide immunity, and at the least it'd give the person a strong incentive to practice safe sex. Compare that to ten or fifteen years per patient, and you're talking about a 90% reduction in profits (after a temporary boom).
"Security flaws have a way of coming out, code or no code."
This is true for popular products. Note that the article was asking about a framework over existing libraries; it probably isn't too vulnerable, no more so than its components, and his company obviously isn't a top software company. The chances that there will be a targeted attack on it that probes deeply enough to find flaws in that...well, by then, the company's pretty much screwed anyway; the attacker will find a way in.
On the other hand, if there's a flaw and the code is published, with references, any script kiddie who sees the exploit will think it's fun to go to the originating organization and haxx0rz their b0xx0rz.
So the sane way of GPLing the work, if it's obscure (and it is), is to do so without being traceable to the originator.
Yes, but it's only if they explicitly request a specific record. Libraries don't like serving this type of information.
Why? The intent of the grandparent was clear: the President is too powerful, and the frequent transitions between Presidents, especially combined with the vast policy differences, are destabilizing.
Like Machiavelli said, each new ruler must prove himself*, usually in battle, so other rulers won't try to take over. So we get a war every eight years or so. If we didn't have a head of government, or if we removed our head of government's military authority, we'd probably be a much more stable country.
*Or herself. It's easier not to write both each time, and I'm lazy. I'm not a misogynistic bastard.
Then they'd guarantee support for KHTML/Safari, nothing else.
I know of at least one website that has three standards-compliant versions, one for each of Opera, Mozilla, and MSIE. If the code is _simple_ and standards-compliant, it'll render usefully in all browsers. If you want a certain look or you use obscure functions, you might have to write multiple versions.
That said, a simple JavaScript form such as the USCO probably needs should be easy to implement consistently with only one version of each page. USCO doesn't need anything that's terribly pretty or arcane.
I'm not sure it would be healthy to keep her awake for over a year.
Further evolution on Mars is much easier if we can provide a similar environment to ours and populate it. There's not much chance of any Earth organism larger than a microbe surviving native Mars conditions; after a serious terraforming effort, most Earth organisms will be able to settle on Mars with varying effectiveness. (I wonder how cheetahs would adapt to the lower gravity...)
That's the primary reason, imhoe.
It's easier to write drivers than to write an operating system and drivers.