I believe the person's point was more that State Capitalism was a bad thing because the state was involved. You essentially have the government sitting there trying to make up rules which benefit certain classes of people in the hopes of getting more tax revenue. Icky.
IIRC, Irix achieves this with a NUMA (Non-Uniform Memory Access) architecture. This basically means that all memory has a home, and accessing memory that's not on your current CPU requires a network request for each memory access. Most NUMA machines have a dedicated internal network, just for memory, but it's still needs to have applications that are designed to use it for it to work, which, of course, is your point.:-)
Threaded applications use shared memory to communicate between threads. Distributed shared memory schemes that aren't carefully tailored to the application they're designed for are very slow right now.
An application currently has to be split up in a such a way that the different parts need to communicate with eachother in the most minimal way because communication overhead is large.
Even then, it helps if they communicate with eachother in a way in which the results arrive at the computer that needs them before they're asked for, which is even harder.
SETI@Home works because there's virtually no communication between computers. The only thing that could make SETI@Home faster is to start downloading a new data set just before the current one is finished so you never have a break in doing the hard, CPU intensive mathematics.
He was criticizing the person before him about complaining that people who didn't get the 'secret' information on DNS vulnerabilities and subsequently had their boxes cracked had no business keeping anything important on a box directly connected to the Internet anyway.
My reply was that there are many ways in which this is very unpleasantly damaging even if the box has nothing important on it, and that the abusive person had done nothing to refute the original poster's points.
Except for two small problems. One, every comprimised box becomes yet another weapon to use in a DDoS attack. Two, recovering from a comprimise is an incredible pain and takes a lot of time and effort.
This is regardless of whether or not you kept 'top secret' information on a box connected directly to the Internet or not.
Lastly, you are obviously a complete jerk and idiot since you can't seem to make any point at all without resorting to abusive language and calling people names.
As an addendum, almost any code written for The StreamModule System is immune to buffer overflows because of the way buffers are handled. It's really not hard. The tools are available.
I've written C++ code that is largely immune to buffer overflows because of the manner in which it's written. It's actually not too hard to do, and simply requires a different mindset when dealing with the code.
With a filesystem that uses a linear search to find a file in a directory, maildir is an awful beast. With a filesystem that has fast directories, such as reiserfs, I would bet maildir would beat mbox hands down in almost anyy comparison you could think of.
The only problem maildir would have then is that you have to open every file in the directory to get a header list.
I will echo the response of another and say that the type of testing that was talked about in that book, and the type of testing that XP advocates are different things.
XP also combines extensive unit testing with a couple of processes (pair programming and refactoring) that mimic what you might achieve with formal inspections without actually having formal inspections.
Threading is evil and should be avoided. Sometimes, the evil that is threading is necessary, or the most logical way to accomplish something. Usually it's overused for things (like handling asynchronous behavior (i.e. network/socket communication)) that there are better solutions for.
My biggest complain about Java right now is that it has an I/O model that requires the use of multiple threads to deal with more than one socket at a time, for instance.
Umm, I can't figure out if you're serious or trolling or ignorant.
Linux drivers can, and are updaed independently of the kernel all the time. In fact, you can unload an old driver and load in a new driver all without rebooting. Your users might not even notice. No, it's not really a 'microkernel', but it shares a lot of a microkernel's features in that regard.
Windows requires a reboot every time you loaded a driver, last time I checked. Also, drivers conflicts and incompatibilities are rampant. One of the whole points of Windows 2000 was for Microsoft to start making sure that the drivers vendors released were lots less buggy so their system wouldn't BSOD as often as it used to.
Near as I can tell, while Windows NT/2000's might be based on a microkernel, it has no effect on the system as a whole aside from the additional technical marketing buzzwords people can use to describ it.
A repost of a comment as an article is just fine by me, and this is the kind of news that never really goes out of date until everyone's heard it already.
I don't think most people even read the comment. I didn't.
Strangely enough, the article was making the point that copyrights and patents are actually not a part of the free-market system and are really a form of protectionism.
Of course, actually addressing those points would've prevented you from making this long hand-wringing rant complaining about what the end result of having a copyright and patent system are and wanting to go back to the 'good old days' so the cycle can start all over again.
I long ago decided that copyrights and patents are not strictly necessary. I had kinda felt that way, for awhile, but had many of the same qualms you did, and then I heard about Cygnus (now owned by RedHat), and I never had another.
When trading purely services, you are in fact, using your own property, namely your own body, mind, intellect. These belong to you and any services you provide would be based on the use of your property.
If someone wants you to mow the lawn, you would be providing a service. You might use some property to do it more efficiently than otherwise. You might use a lawnmower you own. You use property all the time in the commission of providing a service.
But, the property is in no way a part of the actual trade for services. You aren't renting your body or mind to someone for an hour. You aren't lending the person your lawnmower, you're making an agreement to make sure that something is accomplishmeded. While property may be used to cary out your end of the contract and things you do may affect someone else's property, the property itself is not the subject of the monetary exchange.
I didn't get any of those benefits at all, and the job was above minimum wage (by 10-20%), but in my area that could easily have been attributable to market conditions, not union wages.
We were lucky to have generally sane management not into playing games. The only ridiculous thing I was ever called out for was talking to the cashiers while working in ways they disliked, mostly because they were odd or above their heads. It actually was only one cashier, and she had seniority. *sigh*
It's hit or miss. Unions can be just as evil as big companies. Unions can be good.
It's better than the BSD lisence. It prevents companies from stealing from the public domain and claiming it as their own. That's real freedom. It's the kind of freedom that creates the stability that people are willing to build around.
Anyway, enough of my arguing. I just enjoy getting you BSD people to show your true faces. Nothing is surer for that purpose than mentioning the GPL.
I'm very suspicious of unions. About as suspicious as I am of large corporations. But, they have their uses. I'm all for mandatory open shops. If workers at a company don't see the need to join a union, maybe it doesn't need one. If the company changes its tune, people will learn, and join the union.
It's not FUD, it's true. I was in a very similar situation when I worked as a bagboy at a grocery store. I made barely above minimum wage, and was forced to pay union dues. It was ridiculous and annoying. If the union had struck, I would've crossed the picket line in an instant, and I suspect most people working there would've too.
Also, $42/mo is astronomical, IMHO. And I care a lot more about a healthy relationship with management than pay or vacation time anyway.
I actually kind of favor a tech union because I think management tends to treat their employees very badly (in terms of forced overtime without pay (for salaried) and job stress) and don't listen to them. I don't know if a union could change this, but I don't know of anything that would have a better chance. But if it ever became like any of the major labor unions I'd want to see it wither away and die.
The worst unions protect mediocre or poor workers, are corrupt, and force you to be a member. They really do. I've heard too many detailed first-hand stories of actual incidents from too many different unconnected people for it to be a made up hoax.
Anytime a BSD bigot puts down the GPL as not being 'free' I'm going to get upset and angry.
Generally, restricting freedom tends to cause economic problems. If the GPL restricts freedom, why aren't there economic problems in the GPL based Open Source community? Seems to me that the flow of informtion and level of activity is much higher in the GPL based parts of the community. Kinda tells me which license is better at promoting freedom.
To me, those kind of assinine comments about licenses are a perfect example of the inferiority complex (not claiming BSD is inferior, for those who are victims of this complex) combined with an elitist attitude that the BSD community is noted for.
The Tucows site had obvious incredibly stupid, misguided and wrong information on it. This much is true. I also have no doubt that some of the behavior that they complain about is also what happened.
I'm perfectly happy to be a friend of the BSD community, but I get the distinct impression that they'd prefer I not be.
Slashdot Mirror
I believe the person's point was more that State Capitalism was a bad thing because the state was involved. You essentially have the government sitting there trying to make up rules which benefit certain classes of people in the hopes of getting more tax revenue. Icky.
I see, if someone can't think of the mystic google search terms, they must be a moron. *sigh*
IIRC, Irix achieves this with a NUMA (Non-Uniform Memory Access) architecture. This basically means that all memory has a home, and accessing memory that's not on your current CPU requires a network request for each memory access. Most NUMA machines have a dedicated internal network, just for memory, but it's still needs to have applications that are designed to use it for it to work, which, of course, is your point. :-)
Threaded applications use shared memory to communicate between threads. Distributed shared memory schemes that aren't carefully tailored to the application they're designed for are very slow right now.
An application currently has to be split up in a such a way that the different parts need to communicate with eachother in the most minimal way because communication overhead is large.
Even then, it helps if they communicate with eachother in a way in which the results arrive at the computer that needs them before they're asked for, which is even harder.
SETI@Home works because there's virtually no communication between computers. The only thing that could make SETI@Home faster is to start downloading a new data set just before the current one is finished so you never have a break in doing the hard, CPU intensive mathematics.
He was criticizing the person before him about complaining that people who didn't get the 'secret' information on DNS vulnerabilities and subsequently had their boxes cracked had no business keeping anything important on a box directly connected to the Internet anyway.
My reply was that there are many ways in which this is very unpleasantly damaging even if the box has nothing important on it, and that the abusive person had done nothing to refute the original poster's points.
Except for two small problems. One, every comprimised box becomes yet another weapon to use in a DDoS attack. Two, recovering from a comprimise is an incredible pain and takes a lot of time and effort.
This is regardless of whether or not you kept 'top secret' information on a box connected directly to the Internet or not.
Lastly, you are obviously a complete jerk and idiot since you can't seem to make any point at all without resorting to abusive language and calling people names.
As an addendum, almost any code written for The StreamModule System is immune to buffer overflows because of the way buffers are handled. It's really not hard. The tools are available.
I've written C++ code that is largely immune to buffer overflows because of the manner in which it's written. It's actually not too hard to do, and simply requires a different mindset when dealing with the code.
With a filesystem that uses a linear search to find a file in a directory, maildir is an awful beast. With a filesystem that has fast directories, such as reiserfs, I would bet maildir would beat mbox hands down in almost anyy comparison you could think of.
The only problem maildir would have then is that you have to open every file in the directory to get a header list.
I will echo the response of another and say that the type of testing that was talked about in that book, and the type of testing that XP advocates are different things.
XP also combines extensive unit testing with a couple of processes (pair programming and refactoring) that mimic what you might achieve with formal inspections without actually having formal inspections.
A very central tenent of XP is testing. It's probably the thing that does the most to hold XP together.
Threads introduce non-deterministic interactions between different parts of a program. This can make adequate testing a pain.
Threading is evil and should be avoided. Sometimes, the evil that is threading is necessary, or the most logical way to accomplish something. Usually it's overused for things (like handling asynchronous behavior (i.e. network/socket communication)) that there are better solutions for.
My biggest complain about Java right now is that it has an I/O model that requires the use of multiple threads to deal with more than one socket at a time, for instance.
Umm, I can't figure out if you're serious or trolling or ignorant.
Linux drivers can, and are updaed independently of the kernel all the time. In fact, you can unload an old driver and load in a new driver all without rebooting. Your users might not even notice. No, it's not really a 'microkernel', but it shares a lot of a microkernel's features in that regard.
Windows requires a reboot every time you loaded a driver, last time I checked. Also, drivers conflicts and incompatibilities are rampant. One of the whole points of Windows 2000 was for Microsoft to start making sure that the drivers vendors released were lots less buggy so their system wouldn't BSOD as often as it used to.
Near as I can tell, while Windows NT/2000's might be based on a microkernel, it has no effect on the system as a whole aside from the additional technical marketing buzzwords people can use to describ it.
Hey, you replied in the postings section. *grin* And you reply is so dry I can't tell if it's a joke or not. :-)
A repost of a comment as an article is just fine by me, and this is the kind of news that never really goes out of date until everyone's heard it already.
I don't think most people even read the comment. I didn't.
Strangely enough, the article was making the point that copyrights and patents are actually not a part of the free-market system and are really a form of protectionism.
Of course, actually addressing those points would've prevented you from making this long hand-wringing rant complaining about what the end result of having a copyright and patent system are and wanting to go back to the 'good old days' so the cycle can start all over again.
I long ago decided that copyrights and patents are not strictly necessary. I had kinda felt that way, for awhile, but had many of the same qualms you did, and then I heard about Cygnus (now owned by RedHat), and I never had another.
But, the property is in no way a part of the actual trade for services. You aren't renting your body or mind to someone for an hour. You aren't lending the person your lawnmower, you're making an agreement to make sure that something is accomplishmeded. While property may be used to cary out your end of the contract and things you do may affect someone else's property, the property itself is not the subject of the monetary exchange.
I just felt the need to be nitpicky.
I didn't get any of those benefits at all, and the job was above minimum wage (by 10-20%), but in my area that could easily have been attributable to market conditions, not union wages.
We were lucky to have generally sane management not into playing games. The only ridiculous thing I was ever called out for was talking to the cashiers while working in ways they disliked, mostly because they were odd or above their heads. It actually was only one cashier, and she had seniority. *sigh*
It's hit or miss. Unions can be just as evil as big companies. Unions can be good.
It's better than the BSD lisence. It prevents companies from stealing from the public domain and claiming it as their own. That's real freedom. It's the kind of freedom that creates the stability that people are willing to build around.
Anyway, enough of my arguing. I just enjoy getting you BSD people to show your true faces. Nothing is surer for that purpose than mentioning the GPL.
*grin* Yeah it is. That was the point.
In all likelihood, all the companies in that industry were unionized under the same union. His dad would've had the same problem everywhere.
Umm, what is the iron law of political science?
Hear Here!
I'm very suspicious of unions. About as suspicious as I am of large corporations. But, they have their uses. I'm all for mandatory open shops. If workers at a company don't see the need to join a union, maybe it doesn't need one. If the company changes its tune, people will learn, and join the union.
It's not FUD, it's true. I was in a very similar situation when I worked as a bagboy at a grocery store. I made barely above minimum wage, and was forced to pay union dues. It was ridiculous and annoying. If the union had struck, I would've crossed the picket line in an instant, and I suspect most people working there would've too.
Also, $42/mo is astronomical, IMHO. And I care a lot more about a healthy relationship with management than pay or vacation time anyway.
I actually kind of favor a tech union because I think management tends to treat their employees very badly (in terms of forced overtime without pay (for salaried) and job stress) and don't listen to them. I don't know if a union could change this, but I don't know of anything that would have a better chance. But if it ever became like any of the major labor unions I'd want to see it wither away and die.
The worst unions protect mediocre or poor workers, are corrupt, and force you to be a member. They really do. I've heard too many detailed first-hand stories of actual incidents from too many different unconnected people for it to be a made up hoax.
Anytime a BSD bigot puts down the GPL as not being 'free' I'm going to get upset and angry.
Generally, restricting freedom tends to cause economic problems. If the GPL restricts freedom, why aren't there economic problems in the GPL based Open Source community? Seems to me that the flow of informtion and level of activity is much higher in the GPL based parts of the community. Kinda tells me which license is better at promoting freedom.
To me, those kind of assinine comments about licenses are a perfect example of the inferiority complex (not claiming BSD is inferior, for those who are victims of this complex) combined with an elitist attitude that the BSD community is noted for.
The Tucows site had obvious incredibly stupid, misguided and wrong information on it. This much is true. I also have no doubt that some of the behavior that they complain about is also what happened.
I'm perfectly happy to be a friend of the BSD community, but I get the distinct impression that they'd prefer I not be.