Given how buggy Windows is at switching languages (I can't count how many times I've changed the langauge, switched the window, then started typing only to find that Windows is using the previously selected language), having the keys on the keyboard change would greatly assist in knowing the currently selected language. Well, that and you can see which keys you're typing.;-)
If you look down at the taskbar, you can see the two character locale ID. If not, got Regional and Language options in control pane and make sure "Show Language Bar" is checked. Minimise it and it will dock in the taskbar.
Play with it, and you can see it's per process, and so "changing it and switching windows" will behave exactly the way you describe, every time.
It's not buggy though, you just don't understand that the locale is a property of each process, not the whole system.
Isn't the point about LSB that it allows binary packages?
If people want to release source code, they'll do it anyway, and people will port it. But binary applications, which are allowed by the GPL, are impossible unless you have things like LSB. You'd need a lot more of course, like being having a stable ABI with enough libraries to build GUI applications.
If some vendor has an application which they won't (or can't since they don't have rights to redistribute libraries as source code) release as source code, if there is no stable ABI they won't release it on Linux, it's as simple as that.
Where can I locate the anonymous "Air Force visitor" who always gets trotted out as "proof" the inventor isn't a crackpot?
I've met him. Actually he flys off at great speed in a small silver sphere after reassuring himself that the inventor *is* a crackpot. He's not really from the air force though.
The only problem with this propulsion method is that you need an awful number of photons, and you wouldn't like to be in a spot that they hit. Some writers theorized that the Solar system would need an energy shield before it can launch a photon-driven starship from anywhere close to it.
But that's no problem! I found some dude with a very colorful website who can make an energy shield. Then again, that works as an inertial damper too, so you could just put one on the spaceship and you wouldn't need so many photons.
Good job Linus deleted the 'or a later version at your discretion' clause really, isn't it?
Otherwise in 10 years time it would be licensed under a GPLv10 license, where contributors have to give up their paid jobs, move to Stallman's compound in Waco and donate all their cheetos to the communal food store next to his Sparc station.
The average performance improvement we have seen from Athlon 64 FX-62 equaled 16%, while Core 2 Extreme X6800 demonstrated only 10% average performance boost. This way, there is a certain difference: AMD K8 turns out 6% mode efficient in 64-bit mode than Intel Core. However, this difference cannot compensate for the 20% performance advantage of the Intel Core 2 Duo over the Athlon 64 X2 working at the same clock speed, which we have pointed out in our previous articles. Therefore, we will not change our conclusions about the performance of the new Intel processors even keeping in mind the upcoming launch of 64-bit Windows Vista OS family.
I have an Athlon now and it's stable and fast, but the fans are loud. But initially I had more stability issues (problems with generic SDRAM, flaky firewire, overheating hard disks) on an Athlon/Nforce2 than I was used to on an Celeron/Intel 440BX. Even if Intel was a bit slower, I'd probably pick an Intel CPU and chipset over any other combination, since most stuff isn't very CPU bound these days.
Why didn't the call it the "Bad Ass" motherboard? That's the sort of hip, ironic yet edgy brand image that Intel need to take back the gaming market from AMD.
They could publish "buttmark" synthetic benchmarks too.
Got to say for once, Intel have a superior product (if they're really lucky, it might be competive with the K8L, if not they have the resources for Core3) but their marketing sucks.
That's not Godwin's law, at least in not in the sense of comparing your opponent to the Nazis. Here's an example of Godwin's law in this context :
BurnEmacsHeretics: The world would be a lot simpler if everyone learnt VI. Then I would need to write scripts to auto uninstall Emacs on my boxen, or have my black clad, goosestepping lab monitors break the fingers of anyone who installs it. Plus I wouldn't need to bug users home internet connections to see if they are finding ways to get around the scripts. GasAllViUnternmenschen: Oh, I see. Ein Lab, Ein Sysadmin, Ein Editor. Fukk you, Hitler!
According to the ever informative,interesting and insightfulwikipedia
The spoof band Spnal Tap raised the stakes in 1984 by using an umlaut over the letter N, a consonant (it also makes use of a dotless i). This is a construction found only in the Jacaltec language of Guatemala and in some orthographies of Malagasy, although it is uncertain whether the writers of This Is Spinal Tap knew this at the time.
Note, this post has informed you aboout the Jacaltec language of Guatemala and (if you view the HTML source) the uses of U+308 aka ̈ the combining diaresis
I went from Basic to Assembler to C. C was a breath of fresh air.
The problem I have with computer 'scientists' slagging off Basic is that all the stuff they say is based on subjective aesthetics. They don't seem to understand anything at the hardware or even assembler level, and they don't seem to build up theories that has been tuned by experiments like real scientists.
E.g. the idea that GOTO is somehow inherently bad is completely bogus. C compilers user JMP instructions all the time, it's the same thing. Of course, the Basic-ism of using GOTOs all over the place, passing parameters to GOSUB'd procedures in global variables is horrible. In fact it's worse than assembler, where you can get parameters and local variables by using the stack and registers. But there are legitimate reasons for JMPing, which is why the processor supports it, and why C as a sort of portable assembler does too.
In early, in order non superscalar, Risc chips branch delay slots are natural, since the instruction following the branch has almost completed execution by the time the branch is taken.
Later chips, notable Alpha, don't do this because the number of natural branch delay slots would vary with implementation. To avoid it, you need to add logic to stall the pipeline until the branch result is known. The idea behind MIPS was to build a simple processor without this logic that could be clocked at enormous frequencies - the original acronym was "Microprocessor without Interlocked Pipeline Stages".
It's not really a problem, the compiler can usually schedule an instruction there, and if not the NOP doesn't take any time to execute.
Slashdot Mirror
Given how buggy Windows is at switching languages (I can't count how many times I've changed the langauge, switched the window, then started typing only to find that Windows is using the previously selected language), having the keys on the keyboard change would greatly assist in knowing the currently selected language. Well, that and you can see which keys you're typing. ;-)
If you look down at the taskbar, you can see the two character locale ID. If not, got Regional and Language options in control pane and make sure "Show Language Bar" is checked. Minimise it and it will dock in the taskbar.
Play with it, and you can see it's per process, and so "changing it and switching windows" will behave exactly the way you describe, every time.
It's not buggy though, you just don't understand that the locale is a property of each process, not the whole system.
Shouldn't you be posting as an AC?
Sorry, just kidding.
Isn't the point about LSB that it allows binary packages?
If people want to release source code, they'll do it anyway, and people will port it. But binary applications, which are allowed by the GPL, are impossible unless you have things like LSB. You'd need a lot more of course, like being having a stable ABI with enough libraries to build GUI applications.
If some vendor has an application which they won't (or can't since they don't have rights to redistribute libraries as source code) release as source code, if there is no stable ABI they won't release it on Linux, it's as simple as that.
Don't be a vagina, name calling should not denigrate the male gender.
I was being sarcastic, proposing Starship Troopers style military control of government as a way to allow DARPA to stop wars.
I read Starship Troopers, and more importantly saw the film which does a good job satirising the ideas from the book.
The art of trolling has declined, to the point where a one line flamebait post is moderated as troll. A good troll is so much more than that.
8 86346
Like this for example, my all time favourite
http://ask.slashdot.org/comments.pl?sid=6823&cid=
If Swift were alive today, he'd be trolling slashdot.
Easy, only veterans should be allowed to vote and run for office.
Where can I locate the anonymous "Air Force visitor" who always gets trotted out as "proof" the inventor isn't a crackpot?
I've met him. Actually he flys off at great speed in a small silver sphere after reassuring himself that the inventor *is* a crackpot. He's not really from the air force though.
The only problem with this propulsion method is that you need an awful number of photons, and you wouldn't like to be in a spot that they hit. Some writers theorized that the Solar system would need an energy shield before it can launch a photon-driven starship from anywhere close to it.
But that's no problem! I found some dude with a very colorful website who can make an energy shield. Then again, that works as an inertial damper too, so you could just put one on the spaceship and you wouldn't need so many photons.
Yeah, you were just trying to do your job ferrying nukes to cities, and those dicks in F14s kept trying to shoot you down.
Good job Linus deleted the 'or a later version at your discretion' clause really, isn't it?
Otherwise in 10 years time it would be licensed under a GPLv10 license, where contributors have to give up their paid jobs, move to Stallman's compound in Waco and donate all their cheetos to the communal food store next to his Sparc station.
Do you think your appearance is pleasing to us, human?
I never realised before that it was possible to fail a Rorschach test.
The only thing the Tomcat was intended to "kill" were enemy bombers.
And who was flying the bombers? PEOPLE!
I bet the enemy pilots feel the same way.
http://www.xbitlabs.com/articles/cpu/display/core
Their conclusion
I have an Athlon now and it's stable and fast, but the fans are loud. But initially I had more stability issues (problems with generic SDRAM, flaky firewire, overheating hard disks) on an Athlon/Nforce2 than I was used to on an Celeron/Intel 440BX. Even if Intel was a bit slower, I'd probably pick an Intel CPU and chipset over any other combination, since most stuff isn't very CPU bound these days.
Why didn't the call it the "Bad Ass" motherboard? That's the sort of hip, ironic yet edgy brand image that Intel need to take back the gaming market from AMD.
They could publish "buttmark" synthetic benchmarks too.
Got to say for once, Intel have a superior product (if they're really lucky, it might be competive with the K8L, if not they have the resources for Core3) but their marketing sucks.
You could tell the person making the argument to STFU NOOB.
That would make them mute.
Image macros with cute animals end any argument on the internet, everyone knows that.
That's not Godwin's law, at least in not in the sense of comparing your opponent to the Nazis. Here's an example of Godwin's law in this context :
BurnEmacsHeretics: The world would be a lot simpler if everyone learnt VI. Then I would need to write scripts to auto uninstall Emacs on my boxen, or have my black clad, goosestepping lab monitors break the fingers of anyone who installs it. Plus I wouldn't need to bug users home internet connections to see if they are finding ways to get around the scripts.
GasAllViUnternmenschen: Oh, I see. Ein Lab, Ein Sysadmin, Ein Editor. Fukk you, Hitler!
Note, this post has informed you aboout the Jacaltec language of Guatemala and (if you view the HTML source) the uses of U+308 aka ̈ the combining diaresis
Umulated is when you emulate an umlaut on an pure ASCII system by replacing ü with ue. Or ö with oe.
// can someone else think of some examples that don't make German's spit their coffee?
#ifndef READER_IS_GERMAN
An example
E.g. Göring -> Goering, or Führer to Fuehrer.
#else
#endif
Maybe he could join Theo's project. Seems crazy to let ego get in the way of the important work of developing software.
Read this
0 10.html
http://www.adequacy.org/stories/2001.10.2.33542.4
Now for each reply to your post, see if the LFT threshold is reached. Flame the shit out of any that do.
Way more fun than F.E.A.R or Doom3. And people complain that Linux users can't play games.
I went from Basic to Assembler to C. C was a breath of fresh air.
The problem I have with computer 'scientists' slagging off Basic is that all the stuff they say is based on subjective aesthetics. They don't seem to understand anything at the hardware or even assembler level, and they don't seem to build up theories that has been tuned by experiments like real scientists.
E.g. the idea that GOTO is somehow inherently bad is completely bogus. C compilers user JMP instructions all the time, it's the same thing. Of course, the Basic-ism of using GOTOs all over the place, passing parameters to GOSUB'd procedures in global variables is horrible. In fact it's worse than assembler, where you can get parameters and local variables by using the stack and registers. But there are legitimate reasons for JMPing, which is why the processor supports it, and why C as a sort of portable assembler does too.
In early, in order non superscalar, Risc chips branch delay slots are natural, since the instruction following the branch has almost completed execution by the time the branch is taken.
Later chips, notable Alpha, don't do this because the number of natural branch delay slots would vary with implementation. To avoid it, you need to add logic to stall the pipeline until the branch result is known. The idea behind MIPS was to build a simple processor without this logic that could be clocked at enormous frequencies - the original acronym was "Microprocessor without Interlocked Pipeline Stages".
It's not really a problem, the compiler can usually schedule an instruction there, and if not the NOP doesn't take any time to execute.