Thus all the other humans nowadays native Americans, Chinese, Aboriginees etc. are either from another 'humanoid' flock or they could swim very very well;)
The 'other humans' may have built their own boats. Also likely took (mental) notes to come up with their own flood legend.
Another developer has left us. I guess we won't be needing this anymore... *throws chair*
(One has to be careful to leave the premises before being noticed, otherwise it becomes *throws chair at developer*)
I find native SVG rendering on firefox interesting, for instance this graphic of the Uluru. I still find it cool that you can click on the picture to view its source.
But since SVG needs the Adobe SVG plugin on IE, i usually draw my clipart in Inkscape or Sodipodi (i forgot which has better Japanese support) then export it to PNG.
The thing is, uncomfortable engagement can be more effective than complete, self-satisfied and puritanical shunning.
I think in China, a business can't remain "uncomfortably engaged." If the government demands access to data that would lead to the arrest of activists (like they did with Yahoo), the business would have to cooperate. Otherwise, they would be "obstructing justice." I think Google is trying to avoid that sort of situation.
I was gonna take a look at the specs, since I wanted to see how WMP compares to PNG and JPEG. Did they really get some smart people to come up with a better compression algorithm? The news article was very sparse on detail, so I went to the microsoft site, which had an opening page saying (and I paraphrase):
1.You may read the specs only if you use them to write software which work with Microsoft products, or
2. To provide feedback on the Specs to Microsoft.
Duh... where's the "I wanna know if it's any good" option? I did a google of "Windows Media Photo" to see if there was any more stuff to read, but I didn't get anything more informative than the linked cnet article.
Geez dude... you forgot to close your sarcasm tag, so you got modded troll.
Anyway... the "damage" extension was supposed to fix the bandwidth issue (if there was any, IANA Xdeveloper) by limiting transferred data to parts of the screen that were "damaged." I don't think modularisation has anything to do with performance. It's about code maintainability/flexibility.
What makes you think this will improve matters? Who exactly is going to go reading patents and reviewing them for the patent office?
A question of motivation, huh? The answer is, anyone who wants to. If people can voluntarily create free software without any apparent motivation, then there will be people who want to invalidate patent applications just because they feel they should. It's the "more eyes" option being applied to patents.
Developers/scientists/engineers? No...
In my previous job, I was trained to read patents and to make sure products were non-infringing after the development cycle (and then to find workarounds afterwards). So yes, some developers can and do read patents to prevent being sued.
most legal advice suggests that you shouldn't go reading about patents in your field, and instead just read patents whenever they become relevant to you
That depends on your habits as a developer. If you've started a project, and then somewhere along you feel you want to check the patent minefield, you can go on ahead. At least this time, if someone came up with an idiotic patent application, you can vent your frustration and hopefully point out some prior art on the forum.
I struggle to see how the patent office is going to get much out of this.
That will depend on how they will be able to process input from the forums. They will have to come up with some system to filter out the spam and trolls, etc. And the examiners' jobs will have to be redefined to include reading the forum posts, which is the tough part i think.
Taking a look at the screenshots on page 4, i noticed that some apps (KDE?) are in Dutch, while others (Mandriva-specific?) are in English. Looks like i18n isn't finished yet, unless they mixed shots from different language installations (which i very much doubt).
Incidentally, the reason I left Mandrake 4 years ago for Fedora (core 2, i think) was that Fedora had better Japanese language support. I also didn't like MenuDrake.. too inflexible, iirc.
Then why do UNIX developers _willingly_ develop on UNIX, for zero-cost and for Free Software, but rarely do so on Windows?
Just a positive comment on this point. It is *much* easier to develop open source software for Linux than it is for Windows, because of the sheer availability of free libraries on Linux.
In my personal experience, FOSS development on Windows is limited because (1) free libraries are unavailable/outdated and hell to port/hell to build, and (2) development on Win is B-O-R-I-N-G because it's what I use at work 90% of the time, and the only tool I get to use is Visual Studio + SDKs.
A word to windows-only programmers: Windows is good and pays well, but try out Linux programming. To feel the difference between the libraries, write something like a video player. It takes a bit to get out of the windows way of thinking, but when you get the hang of it, it is much more interesting. You don't know what you're missing.
Supposing Duval started a new project... any chance Mandriva would screw up, acquire Duval, and make him chief once more? Something like the Apple fairy tale.
We could have NPCs on MUDs and MMORPGs controlled by slime molds! Server rooms will have to be kept dark and damp... gaming will never be the same. </prior art>
Hmm... might actually be one of the things they're trying to do: increase chances of assimilation. Instead of sticking to Google, you might once in a while check Yahoo to see if you won. They're hoping you might even find some good hits/useful search options.
Interesting, I had a teacher who actually encouraged that sort of thing . It was an engineering class in our senior year, and the teacher thought that we had a lot to learn about the real world. He said, to get anything done, either (1) do it yourself, (2) write a program to do it, or (3) get someone else to do it for you. Then he gave us some tedious homework. Most of us opted for option (2). But he allowed it only for a couple of projects.
Interesting insight from godeke. Here is my commentary:
*BZZZT* If the *MEAN* time between failures is 500,000 hours it indicates that given a sampling of devices you will find the arithmetic mean lifespan to be 500,000 hours.
As is obvious, the GP is likely using the formula:
drives * failure rate * time = number of failures
an average drive will fail in 500,000 hours:
1 drive * (1 failure / 5e5 hours) * 5e5 hours = 1 failure
if 500 drives run for 1000 hours, how many failures might there be?
500 drives * (1 failure / 5e5 hours) * 1e3 hours = 1 failure
However, this assumes that the likelihood of failure of each drive is evenly distributed within those 500,000 hours (curve is flat) -- even if drives were bought at the same time, something like 1 drive dies every 1000 hours.
If you expect 1 drive in 500 to fail in 1000 hours, then you must have the expectation that at the other end you have a near immortal drive.
What the GP pointed out is that actual drives tend to fail towards the end of their lifetimes, so that the death curve starts low and then shoots up later. They'll start healthy, then die en masse when they get old.
The trouble with averages is that they make the curves look flat.
Interesting to keep this in mind when shopping for equipment...
Slashdot Mirror
The 'other humans' may have built their own boats. Also likely took (mental) notes to come up with their own flood legend.
Another developer has left us.
I guess we won't be needing this anymore... *throws chair*
(One has to be careful to leave the premises before being noticed, otherwise it becomes *throws chair at developer*)
Redundant Corollary of Redundancy: even a first post can be redundant if you post the same sentence redundantly. ;)
But since SVG needs the Adobe SVG plugin on IE, i usually draw my clipart in Inkscape or Sodipodi (i forgot which has better Japanese support) then export it to PNG.
I have a right not to sneeze on my $4000 cat from e-bay, you insensitive clod!
I agree. Realdoll boobs are WAY better.
I think in China, a business can't remain "uncomfortably engaged." If the government demands access to data that would lead to the arrest of activists (like they did with Yahoo), the business would have to cooperate. Otherwise, they would be "obstructing justice." I think Google is trying to avoid that sort of situation.
The page has the lightweight look of digg and link menus open up like those on the Mac. And it works on firefox.
Looks like they're learning to be sleek.
1.You may read the specs only if you use them to write software which work with Microsoft products, or
2. To provide feedback on the Specs to Microsoft.
Duh... where's the "I wanna know if it's any good" option? I did a google of "Windows Media Photo" to see if there was any more stuff to read, but I didn't get anything more informative than the linked cnet article.
Anyway... the "damage" extension was supposed to fix the bandwidth issue (if there was any, IANA Xdeveloper) by limiting transferred data to parts of the screen that were "damaged." I don't think modularisation has anything to do with performance. It's about code maintainability/flexibility.
This will be based on Ooo.org?
I wonder what happened to Lotus SmartSuite... would leaning towards OpenOffice mean they will kill it off?
Poor old Lotus 1-2-3 *nostalgic sigh*
A question of motivation, huh? The answer is, anyone who wants to. If people can voluntarily create free software without any apparent motivation, then there will be people who want to invalidate patent applications just because they feel they should. It's the "more eyes" option being applied to patents.
Developers/scientists/engineers? No...
In my previous job, I was trained to read patents and to make sure products were non-infringing after the development cycle (and then to find workarounds afterwards). So yes, some developers can and do read patents to prevent being sued.
most legal advice suggests that you shouldn't go reading about patents in your field, and instead just read patents whenever they become relevant to you
That depends on your habits as a developer. If you've started a project, and then somewhere along you feel you want to check the patent minefield, you can go on ahead. At least this time, if someone came up with an idiotic patent application, you can vent your frustration and hopefully point out some prior art on the forum.
I struggle to see how the patent office is going to get much out of this.
That will depend on how they will be able to process input from the forums. They will have to come up with some system to filter out the spam and trolls, etc. And the examiners' jobs will have to be redefined to include reading the forum posts, which is the tough part i think.
Incidentally, the reason I left Mandrake 4 years ago for Fedora (core 2, i think) was that Fedora had better Japanese language support. I also didn't like MenuDrake.. too inflexible, iirc.
Not to mention meat buckyballs... and carbonara sauce *drool*
Then why do UNIX developers _willingly_ develop on UNIX, for zero-cost and for Free Software, but rarely do so on Windows?
Just a positive comment on this point. It is *much* easier to develop open source software for Linux than it is for Windows, because of the sheer availability of free libraries on Linux.
In my personal experience, FOSS development on Windows is limited because (1) free libraries are unavailable/outdated and hell to port/hell to build, and (2) development on Win is B-O-R-I-N-G because it's what I use at work 90% of the time, and the only tool I get to use is Visual Studio + SDKs.
A word to windows-only programmers: Windows is good and pays well, but try out Linux programming. To feel the difference between the libraries, write something like a video player. It takes a bit to get out of the windows way of thinking, but when you get the hang of it, it is much more interesting. You don't know what you're missing.
Supposing Duval started a new project... any chance Mandriva would screw up, acquire Duval, and make him chief once more? Something like the Apple fairy tale.
You forgot Windows Vista Me!
nobody remembers poor Me...
Oh yeah, Vista CE just might be legit... in addition to the 8 desktop/note os vistas.
Check out the text output performance improvement of gterm! http://www.gnome.org.nyud.net:8080/~davyd/gnome-2- 14/ Hallelujah!
I hope the startup speed gets a boost too.
We could have NPCs on MUDs and MMORPGs controlled by slime molds! Server rooms will have to be kept dark and damp... gaming will never be the same.
</prior art>
Hmm... might actually be one of the things they're trying to do: increase chances of assimilation. Instead of sticking to Google, you might once in a while check Yahoo to see if you won. They're hoping you might even find some good hits/useful search options.
Interesting, I had a teacher who actually encouraged that sort of thing . It was an engineering class in our senior year, and the teacher thought that we had a lot to learn about the real world. He said, to get anything done, either (1) do it yourself, (2) write a program to do it, or (3) get someone else to do it for you.
Then he gave us some tedious homework. Most of us opted for option (2). But he allowed it only for a couple of projects.
Interesting insight from godeke. Here is my commentary:
*BZZZT* If the *MEAN* time between failures is 500,000 hours it indicates that given a sampling of devices you will find the arithmetic mean lifespan to be 500,000 hours.
As is obvious, the GP is likely using the formula:
drives * failure rate * time = number of failures
an average drive will fail in 500,000 hours:
1 drive * (1 failure / 5e5 hours) * 5e5 hours = 1 failure
if 500 drives run for 1000 hours, how many failures might there be?
500 drives * (1 failure / 5e5 hours) * 1e3 hours = 1 failure
However, this assumes that the likelihood of failure of each drive is evenly distributed within those 500,000 hours (curve is flat) -- even if drives were bought at the same time, something like 1 drive dies every 1000 hours.
If you expect 1 drive in 500 to fail in 1000 hours, then you must have the expectation that at the other end you have a near immortal drive.
What the GP pointed out is that actual drives tend to fail towards the end of their lifetimes, so that the death curve starts low and then shoots up later. They'll start healthy, then die en masse when they get old.
The trouble with averages is that they make the curves look flat. Interesting to keep this in mind when shopping for equipment...
It would have been funny if it wasn't a week right after August 6 (Hiroshima) / August 9 (Nagasaki). And the mention of the word "casualty" reminded me of a witness account.
Although I probably wouldn't have known if I weren't working in Japan.
Imagine how the switch on the device would be labeled:
Jerk - on
:-)
Jerk - oh, nevermind...