Like it or not, Welsh is the native tongue, English is an import brought in during the conquests.
"Native tongue" could mean a lot of things, I guess. If it means "the langauge people spoke in a given place several generations ago," my "native tongue" would probably be Shawnee, maybe Iroquois depending on how far back you want to go.
Guess I had better hit the books! Before they change the street signs and all.
Try saying that in Wales and see how long it takes before someone pops you one.
While Fear Of All That Is Welsh is not a prime motivating factor for the typical American, I should point out that I'm all for Welsh independence, removing Wales from under the boot of English tyranny, and all that. I'm pretty sure Welsh will remain just a curiousity as a language and I'm not clear on what the benefit of bringing it back in a really strong way would be.
Sure, but when you talk about someone's "native tongue" you are ordinarily talking about the language they and their neighbors grew up speaking. In this case, that ain't Welsh.:)
Once GIMP people implement 48bit color and color management, they'll have a potential to take away a large portion of Adobe clientele - web designers and photographers (i.e. people in no way related to prepress and CMYK). When two products have equal capabilities in relation to your tasks, but one is $650 and one is free, the choice becomes really simple.
Once the GIMP is not a bloody abortion with regards to user friendliness, some of that might start to matter.
Just to add to the confusion, you can also use pkg-get with blastwave.org, and you get yet another path you need to add to your, er, path. Blastwave is much more of a community effort, until very recently the guy who maintains Sunfreeware refused to take packages from anyone and created them all himself.
So you get a lot of different namespaces for the solaris stuff, the legacy SunOS stuff, the sfw stuff, and the csw (blastwave) stuff. It is an ugly pain in the ass but it is a good way to keep separate all sorts of different software.
Sure, I know how to hand-hack everything, but why does Solaris make me keep around checklists to do all this stuff after an install when they could've just done it themselves?
A tradition of relying less on scripts in packages, a tradition of letting each user have their own settings, and in some cases a difficulty in guessing what the appropriate order might be when binaries with the same name exist.
If OpenSolaris works out okay, with custom distributions available, some of these problems will probably go away.
The cool thing about OpenSolaris is that people will soon be able to make really detailed analysis of the engineering tradeoffs between jails, Xen, and zones. There might end up being some other cool things you can do, with a little hacking. There is already a project out there (can't remember the name) to allow FreeBSD to run in a Solaris zone.
Then who do you suggest does this? Have you ever told your boss (if you are a sysadmin) that you won't do something because it's "trivial crap"?
Somehow you've understood my statement to mean about the opposite of what I said. Everyone who uses a *nix machine professionally in a technical capacity should be able to set the path. Everyone ought to do it when it's appropriate.
Even though it seems wacky to me personally, I would not have criticized the guy for calling a sysadmin for help solving the trivial problems. But reinstalling the OS? WTF.
So do YOU know how to talk directly to chips on the ISA bus
Yeah, but when I do they talk back to me, and tell me to do... terrible things.:(
Re:struggling with solaris 10 for the last week
on
Take A Look At Solaris 10
·
· Score: 3, Insightful
Personally I fail to see how one has anything to do with the other. Writing a driver is system level programming. Setting up paths, shells and patches is system administration. While some people can be good at both, most people are generally only good at one. If you are one of the former, then we bow to your superior intellect.
Horseshit. "Setting up paths, shells and patches" is the idiot work of system administration. It is the stuff you learn on the first day or two of the job. Redefining system administration to even include trivial crap like figuring out $PATH dumbs down the profession.
A programmer should know how to administer his own machine.
Re:struggling with solaris 10 for the last week
on
Take A Look At Solaris 10
·
· Score: 3, Insightful
After a bit of frustration with trying to setup paths for root, and login shells, and patches, and packages. I decided to just clean install solaris 10.
In other words, you do not know what you are doing. And you are writing drivers.
The North Korean army is a joke. Oh, they have a lot of manpower, which is useful for keeping domestic peace (you won't see large unarmed civilian uprisings in North Korea), but that hardly says anything about how capable it would be in fighting any of its neighbors.
That is a pretty gross oversimplification of the situation. First, it's important to recognize that North Korea's military is set up to be a primarily defensive force, meant to put an enemy opponent through a meatgrinder if they attempt an invasion. Nobody wants to send troops into North Korea. Second, the key to their situation is that they can flatten Seoul in about an hour with their conventional artillary. That has been their "mutually assured destruction" equivalent for a long time. With a nuke and a delivery system they'd have a similar deterrant capability with regard to Japan.
They aren't setup to invade anybody, really, that is true. Although South Korea looks like a pretty soft target if the US decides not to protect it, or is incapable of protecting it because they are fully engaged elsewhere.
In short, if North Korea decided to make a move right now, it is likely that they would get squashed by several military powers simultaneously...
That would be a lot more comforting if the people running that country were rational actors.
with a very strange Sino-Japanese alliance putting it down along with a very powerful South Korean army in its own right.
Wouldn't China love to see the whole peninsula communist?
It'll be interesting to see how wars are conducted when both populations exist in an inhospitable wasteland that can't support their existance for more than 30 seconds without critical and easily-targeted infrastructure.
The Japanese are still embarassed by the last war they started, but they understand the need to get involved the "fighting amongst ourselves" so that it can be stopped.
I can't speak to the embarassment part, but until our fearless leader convinced them to send troops to Iraq postwar Japan was content to be a very pacifist nation with a self-defense military. I predict that will have some entertaining side-effects in the decades to come, although I can't judge its future ranking on the "Dubya, Gosh THAT Was Stupid" historical chart.
The Right to Privacy is, in my opinion, a perfect reasonable example of an unenumerated right, a la the 9th Amendment. Deciding that abortion falls under said privacy right, however, was in my opinion bad precedent. It pretty much opens the door to including anything under such a vast, unlimited "none of your beeswax" umbrella.
What else is there going on inside your body which some do not consider private?
Interesting, but "well regulated" in the specific context of the 2nd Amendment means "practiced and competent", as in regular troops; as opposed to irregulars, which were basically anybody who showed up with a sharp stick or club and no clear idea how to use it.
Doesn't that imply a certain kind of gun control would be assumed, i.e. the state determining who is competant to use a gun and who is not? Or was the assumption that everyone would train on their own?
No. It most places in the US you do not have to prove that you are a US Citizen to vote. A lot of them only require a photo id and/or an utility bill.
I guess it depends on the state. In Ohio, you can't register without a license or state ID, and you can't get one of those without being a citizen. I'm pretty sure aliens have a different license if they want to drive.
If the code isn't transparent, it doesn't matter what the coder's background is.
Logical fallacy there? You're not addressing anything I've said, and I happen to agree completely.
I wouldn't design a process solely to prevent such an occurrence, and the process proposed in the legislation won't achieve that anyway.
Yeah. I think you just basically want a good and open engineering process. They seem to at least have the right idea, and I don't know how much of the legislation actually INTERFERES with that.
The legislation should focus on ensuring that this process is open and verifiable. It appears instead that the proposed legislation is written by people who have no understanding of process integrity,
It is interesting you should say that. I got a different impression, that the legislation was written by people who know a lot about process integrity, but working under a different paradigm: lawyers. The whole "chain of evidence" thing seemed like a giveaway to me.
The employer would just as well spend the money on horoscopes, graphology or having the candidate's aura read. Employers use it not because it's useful, but because it's there.
That seems pretty silly to me. It's at the very least useful to know if someone working for you has a criminal history including embezzlement or homicide. Employers use it because in this regulatory and liability environment, they have to.
The really great thing about our current environment is, you can call a person's former employer and (in most states, anyhow) they are not allowed to say "we fired so-and-so for embezzlement and pursued charges." Joy.
Above the level of "supervisor" or "team leader" managers need to have skills in management first. I'm sure I'm not the only one who has worked for people who were brilliant but completely incapable of managing me or my coworkers, either because of a disdain for the simple work of management or poor "people skills."
Slashdot Mirror
Chilling. This means she had a key role in the sinking of two of the great American private research institutions.
Let's send her to IBM next. I am sure she can accomplish great things there.
"Native tongue" could mean a lot of things, I guess. If it means "the langauge people spoke in a given place several generations ago," my "native tongue" would probably be Shawnee, maybe Iroquois depending on how far back you want to go.
Guess I had better hit the books! Before they change the street signs and all.
While Fear Of All That Is Welsh is not a prime motivating factor for the typical American, I should point out that I'm all for Welsh independence, removing Wales from under the boot of English tyranny, and all that. I'm pretty sure Welsh will remain just a curiousity as a language and I'm not clear on what the benefit of bringing it back in a really strong way would be.
Sure, but when you talk about someone's "native tongue" you are ordinarily talking about the language they and their neighbors grew up speaking. In this case, that ain't Welsh. :)
Once the GIMP is not a bloody abortion with regards to user friendliness, some of that might start to matter.
Gnahck!
English is the native tongue of Wales. Welsh is a historical curiousity. Maybe the Welsh intend for it to be more than that, eventually, I don't know.
Just to add to the confusion, you can also use pkg-get with blastwave.org, and you get yet another path you need to add to your, er, path. Blastwave is much more of a community effort, until very recently the guy who maintains Sunfreeware refused to take packages from anyone and created them all himself.
So you get a lot of different namespaces for the solaris stuff, the legacy SunOS stuff, the sfw stuff, and the csw (blastwave) stuff. It is an ugly pain in the ass but it is a good way to keep separate all sorts of different software.
A tradition of relying less on scripts in packages, a tradition of letting each user have their own settings, and in some cases a difficulty in guessing what the appropriate order might be when binaries with the same name exist.
If OpenSolaris works out okay, with custom distributions available, some of these problems will probably go away.
The cool thing about OpenSolaris is that people will soon be able to make really detailed analysis of the engineering tradeoffs between jails, Xen, and zones. There might end up being some other cool things you can do, with a little hacking. There is already a project out there (can't remember the name) to allow FreeBSD to run in a Solaris zone.
:)
Remains to be seen if that will work.
Somehow you've understood my statement to mean about the opposite of what I said. Everyone who uses a *nix machine professionally in a technical capacity should be able to set the path. Everyone ought to do it when it's appropriate.
Even though it seems wacky to me personally, I would not have criticized the guy for calling a sysadmin for help solving the trivial problems. But reinstalling the OS? WTF.
Yeah, but when I do they talk back to me, and tell me to do... terrible things.
Horseshit. "Setting up paths, shells and patches" is the idiot work of system administration. It is the stuff you learn on the first day or two of the job. Redefining system administration to even include trivial crap like figuring out $PATH dumbs down the profession.
A programmer should know how to administer his own machine.
In other words, you do not know what you are doing. And you are writing drivers.
Great!
That is a pretty gross oversimplification of the situation. First, it's important to recognize that North Korea's military is set up to be a primarily defensive force, meant to put an enemy opponent through a meatgrinder if they attempt an invasion. Nobody wants to send troops into North Korea. Second, the key to their situation is that they can flatten Seoul in about an hour with their conventional artillary. That has been their "mutually assured destruction" equivalent for a long time. With a nuke and a delivery system they'd have a similar deterrant capability with regard to Japan.
They aren't setup to invade anybody, really, that is true. Although South Korea looks like a pretty soft target if the US decides not to protect it, or is incapable of protecting it because they are fully engaged elsewhere.
That would be a lot more comforting if the people running that country were rational actors.
Wouldn't China love to see the whole peninsula communist?
So they're in Iraq... why? You make it sound as though Iraq were a threat to someone other than Iran, Israel, or Kuwait, which is complete nonsense.
Briefly?
That sounds pretty interesting. Could you report on that? And remember, we're putting the coversheets on the TPS reports before they go out now.
So, if you could just remember to do that from now on that'd be great.
I can't speak to the embarassment part, but until our fearless leader convinced them to send troops to Iraq postwar Japan was content to be a very pacifist nation with a self-defense military. I predict that will have some entertaining side-effects in the decades to come, although I can't judge its future ranking on the "Dubya, Gosh THAT Was Stupid" historical chart.
Which it isn't.
What else is there going on inside your body which some do not consider private?
Doesn't that imply a certain kind of gun control would be assumed, i.e. the state determining who is competant to use a gun and who is not? Or was the assumption that everyone would train on their own?
I guess it depends on the state. In Ohio, you can't register without a license or state ID, and you can't get one of those without being a citizen. I'm pretty sure aliens have a different license if they want to drive.
The black helicopters are on the way. Resistance is futile.
Good day!
Logical fallacy there? You're not addressing anything I've said, and I happen to agree completely.
Yeah. I think you just basically want a good and open engineering process. They seem to at least have the right idea, and I don't know how much of the legislation actually INTERFERES with that.
It is interesting you should say that. I got a different impression, that the legislation was written by people who know a lot about process integrity, but working under a different paradigm: lawyers. The whole "chain of evidence" thing seemed like a giveaway to me.
That seems pretty silly to me. It's at the very least useful to know if someone working for you has a criminal history including embezzlement or homicide. Employers use it because in this regulatory and liability environment, they have to.
The really great thing about our current environment is, you can call a person's former employer and (in most states, anyhow) they are not allowed to say "we fired so-and-so for embezzlement and pursued charges." Joy.
Above the level of "supervisor" or "team leader" managers need to have skills in management first. I'm sure I'm not the only one who has worked for people who were brilliant but completely incapable of managing me or my coworkers, either because of a disdain for the simple work of management or poor "people skills."