interesting post but, I don't think it applies. Open Office started out as a proprietary product, not an open one. Its was later made open source.
I guess we should throw away Apache Tomcat, JBoss, Ant, Jakarta Commons to name a few.
Or maybe, when you build a project, you build it in whatever language you want. Its your project. If people don't like it, they don't have to use it. As for the OOo debate, I'm sure MS would be happy to sell an office suite to those who object so strongly to the use of Java in OO.
I think we've come to a really sad state when a bunch of guys working for free part time as a hobby need a bunch of lawyers to tell them how to go about it.
I'm going to venture slightly off topic. Your post brings up another question. I wonder what effects the radiation from the van allen belts will have on the carbon nanotubes and the polymers to bind them in the "ribbon" for the space elevator. It seems to me that having a sensive molecular structure getting bombarded by high energy particles is not a good thing. OTOH, if they put a big collection plate up, and hooked it up to a cable running down the ribbon, you'd have some zero pollution electricity;)
Open source deveopers have been bickering since there were open source developers. Hell, even closed source dev bicker. It can actually be a good thing when they are bickering about the code. A resolution usually results in higher quality and new design patterns. We all get to benefit from it. But, sometimes its just bickering and then, you're right, time just gets wasted. Unless, a dev says "I'll show him", and goes on to write some awesome code to prove a point.
This looks like a classic case of a developer arguing against a manager. dev: If we don't get the code in good shape, we'll never have the opportunity. It will just get worse.
mgr: just do whatever it takes to meet the deadline, we'll fix it later (thinking: I've got two projects after this one)
dev: The bad code makes new development take longer. So the result of a shortcut will mean we'll still miss the deadline.
mgr (missing the point): Yes, I understand but, we don't have time to fix it.
dev: (nods head, returns to desk, pulls tequila from desk drawer)
I personally can't wait for the next KDE/Apple slashdot flamewar.
Are the editors just doing this for kicks? I have to admit, I've gotten sucked in and made the comments too. First, we get repeated Evolution vs Intelligent Design debates until everyone was sick of them. Now, its the Apple/KDE. Maybe after a week we'll get ad naseum: Apple rocks/sucks Linux vs Windows Java vs world OOo using java Your favorite open source product has new security hole Your most hated closed source product has security hole
wha, I just saw a comment that got me riled up, KDE ro... Apple, wha.. let me go straighten out that troll...
I wonder if this would be as big an issue if Apple had started out by saying, "we want to fork the code." The license gives them that right. This is essentially what's happened. Neither team is actively using the others patches.
My experience is that merging code on large projects is a pain. Even when you share the same respository (CVS) and have teams working on different branches. I hate the thought of trying to merge code that's several months apart developmentaly. Besides just dealing with the code, check-in comments, when they exist, are usually vague, brief, and overly broad (25 files modified, the comment only actually refers to two of them).
It sucks, but, they might be better off just accepting it as the fork that it is. Both of these teams have differing objectives. Trying to keep the code in sync while trying to (in all intents and purposes) create different end products may be more pain than its worth (to all parties).
The developers of KHTML should be proud. They created an excellent product. A large company felt their product was of high enough quality to warrant distribution in a mainstream operating system.
lol, I purposely avoided mentioning MySql for fear of flames (because I rarely have anything good to say about it). I agree with your point but, I'll have to mention that I haven't experienced data coruption with either PostgreSQL or DB2. However, admittedly, my experience with those is limited, and I'm a developer not a dba.
I don't think this is really a product to compete with samba (except maybe file transfer). With samba, you can mount a remote (windows) file system, and work with it as if were local. This tool isn't going to provide the capability to do that. It will give you gui'ish directory browsing and file transfer. As for using mini http servers, it would definitly provide more security, control, and understanding of what is shared. But, if the files are on someone else's box, you don't really have the option. On this topic, Mandrake has this neat little feature where you can right-click/share a directory, and it does just this, starts an http server, you pick the port and amount of bandwidth you're willing to dedicate. This program would be a good tool for non-techies to just grab files from remote windows boxes and not have to deal with the vagaries of windows networking. Think graphic designer on a mac, a secretary on windows, an intern on a linux machine...
Like how they san't seem to maintain compatibility between minor realeases. How they fix bugs, then reintroduce the same bugs in the next release. Support that reeks when you call them. IBM actually supports Oracle better than Oracle. I know, I've used them both.
I think the only thing Oracle really has going for them is a great sales team. And getting customers locked in because they write all their stuff in plsql. And what do we get for using this, I think the last report said its 5% faster than PostgreSQL or DB2. Hundreds of thousands of dollars for 5%? WTF? For the cost of an Oracle 9i/10g license, you can install DB2 or PostgreSQL, buy a box, and hire a new dba.
I think you make some really good points about "cost" here. So, basically we can say that when determining the relative "costs" of products we should consider the following: - necessary for conducting business - actual price of the product - cost of labor for the user (productivity) - labor costs of supporting the product (updates/security fixes) Some things can supercede all others. If your business requires that you deal with a particular type of document, then its a bad business decision to not use the correct tool, regardless of cost.
Basically, people should look at their needs first, then find the product that best fits them, open source, closed source, public domain, whatever. Different people have different needs. Trying to apply a one size fits all solution, whether open or closed source is probably not the best way to go.
It seems its been quite some time since he has given away any code. He has been very busy in the last few years trying to convince others to give their code away. Maybe trying to convince others to write code for free has left him with little time to do the same.
I still stand by my statement. Instead of criticizing others and calling for volunteers, he could start coding and say, "I've started this new project, here's my code, if anyone would like to help, I'm open."
How about instead of looking the gift horse in the mouth, we just express a simple thank you to the developers for all of their hard work.
The developers have made zero effort to try to make it possible for Kaffe, GCJ, or the upcoming Harmony
Wait, you mean developers working for free, have made zero effort to make their task more difficult?
Those jerks.
Why didn't they consult with us before giving us free software?
Don't they know that we care more about the choice of development language than functionality and bugs.
You can't seriously trust a developer to chose the implementation language for his or her project. Isn't it more appropriate for the users of software to decide the deveopment language. They are the ones who will get the binaries.
Maybe they think that OOo 2.0 will get released too soon and would prefer to wait a few years for the developers to port, and test the code.
There's HypersonicSQL, that would have to be removed from its dev team, forked, and ported to a non java language. Then all of the code that uses it. I'm sure there's lots of other stuff. So, we could add a year or more to the release and get the exact same features with the same performance, the same license (OOo license), and more bugs.
Yes, we could wait and get nothing except binaries that were made from source that was written in a language that has a different license.
Or maybe the crybabies, who think this is such a big deal, could take the open source java source code and port it too some other language (C#?) of their choosing and thank the original developers for devoting their time. I notice that Richard Stallman is calling for volunteers instead of just doing it. Typical.
Bill Gates has got to love this. The open source community builds a product to compete against his products. Then instead of unifying to make the project better, they split up to make a competing copy of the competing product. And this is over a language that there are open source tools to deal with.
Or, we could all give a word of thanks to the developers who dedicated so much time so that we all may benefit. Even MSOffice users will benefit as MS improves their product and lowers their prices to cope with new competition.
seaching the error code seems to indicate a database connectivity error.
Disclaimer: I'm a J2EE dev so my opinion may not count. It appears that they are either not properly implementing connection pooling and running out of connections. Or the database is being overloaded by failing to implement caching to non changing data.
Maybe they just aren't used to developing for a high traffic web site.
Even worse is letting the default error page get treturned instead of providing a custom one or sending a 302.
Seems most of the pages returned from google feeding this error code(0x80004005) are about people using MS Access behind the web server. Now I like to raz on MS as much as the next guy but, this may just be a case of the wrong tool for the job. Access on a public web site is just a plain bad idea.
OTOH, even if its not Access the nature of the article suggests that any reasonable site would employ caching and not bang the database with every request. OF course, I admit that without seeing the site or their code its all just speculation.
I think we can expect poor results from any tool misapplied.
I don't know why I kept thinking these laws were passed around the late 50's. Maybe, I'm thinking old jazz scene. Of course, the Civil Rights Act was the one I meant.
Weren't the drug laws passed around the same time as the civil rights ammendment? Aren't the overwhelming majority of people convicted on drug charges African American? In many states convicted felons never regain the right to vote.
I am not putting on the tinfoil hat here, I'm just pointing out an interesting coincidence.
There are a lot of knowledgeble people here, I hope someone will point out a misconception or bad info (please).
Unfortuneately here in the US things like that do happen. Our system (actually the culture that tolerates it) is wacked, to say the least. These things can be defended however, you will need some big resources to defend yourself. Then the other problem is becasue lawsuits are held in civil courts (instead of criminal) you are stuck trying to prove your inocence instead of simply disproving their claims. And of course, the biggest problem is that even when you win the case, you still lose. The trial itself becomes a slander against your career. This kind of thing truly sucks, is completely unfair, and unfortunatly is something that has to be taken into consideration. Its never happend to me but, I do know a guy who had to suffer through this. He did nothing wrong, but had a wacko boss.
You'll hear a lot stuff about its a small world and how you on't want a bad rep, and yada, yada, yada.
I think the main reason not to burn em is keeping your self respect. You'll probably find that most people who tell you not to burn your bridges are folks who've done it in their youth. I know I have. Don't lower yourself to their level, remember you are a PROFESSIONAL, ACT THAT WAY. The other is when people try to "make a point" when they quit, it always falls on deaf ears. I can't give details but, once during a company meeting, a co-worker asked the company predident a question, didn't like the answer, and resigned on the spot. He was trying very hard to make a strong point. The result. nothing. nothing happened at all. His projects got handed to other people, the dates extended on them, and he was all but forgotten in a couple of weeks. People couldn't even remeber the question.
The best way to quit a job is to quietly disappear.
Also, there is always the disclosure issue. Any developer is going to fnd themselves re-implementing similar solutions at any company they work for. And, whether you carry around a code library or not, you'll end up (re)writing lots of similar code. And after its been compiled, the object code is going to look very similar when disassembled. An old boss can get you in court if they really want to. He may not win but, your life will suck when it happens, and your career will suffer even more as you are publicly made into someone who can't be trusted with company secrets. Even if you do nothing wrong, this can happen.
Just by making the acusation with the police, you could find the cops busting into your home and confiscating your computer and personal items. You can counter-sue but, the damage to your career and life can't really be undone.
When quitting, I recommend you give 2-3 weeks notice, in writing (read some books on a good resignation letter) to both your boss and your HR department. Make sure the reason for your leaving has nothing to do with any problems the company has. Then walk on eggshells for your remaining time. Be helpful, organize your projects and documentation, and be quiet, don't bad mouth anyone, compliment everybody you work with, especially the adversarial ones.
I've never understood this mentality of drawing a "line in the sand" with your employer.
If you have a problem with the conditions at your job, then, bring them up with your employer. Just say, "hey, I've got a serious problem with X". If the condition is intolerable and they don't do anything, then start looking for another job. period.
If you back them into a corner, then everybody loses. Your boss/company in order to save face will be forced to maintain its position. You will have burned bridges and look like an extremist in your leaving.
I think some of these guys get too obsessed with their own points of view. And I would hope that a JOURNALIST would stay on the facts and not make judgements. But, maybe I suffer from the same problem that they do, dreaming of (my idea of) a perfect world.
You make a very good argument, and I agree with you on most points but, I might disagree on some details. Although I agree with you on the role of evolution, I disagree with using it as justification. Primitive man also killed his competition for a better chance of propagation. As for our biological requirements, you are completely right.
As for having someone else (butcher) kill an animal vs killing it yourself, I believe that killing the animal yourself is more ethical. Look at how much meat is thrown away in this country. People who kill their own animals tend to have much more respect for the creature and do not waste them. Where I disagree with you is in the making a sport out of killing the creature. I have butcherd a few animals (goats, sheep, and pig) for BBQ's. However, I try to make it quick, simple, and as painless as possible. Now, I do understand the desire for the sport, hell, we've got millions of years of evolution that make it desireable. There's the inrush of all kinds of hormones and nuerochemicals to make it a desireable activity. But, as a thinking being I find it distasteful to make sport out of killing.
Considering that the kids will be using computers for a very small percentage of their time at school at first glance, it would make sense to save money there inorder to maintain teacher salaries, or to invest in higher quality books. This could then help to increase the quality of education. (can you tell I'm a dreamer?)
But honestly, the decision about what OS and applications are used in schools should be based upon the usage and curriculum. If they are just using internet resources for research or typing docs, then a free OS is fine BSD or Linux. If they are running AutoCAD, 3D Studio, or other specialized programs then the program will dictate the OS. This really looks like it should be judged on a case by case basis and not mandated.
Slashdot Mirror
interesting post but, I don't think it applies.
Open Office started out as a proprietary product, not an open one. Its was later made open source.
I guess we should throw away Apache Tomcat, JBoss, Ant, Jakarta Commons to name a few.
Or maybe, when you build a project, you build it in whatever language you want. Its your project. If people don't like it, they don't have to use it.
As for the OOo debate, I'm sure MS would be happy to sell an office suite to those who object so strongly to the use of Java in OO.
I think we've come to a really sad state when a bunch of guys working for free part time as a hobby need a bunch of lawyers to tell them how to go about it.
I'm going to venture slightly off topic. Your post brings up another question. ;)
I wonder what effects the radiation from the van allen belts will have on the carbon nanotubes and the polymers to bind them in the "ribbon" for the space elevator.
It seems to me that having a sensive molecular structure getting bombarded by high energy particles is not a good thing. OTOH, if they put a big collection plate up, and hooked it up to a cable running down the ribbon, you'd have some zero pollution electricity
Wow, I went from offtopic to wandering.
Open source deveopers have been bickering since there were open source developers. Hell, even closed source dev bicker.
It can actually be a good thing when they are bickering about the code. A resolution usually results in higher quality and new design patterns. We all get to benefit from it. But, sometimes its just bickering and then, you're right, time just gets wasted. Unless, a dev says "I'll show him", and goes on to write some awesome code to prove a point.
This looks like a classic case of a developer arguing against a manager.
dev: If we don't get the code in good shape, we'll never have the opportunity. It will just get worse.
mgr: just do whatever it takes to meet the deadline, we'll fix it later (thinking: I've got two projects after this one)
dev: The bad code makes new development take longer. So the result of a shortcut will mean we'll still miss the deadline.
mgr (missing the point): Yes, I understand but, we don't have time to fix it.
dev: (nods head, returns to desk, pulls tequila from desk drawer)
As a general rule, people don't like being told what to do
especially when they are working for free
I personally can't wait for the next KDE/Apple slashdot flamewar.
Are the editors just doing this for kicks? I have to admit, I've gotten sucked in and made the comments too.
First, we get repeated Evolution vs Intelligent Design debates until everyone was sick of them. Now, its the Apple/KDE. Maybe after a week we'll get ad naseum:
Apple rocks/sucks
Linux vs Windows
Java vs world
OOo using java
Your favorite open source product has new security hole
Your most hated closed source product has security hole
wha, I just saw a comment that got me riled up, KDE ro... Apple, wha.. let me go straighten out that troll...
I wonder if this would be as big an issue if Apple had started out by saying, "we want to fork the code." The license gives them that right. This is essentially what's happened. Neither team is actively using the others patches.
My experience is that merging code on large projects is a pain. Even when you share the same respository (CVS) and have teams working on different branches. I hate the thought of trying to merge code that's several months apart developmentaly. Besides just dealing with the code, check-in comments, when they exist, are usually vague, brief, and overly broad (25 files modified, the comment only actually refers to two of them).
It sucks, but, they might be better off just accepting it as the fork that it is. Both of these teams have differing objectives. Trying to keep the code in sync while trying to (in all intents and purposes) create different end products may be more pain than its worth (to all parties).
The developers of KHTML should be proud. They created an excellent product. A large company felt their product was of high enough quality to warrant distribution in a mainstream operating system.
lol,
I purposely avoided mentioning MySql for fear of flames (because I rarely have anything good to say about it).
I agree with your point but, I'll have to mention that I haven't experienced data coruption with either PostgreSQL or DB2. However, admittedly, my experience with those is limited, and I'm a developer not a dba.
I don't think this is really a product to compete with samba (except maybe file transfer).
With samba, you can mount a remote (windows) file system, and work with it as if were local. This tool isn't going to provide the capability to do that. It will give you gui'ish directory browsing and file transfer.
As for using mini http servers, it would definitly provide more security, control, and understanding of what is shared. But, if the files are on someone else's box, you don't really have the option. On this topic, Mandrake has this neat little feature where you can right-click/share a directory, and it does just this, starts an http server, you pick the port and amount of bandwidth you're willing to dedicate.
This program would be a good tool for non-techies to just grab files from remote windows boxes and not have to deal with the vagaries of windows networking. Think graphic designer on a mac, a secretary on windows, an intern on a linux machine...
Like how they san't seem to maintain compatibility between minor realeases. How they fix bugs, then reintroduce the same bugs in the next release. Support that reeks when you call them. IBM actually supports Oracle better than Oracle. I know, I've used them both.
I think the only thing Oracle really has going for them is a great sales team. And getting customers locked in because they write all their stuff in plsql.
And what do we get for using this, I think the last report said its 5% faster than PostgreSQL or DB2. Hundreds of thousands of dollars for 5%? WTF?
For the cost of an Oracle 9i/10g license, you can install DB2 or PostgreSQL, buy a box, and hire a new dba.
I think you make some really good points about "cost" here.
So, basically we can say that when determining the relative "costs" of products we should consider the following:
- necessary for conducting business
- actual price of the product
- cost of labor for the user (productivity)
- labor costs of supporting the product (updates/security fixes)
Some things can supercede all others. If your business requires that you deal with a particular type of document, then its a bad business decision to not use the correct tool, regardless of cost.
Basically, people should look at their needs first, then find the product that best fits them, open source, closed source, public domain, whatever. Different people have different needs. Trying to apply a one size fits all solution, whether open or closed source is probably not the best way to go.
If "he perceives a need for code", why should it be anybody's responsibility, except his, to write it?
I perceive a need for my bills to be paid, any volunteers?
It seems its been quite some time since he has given away any code. He has been very busy in the last few years trying to convince others to give their code away.
Maybe trying to convince others to write code for free has left him with little time to do the same.
I still stand by my statement. Instead of criticizing others and calling for volunteers, he could start coding and say, "I've started this new project, here's my code, if anyone would like to help, I'm open."
How about instead of looking the gift horse in the mouth, we just express a simple thank you to the developers for all of their hard work.
The developers have made zero effort to try to make it possible for Kaffe, GCJ, or the upcoming Harmony
Wait, you mean developers working for free, have made zero effort to make their task more difficult?
Those jerks.
Why didn't they consult with us before giving us free software?
Don't they know that we care more about the choice of development language than functionality and bugs.
You can't seriously trust a developer to chose the implementation language for his or her project. Isn't it more appropriate for the users of software to decide the deveopment language. They are the ones who will get the binaries.
Maybe they think that OOo 2.0 will get released too soon and would prefer to wait a few years for the developers to port, and test the code.
There's HypersonicSQL, that would have to be removed from its dev team, forked, and ported to a non java language. Then all of the code that uses it. I'm sure there's lots of other stuff.
So, we could add a year or more to the release and get the exact same features with the same performance, the same license (OOo license), and more bugs.
Yes, we could wait and get nothing except binaries that were made from source that was written in a language that has a different license.
Or maybe the crybabies, who think this is such a big deal, could take the open source java source code and port it too some other language (C#?) of their choosing and thank the original developers for devoting their time. I notice that Richard Stallman is calling for volunteers instead of just doing it. Typical.
Bill Gates has got to love this. The open source community builds a product to compete against his products. Then instead of unifying to make the project better, they split up to make a competing copy of the competing product. And this is over a language that there are open source tools to deal with.
Or, we could all give a word of thanks to the developers who dedicated so much time so that we all may benefit. Even MSOffice users will benefit as MS improves their product and lowers their prices to cope with new competition.
seaching the error code seems to indicate a database connectivity error.
Disclaimer: I'm a J2EE dev so my opinion may not count.
It appears that they are either not properly implementing connection pooling and running out of connections. Or the database is being overloaded by failing to implement caching to non changing data.
Maybe they just aren't used to developing for a high traffic web site.
Even worse is letting the default error page get treturned instead of providing a custom one or sending a 302.
Seems most of the pages returned from google feeding this error code(0x80004005) are about people using MS Access behind the web server. Now I like to raz on MS as much as the next guy but, this may just be a case of the wrong tool for the job. Access on a public web site is just a plain bad idea.
OTOH, even if its not Access the nature of the article suggests that any reasonable site would employ caching and not bang the database with every request. OF course, I admit that without seeing the site or their code its all just speculation.
I think we can expect poor results from any tool misapplied.
I don't know why I kept thinking these laws were passed around the late 50's. Maybe, I'm thinking old jazz scene.
Of course, the Civil Rights Act was the one I meant.
thank you for the clarification
Weren't the drug laws passed around the same time as the civil rights ammendment?
Aren't the overwhelming majority of people convicted on drug charges African American?
In many states convicted felons never regain the right to vote.
I am not putting on the tinfoil hat here, I'm just pointing out an interesting coincidence.
There are a lot of knowledgeble people here, I hope someone will point out a misconception or bad info (please).
Unfortuneately here in the US things like that do happen. Our system (actually the culture that tolerates it) is wacked, to say the least.
These things can be defended however, you will need some big resources to defend yourself. Then the other problem is becasue lawsuits are held in civil courts (instead of criminal) you are stuck trying to prove your inocence instead of simply disproving their claims. And of course, the biggest problem is that even when you win the case, you still lose. The trial itself becomes a slander against your career.
This kind of thing truly sucks, is completely unfair, and unfortunatly is something that has to be taken into consideration. Its never happend to me but, I do know a guy who had to suffer through this. He did nothing wrong, but had a wacko boss.
You'll hear a lot stuff about its a small world and how you on't want a bad rep, and yada, yada, yada.
I think the main reason not to burn em is keeping your self respect. You'll probably find that most people who tell you not to burn your bridges are folks who've done it in their youth. I know I have. Don't lower yourself to their level, remember you are a PROFESSIONAL, ACT THAT WAY.
The other is when people try to "make a point" when they quit, it always falls on deaf ears.
I can't give details but, once during a company meeting, a co-worker asked the company predident a question, didn't like the answer, and resigned on the spot. He was trying very hard to make a strong point. The result. nothing. nothing happened at all. His projects got handed to other people, the dates extended on them, and he was all but forgotten in a couple of weeks. People couldn't even remeber the question.
The best way to quit a job is to quietly disappear.
Also, there is always the disclosure issue. Any developer is going to fnd themselves re-implementing similar solutions at any company they work for. And, whether you carry around a code library or not, you'll end up (re)writing lots of similar code. And after its been compiled, the object code is going to look very similar when disassembled. An old boss can get you in court if they really want to. He may not win but, your life will suck when it happens, and your career will suffer even more as you are publicly made into someone who can't be trusted with company secrets. Even if you do nothing wrong, this can happen.
Just by making the acusation with the police, you could find the cops busting into your home and confiscating your computer and personal items. You can counter-sue but, the damage to your career and life can't really be undone.
When quitting, I recommend you give 2-3 weeks notice, in writing (read some books on a good resignation letter) to both your boss and your HR department. Make sure the reason for your leaving has nothing to do with any problems the company has. Then walk on eggshells for your remaining time. Be helpful, organize your projects and documentation, and be quiet, don't bad mouth anyone, compliment everybody you work with, especially the adversarial ones.
I've never understood this mentality of drawing a "line in the sand" with your employer.
If you have a problem with the conditions at your job, then, bring them up with your employer. Just say, "hey, I've got a serious problem with X". If the condition is intolerable and they don't do anything, then start looking for another job. period.
If you back them into a corner, then everybody loses. Your boss/company in order to save face will be forced to maintain its position. You will have burned bridges and look like an extremist in your leaving.
I think some of these guys get too obsessed with their own points of view. And I would hope that a JOURNALIST would stay on the facts and not make judgements. But, maybe I suffer from the same problem that they do, dreaming of (my idea of) a perfect world.
You make a very good argument, and I agree with you on most points but, I might disagree on some details.
Although I agree with you on the role of evolution, I disagree with using it as justification. Primitive man also killed his competition for a better chance of propagation. As for our biological requirements, you are completely right.
As for having someone else (butcher) kill an animal vs killing it yourself, I believe that killing the animal yourself is more ethical. Look at how much meat is thrown away in this country. People who kill their own animals tend to have much more respect for the creature and do not waste them. Where I disagree with you is in the making a sport out of killing the creature. I have butcherd a few animals (goats, sheep, and pig) for BBQ's. However, I try to make it quick, simple, and as painless as possible.
Now, I do understand the desire for the sport, hell, we've got millions of years of evolution that make it desireable. There's the inrush of all kinds of hormones and nuerochemicals to make it a desireable activity. But, as a thinking being I find it distasteful to make sport out of killing.
Just my $0.02
Considering that the kids will be using computers for a very small percentage of their time at school at first glance, it would make sense to save money there inorder to maintain teacher salaries, or to invest in higher quality books. This could then help to increase the quality of education. (can you tell I'm a dreamer?)
But honestly, the decision about what OS and applications are used in schools should be based upon the usage and curriculum. If they are just using internet resources for research or typing docs, then a free OS is fine BSD or Linux. If they are running AutoCAD, 3D Studio, or other specialized programs then the program will dictate the OS. This really looks like it should be judged on a case by case basis and not mandated.