Where do you get off saying something like, "I for one think it's about time"? Did you contribute even a single line of code to get it to this point? Please show a little gratitude to the developers. They're volunteers, after all.
The old architecture didn't allow it because of some technical difficulty due to privilege separation. It's not arrogance, it's just that microkernel design fits some things better than others.
CSS is only considered by M$ to be a "flawed standard" because they didn't have enough input in setting the standard in a way that makes it easy for them to take the standard in a narrow-minded direction. This is the rebellion of a netizen that is not happy when other bodies start setting the standards for once.
Xen 2.0 requires the OS to run in ring 1. This results in a few % performance decrease in most tasks. Is this enabled by default? Or is it some commandline option?
It's all the spyware that Microsoft inserted while you weren't looking. It's a ploy by Microsoft to buy Novell through their involvement with Mono, and infiltrate the CVS repositories that Novell share with RedHat. One small step for Microsoft, one giant leap for Big Brother.
...and for real standards compliance, you'll have to wait for IE20. Or maybe IE21. By that time no web developer on the face of the planet will have any hair left.
Thank you to the US government for offering to beta-test security patches for the rest of us. Thank you to Microsoft for waiting a month before releasing those patches to everybody else. I'm so glad you don't risk fixing security holes in the general public before you have thoroughly tested the fixes with government machines. It makes me feel all warm and fuzzy knowing that I'm safe because George W. Bush's PC is running your latest software before mine is. (If I ran Windows, that is.)
Most users do not actually know what they want, despite the fact that they think they do. If you were to implement what they asked for, they would probably come back and say, "That's not what I asked for!" And you'd say, "Yes it is." And they'd say, "Well, that's not what I meant." Pick any of a number of huge, high-profile software projects that have been canceled due to budget and time overruns, feature creep, bug pandemics, etc., and you will find that one of the major problems is that the customer's requirements changed constantly, because the customer did not know what they really wanted from the beginning to the end, or because their requirements or understanding changed as they saw things implemented.
Users may not understand what they want because so much of what they do in using the system is subconscious, and we humans are *not* aware of our subconscious processes. Some of it is even "hardware" rather than "software", e.g. in our visual system, and we absolutely cannot reverse-engineer our hardware by introspection. Try to figure out how you read handwritten words sometime. No, really try and figure it out. Then try to write a program to do handwriting recognition the same way humans do it. I know what this entails, because I've spent a few years actually trying to understand how humans work and build such a system. We humans just don't get our own thought processes. This is why usability studies are more important than implementing whatever feature you *think* will be cool.
Even if the user knew exactly what they wanted, it may be completely impractical to implement, due to programming contstraints.
Even if the user knew exactly what they wanted, they probably don't know how to succinctly describe it to the programmer. It's a language problem and a communication problem. It's also a point-of-view problem (relativism).
Humans are all very, very different. Ask 100 people to give you a list of the music that they think the rest of the world should listen to. You will *not* find a consensus. But there are songs that almost everybody likes. And there are multiple radio stations if you don't like a certain genre, but you like another instead (think KDE vs. GNOME).
GNOME got to a point where something had to be done to take it in a specific direction. The direction it took stands to benefit the most people in the most profound way. Personally I'm glad that they moved ahead the way they did. The KDE community is currently locked somewhat in stasis, because there are too many opinions, too much entropy, and no single consensus as to how to move forward. I'm not talking about making small changes, those are happening, and KDE is implementing some great features, I'm talking about the lack of major new directions for KDE such as what is happening in GNOME. That will change, a consensus will arise, and KDE will move forward in a major new direction at some point in the future.
Until then, try taking GNOME 1.0-GNOME 1.2 and extrapolate the situation that existed then to produce a hypothetical view of the way things would be now if a few core GNOME hackers hadn't done something. It would be a real mess of mismatching pieces. It might be a hacker-boy-cool mess, but it would be a mess. GNOME-2.10 is clean, lean, and most importantly consistent, and a better fit for how our subconscious processes understand information.
Besides, if they're the ones writing the code, I say they can do whatever they want with it.
And Gnome is so great that programmers have gotten into the habbit of bypassing it and using only GTK
This is by design. The goal is to make a GNOME app a GTK app, and vice versa, by moving critical/useful stuff for all apps into GTK, and making everything else just "value-added" and "automatically utilized" if extra GNOME libs are present.
Avogadro's number, also called Avogadro's constant (N_A) is a large mathematical constant used in chemistry, formally defined as the number of carbon-12 atoms in 0.012 kg of carbon-12.
So the kilogram will now be defined in terms of a constant that is defined in terms of kilograms.
Isn't it dangerous to evaluate JSON on the js side by calling Javascript's eval() ? The server could be returning anything, not just JSON-valid JS syntax.
Mind you, if there's a non-JSON JS exploit that could be taken advantage, I guess you could put it straight into JS code in the HTML, and the user would be just as vulnerable as if the exploit were run using eval().
Granted you cat take this too far
Exactly.
Compare the 386 or older pentiums to the P4, clock-cycle-for-clock-cycle.
Oh wait. That's basically the same thing as comparing the Pentium-M to the P4:o)
Intel was extremely dishonest in its design of the P4. They pushed the pipeline from around 10 stages to around 23 stages. This goes against everything you will ever learn in any engineering class about pipeline design -- as soon as there is a branch instruction (of which there are a ton in x86 code -- it is much less efficient about this than say the ARM), the whole pipeline has to be flushed, so you get a huge latency hit for every condition. The pipeline flush isn't so bad with speculative evaluation / branch prediction.
The whole reason Intel lengthened the pipeline is that it allowed them to push clockspeeds up further (because less work had to be done per clock cycle), and people bought CPUs based on clock speed. This gave them temporary headway against AMD, although clock cycle for clock cycle, the P4 was the least efficient processor I think anyone has ever released. More efficient branch prediction, as well as advances like hyperthreading, helped a little, but AMD chips were actually still in the lead performancewise, even though the clock speeds were much lower.
The Pentium-M was apparently based on an earlier (Pentium-Pro?) architecture, but wasn't even designed by Intel directly -- they contracted out to a company in Israel (anyone know the details?). That team focussed on actual processor efficiency rather than devious marketing tactics, and hence the clock speeds of the Pentium-M are comparable to AMD offerings, and Intel finally bit the bullet and started using model numbers like AMD had to to originally compete with Intel's FUD. Intel finally acknowledges that it isn't just CPU speed that counts.
The Pentium-M is the first Intel processor I have liked since Intel started being evil several years ago.
Don't ever try to open a camera case, either out of curiosity or to fix it. No matter how careful you are, you're likely to get a massive shock from the flash unit that could kill you if it passed through the wrong part of your body. I have been fixing gadgets for years, and have had two massive shocks when I opened cameras to fix them.
Great. Just what we need. There are a lot of programmers that will try to take advantage of multiple cores, but very few programmers are able to write properly-threadsafe code. Bring on the bugs.
The Japanese are way ahead of us in trying out this little socialogical experiment [Link]:
Karoshi - Japanese for Death from Overwork
Karoshi (...) (pronounced/karo:Si/), which can be translated quite
literally from the Japanese as death from overwork, is occupational sudden
death. The major medical causes of karoshi deaths are heart attack and
stroke due to stress.
The first case of karoshi was reported in 1969 with the death from a
stroke of a 29-year-old married male worker in the shipping department of
Japan's largest newspaper company. It was not until the latter part of the
1980s, however, when several high-ranking business executives who were still
in their prime years suddenly died without any previous sign of illness,
that the media began picking up on what appeared to be a new phenomenon.
This new phenomenon was quickly labelled karoshi, and once it had a name and
its symptoms were described and popularized, it was immediately seen as a
new and serious menace for people in the work force. In 1987, as public
concern increased, the Japanese Ministry of Labour began to publish
statistics on karoshi.
Usually, Japan's rise from the devastation of World War II to economic
prominence in the post-war decades has been regarded as the trigger for what
has been called a new epidemic. It was recognized that employees cannot work
for up to twelve hours a day six or seven days a week, year after year,
without suffering physically as well as mentally.
Meanwhile, death-by-overwork lawsuits have been on the rise in Japan,
with the deceased person's relatives demanding compensation payments.
However, before compensation can be awarded, the labour inspection office
must acknowledge that the death was work-related.
In Korea, where a Confucian-inspired work ethic involves much of the
adult populace, both male and female, in a six-day workweek with long hours,
this phenomenon is known as kwarosa (Hangul, [...]), a word derived from the
same Chinese characters as its Japanese equivalent ([...], ka, being the Chinese
character for exceed, [...], rou, for labor, and [...], shi, for death).
The prototype is equipped with 7 cameras on the body and a 12-inch LCD monitor in the front and another in the rear seat area.
You'll never need to look out the window again.
Slashdot Mirror
With SELinux, just block net access to the acroread binary. Or use Evince.
I wish people wouldn't post, you know, real stories on April 1st. Boycott reality for a day. It causes confusion.
Where do you get off saying something like, "I for one think it's about time"? Did you contribute even a single line of code to get it to this point?
Please show a little gratitude to the developers. They're volunteers, after all.
The old architecture didn't allow it because of some technical difficulty due to privilege separation. It's not arrogance, it's just that microkernel design fits some things better than others.
CSS is only considered by M$ to be a "flawed standard" because they didn't have enough input in setting the standard in a way that makes it easy for them to take the standard in a narrow-minded direction. This is the rebellion of a netizen that is not happy when other bodies start setting the standards for once.
Xen 2.0 requires the OS to run in ring 1. This results in a few % performance decrease in most tasks. Is this enabled by default? Or is it some commandline option?
Or maybe it's debugging symbols? Or just GCC 4.0?
It's all the spyware that Microsoft inserted while you weren't looking. It's a ploy by Microsoft to buy Novell through their involvement with Mono, and infiltrate the CVS repositories that Novell share with RedHat. One small step for Microsoft, one giant leap for Big Brother.
It's not even April 1st yet.
...and for real standards compliance, you'll have to wait for IE20. Or maybe IE21. By that time no web developer on the face of the planet will have any hair left.
Thank you to the US government for offering to beta-test security patches for the rest of us. Thank you to Microsoft for waiting a month before releasing those patches to everybody else. I'm so glad you don't risk fixing security holes in the general public before you have thoroughly tested the fixes with government machines. It makes me feel all warm and fuzzy knowing that I'm safe because George W. Bush's PC is running your latest software before mine is. (If I ran Windows, that is.)
The real problems are:
See the cartoon at the top of this page
GNOME got to a point where something had to be done to take it in a specific direction. The direction it took stands to benefit the most people in the most profound way. Personally I'm glad that they moved ahead the way they did. The KDE community is currently locked somewhat in stasis, because there are too many opinions, too much entropy, and no single consensus as to how to move forward. I'm not talking about making small changes, those are happening, and KDE is implementing some great features, I'm talking about the lack of major new directions for KDE such as what is happening in GNOME. That will change, a consensus will arise, and KDE will move forward in a major new direction at some point in the future.
Until then, try taking GNOME 1.0-GNOME 1.2 and extrapolate the situation that existed then to produce a hypothetical view of the way things would be now if a few core GNOME hackers hadn't done something. It would be a real mess of mismatching pieces. It might be a hacker-boy-cool mess, but it would be a mess. GNOME-2.10 is clean, lean, and most importantly consistent, and a better fit for how our subconscious processes understand information.
Besides, if they're the ones writing the code, I say they can do whatever they want with it.
This is by design. The goal is to make a GNOME app a GTK app, and vice versa, by moving critical/useful stuff for all apps into GTK, and making everything else just "value-added" and "automatically utilized" if extra GNOME libs are present.
From Wikipedia:
Avogadro's number, also called Avogadro's constant (N_A) is a large mathematical constant used in chemistry, formally defined as the number of carbon-12 atoms in 0.012 kg of carbon-12.
So the kilogram will now be defined in terms of a constant that is defined in terms of kilograms.
Yes, there are common principles behind intelligence, but we still don't really know how to abstract things at that level yet.
Isn't it dangerous to evaluate JSON on the js side by calling Javascript's eval() ? The server could be returning anything, not just JSON-valid JS syntax.
Mind you, if there's a non-JSON JS exploit that could be taken advantage, I guess you could put it straight into JS code in the HTML, and the user would be just as vulnerable as if the exploit were run using eval().
Granted you cat take this too far :o)
Exactly.
Compare the 386 or older pentiums to the P4, clock-cycle-for-clock-cycle.
Oh wait. That's basically the same thing as comparing the Pentium-M to the P4
Intel was extremely dishonest in its design of the P4. They pushed the pipeline from around 10 stages to around 23 stages. This goes against everything you will ever learn in any engineering class about pipeline design -- as soon as there is a branch instruction (of which there are a ton in x86 code -- it is much less efficient about this than say the ARM), the whole pipeline has to be flushed, so you get a huge latency hit for every condition. The pipeline flush isn't so bad with speculative evaluation / branch prediction. The whole reason Intel lengthened the pipeline is that it allowed them to push clockspeeds up further (because less work had to be done per clock cycle), and people bought CPUs based on clock speed. This gave them temporary headway against AMD, although clock cycle for clock cycle, the P4 was the least efficient processor I think anyone has ever released. More efficient branch prediction, as well as advances like hyperthreading, helped a little, but AMD chips were actually still in the lead performancewise, even though the clock speeds were much lower. The Pentium-M was apparently based on an earlier (Pentium-Pro?) architecture, but wasn't even designed by Intel directly -- they contracted out to a company in Israel (anyone know the details?). That team focussed on actual processor efficiency rather than devious marketing tactics, and hence the clock speeds of the Pentium-M are comparable to AMD offerings, and Intel finally bit the bullet and started using model numbers like AMD had to to originally compete with Intel's FUD. Intel finally acknowledges that it isn't just CPU speed that counts. The Pentium-M is the first Intel processor I have liked since Intel started being evil several years ago.
Don't ever try to open a camera case, either out of curiosity or to fix it. No matter how careful you are, you're likely to get a massive shock from the flash unit that could kill you if it passed through the wrong part of your body. I have been fixing gadgets for years, and have had two massive shocks when I opened cameras to fix them.
Great. Just what we need. There are a lot of programmers that will try to take advantage of multiple cores, but very few programmers are able to write properly-threadsafe code. Bring on the bugs.
Karoshi - Japanese for Death from Overwork
Karoshi (...) (pronounced /karo:Si/), which can be translated quite
literally from the Japanese as death from overwork, is occupational sudden
death. The major medical causes of karoshi deaths are heart attack and
stroke due to stress.
The first case of karoshi was reported in 1969 with the death from a stroke of a 29-year-old married male worker in the shipping department of Japan's largest newspaper company. It was not until the latter part of the 1980s, however, when several high-ranking business executives who were still in their prime years suddenly died without any previous sign of illness, that the media began picking up on what appeared to be a new phenomenon. This new phenomenon was quickly labelled karoshi, and once it had a name and its symptoms were described and popularized, it was immediately seen as a new and serious menace for people in the work force. In 1987, as public concern increased, the Japanese Ministry of Labour began to publish statistics on karoshi.
Usually, Japan's rise from the devastation of World War II to economic prominence in the post-war decades has been regarded as the trigger for what has been called a new epidemic. It was recognized that employees cannot work for up to twelve hours a day six or seven days a week, year after year, without suffering physically as well as mentally.
Meanwhile, death-by-overwork lawsuits have been on the rise in Japan, with the deceased person's relatives demanding compensation payments. However, before compensation can be awarded, the labour inspection office must acknowledge that the death was work-related.
In Korea, where a Confucian-inspired work ethic involves much of the adult populace, both male and female, in a six-day workweek with long hours, this phenomenon is known as kwarosa (Hangul, [...]), a word derived from the same Chinese characters as its Japanese equivalent ([...], ka, being the Chinese character for exceed, [...], rou, for labor, and [...], shi, for death).
See also Google.
Why is this a little over half the size of FC2?
Are there any actual images of this? They said they captured the Cherenkov radiation -- there must be images somewhere.
The prototype is equipped with 7 cameras on the body and a 12-inch LCD monitor in the front and another in the rear seat area.
You'll never need to look out the window again.