Anyway, I don't consider a info bar to be a major GUI design flaw. It's darned handy to get file details without having to bring up a properties box.
The trouble is, it doesn't even do a good job at it. IMO the single most important piece of information is the file name, in case it's too long to be fully visible in the list view above the status bar. But the statusbar in the screenshot has even less space for the filename than the list view does!
I think ClearType looks better on my system than Freetype. The letters don't look blurry at all, they look very sharp even. Freetype is close, but it's still somewhat behind.
I don't understand why everybody seems to love Bitstream Vera. It doesn't look nice to me, though I can't explain exactly why. It's also less easily readable compared to, for example, Georgia. See this example: on the left is Bitstream Vera serif, on the right is Georgia, both the same size. Despite the Bitstream letters being larger than the Georgia ones, I find the text on the right *much* easier to read.
Of course, Bitstream is Free and Georgia is not, but that doesn't change the fact that I find Georgia much prettier.
The mass of 1 litre of H20 is *not* 1 kg, despite what many people believe. It's OK to use that definition in everyday informal contexts, since it's close enough to the real value, but it's absolutely not good enough in rigorous scientific contexts.
At standard pressure, the density of water is less than 1 kg/m^3; at 4 C the density is at its maximum: 999.972 kg/m^3. In other words: at standard pressure and 4C, the mass of 1 litre of water is 0.999972 kg; at other temperatures it's less than that.
I think a kilogram in the beginning was meant to be the mass of 1 litre of water, but an error occured somewhere.
I also think the possibility of error is often overstated. I think I've made that mistake only two or three times in the 7 years that I'm programming professionally, and I've seen it about the same number of times in other people's code. In all of those cases I found the bug almost immediately when debugging.
IsNot compares the addresses of the variables, not the value. The equivalent in C is &a != &b instead of just a != b.
It's just like the equivalent in Python: a is not b (or not a is b, I don't really understand the need for a separate operator). Only difference is that it's one word instead of two. And different capitalization (but isn't Basic case insensitive?)
In the interview, the CEO says that many customers in their target group stopped buying DVD's because it's too expensive to store them all. Then they buy this DVD jukebox, and start buying DVD's again, he says. Now I wonder where they store those DVD's... Just throw them away?
Incorrect. In Andrew Tanenbaum's words: "Microsoft claimed that Windows NT 3.51 was a microkernel. It wasn't. It wasn't even close. Even they dropped the claim with NT 4.0." (http://www.linuxbusinessweek.com/story/44969.htm).
It's true though. On my other computer I run Mozilla 1.8a5 (the suite instead of Firefox), and the problem is solved there. Since Firefox uses the same codebase for Gecko, the problem will be fixed in the next release.
That's true, but I think result of the rendering shouldn't depend on the source of the contents, only on the contents itself.
I think it's more or less OK to have a not 100% correct layout if the engine is rendering while the file is still loading, but the final result should be correct.
You're right of course, but that's not what I meant. I just tried to say that if the input is the same, and the conditions are the same (which I didn't say explicitly), the output should be the same (note: I'm also not trying to say that different browsers should produce the same output, only that any browser should be consistent with itself).
If I load a webpage, change the font size up, then change it down again, both the input and the conditions are the same before and after, so the page should look the same. But Mozilla did it right after the change, but not always before the change.
A browser should, if given the same HTML multiple times, render it the same every time. Mozilla doesn't: when I encounter the bug, changing the font size up and down (or vice versa) or going back and forth in the history (or vice versa) fixes the layout.
Granted, Slashdot's HTML is ugly, but there really *is* (or was) a problem in Gecko.
The EU is planning their own satellite-based positioning system called Galileo (the first satellites are going to be launch next year I believe), but as a precursor to that they're also working on EGNOSS, a WAAS-like system.
For those not in the know, Flanders is the northern part of Belgium; it borders the Netherlands and its population speaks Dutch, though there are differences in pronunciation and idiom. The difference is smaller than the difference between British and American English.
About the second one: in Flanders(*), people from the Netherlands have the reputation to be miserly (I hope that's the right word?). There is no real basis in reality for that though; I think it's just based by a difference in culture.
Example: you go visit someone and out of courtesy you take something with you, a cake for example. In Flanders the cake is served, and most likely other stuff as well; generally everyone present eats from it as much as he/she likes. In the Netherlands (so I'm told), each gets 1 (one) piece of the cake, and the rest of the cake is put away for later use.
Some 20 years ago, some European TV station ran competetions between athletes of a lot of different sports to test their general fitness. F1 drivers came out as the best, or at least one of the best.
Driving an F1-car is a very taxing occupation; doing it during a whole race is no small feat. In order to be able to pull that of, F1 drivers train as much as other athletes: power training, running, the whole thing.
It happens regularly that something I'd like to be on my server is not yet in stable; I can't remember all of them, but things that I can remember are Python 2.3 (or even better, 2.4), MySQL 4, PHP 5.
I would like PHP 5 in Sarge too, but it's not even in Sid now (and neither is PostgreSQL 8) so I guess I'll have to install it from source if I'm really going to need it.
But AFAIK there isn't really an alternative for people who are willing to use a somewhat changing system. unstable changes too much; it's OK for a desktop, but not for a server. testing would be acceptable, but doesn't get security updates.
So I run stable on my little home server, eagerly awaiting the release of Sarge.
Slashdot Mirror
Anyway, I don't consider a info bar to be a major GUI design flaw. It's darned handy to get file details without having to bring up a properties box.
The trouble is, it doesn't even do a good job at it. IMO the single most important piece of information is the file name, in case it's too long to be fully visible in the list view above the status bar. But the statusbar in the screenshot has even less space for the filename than the list view does!
I think ClearType looks better on my system than Freetype. The letters don't look blurry at all, they look very sharp even. Freetype is close, but it's still somewhat behind.
Not to me... as another poster said, I feel the letters are too big. To each his own, I guess.
I don't understand why everybody seems to love Bitstream Vera. It doesn't look nice to me, though I can't explain exactly why. It's also less easily readable compared to, for example, Georgia. See this example: on the left is Bitstream Vera serif, on the right is Georgia, both the same size. Despite the Bitstream letters being larger than the Georgia ones, I find the text on the right *much* easier to read.
Of course, Bitstream is Free and Georgia is not, but that doesn't change the fact that I find Georgia much prettier.
The mass of 1 litre of H20 is *not* 1 kg, despite what many people believe. It's OK to use that definition in everyday informal contexts, since it's close enough to the real value, but it's absolutely not good enough in rigorous scientific contexts.
At standard pressure, the density of water is less than 1 kg/m^3; at 4 C the density is at its maximum: 999.972 kg/m^3. In other words: at standard pressure and 4C, the mass of 1 litre of water is 0.999972 kg; at other temperatures it's less than that.
I think a kilogram in the beginning was meant to be the mass of 1 litre of water, but an error occured somewhere.
That's exactly how I feel about the issue too.
I also think the possibility of error is often overstated. I think I've made that mistake only two or three times in the 7 years that I'm programming professionally, and I've seen it about the same number of times in other people's code. In all of those cases I found the bug almost immediately when debugging.
I don't do any Java, so I didn't know that.
IsNot compares the addresses of the variables, not the value. The equivalent in C is &a != &b instead of just a != b.
It's just like the equivalent in Python: a is not b (or not a is b, I don't really understand the need for a separate operator). Only difference is that it's one word instead of two. And different capitalization (but isn't Basic case insensitive?)
In the interview, the CEO says that many customers in their target group stopped buying DVD's because it's too expensive to store them all. Then they buy this DVD jukebox, and start buying DVD's again, he says. Now I wonder where they store those DVD's... Just throw them away?
Incorrect. In Andrew Tanenbaum's words: "Microsoft claimed that Windows NT 3.51 was a microkernel. It wasn't. It wasn't even close. Even they dropped the claim with NT 4.0." (http://www.linuxbusinessweek.com/story/44969.htm) .
It's true though. On my other computer I run Mozilla 1.8a5 (the suite instead of Firefox), and the problem is solved there. Since Firefox uses the same codebase for Gecko, the problem will be fixed in the next release.
That's true, but I think result of the rendering shouldn't depend on the source of the contents, only on the contents itself.
I think it's more or less OK to have a not 100% correct layout if the engine is rendering while the file is still loading, but the final result should be correct.
You're right of course, but that's not what I meant. I just tried to say that if the input is the same, and the conditions are the same (which I didn't say explicitly), the output should be the same (note: I'm also not trying to say that different browsers should produce the same output, only that any browser should be consistent with itself).
If I load a webpage, change the font size up, then change it down again, both the input and the conditions are the same before and after, so the page should look the same. But Mozilla did it right after the change, but not always before the change.
A browser should, if given the same HTML multiple times, render it the same every time. Mozilla doesn't: when I encounter the bug, changing the font size up and down (or vice versa) or going back and forth in the history (or vice versa) fixes the layout.
Granted, Slashdot's HTML is ugly, but there really *is* (or was) a problem in Gecko.
The EU is planning their own satellite-based positioning system called Galileo (the first satellites are going to be launch next year I believe), but as a precursor to that they're also working on EGNOSS, a WAAS-like system.
For those not in the know, Flanders is the northern part of Belgium; it borders the Netherlands and its population speaks Dutch, though there are differences in pronunciation and idiom. The difference is smaller than the difference between British and American English.
About the second one: in Flanders(*), people from the Netherlands have the reputation to be miserly (I hope that's the right word?). There is no real basis in reality for that though; I think it's just based by a difference in culture.
Example: you go visit someone and out of courtesy you take something with you, a cake for example. In Flanders the cake is served, and most likely other stuff as well; generally everyone present eats from it as much as he/she likes. In the Netherlands (so I'm told), each gets 1 (one) piece of the cake, and the rest of the cake is put away for later use.
On some blogs, the 'word' USian seems popular.
Some 20 years ago, some European TV station ran competetions between athletes of a lot of different sports to test their general fitness. F1 drivers came out as the best, or at least one of the best.
Driving an F1-car is a very taxing occupation; doing it during a whole race is no small feat. In order to be able to pull that of, F1 drivers train as much as other athletes: power training, running, the whole thing.
We use Mantis too, using Apacha and MySQL running on Windows. No problem. I don't know how it compares to bugzilla concerning features though.
In Korea, only old people are recent.
The packages I like never seem to be available on backports.org. Python 2.3 for example, and PHP 5.
It happens regularly that something I'd like to be on my server is not yet in stable; I can't remember all of them, but things that I can remember are Python 2.3 (or even better, 2.4), MySQL 4, PHP 5.
I would like PHP 5 in Sarge too, but it's not even in Sid now (and neither is PostgreSQL 8) so I guess I'll have to install it from source if I'm really going to need it.
But AFAIK there isn't really an alternative for people who are willing to use a somewhat changing system. unstable changes too much; it's OK for a desktop, but not for a server. testing would be acceptable, but doesn't get security updates.
So I run stable on my little home server, eagerly awaiting the release of Sarge.