My MythTV makes my viewing habits network accessible. I may not publish it for general consumption, but that's a choice, not a patentable design decision.
No, it's because everyone else recognizes that the risk is that you end up using the same applications and web sites for a decade. People have to be able to try new stuff. It's a far greater risk to the organization to stagnate. You'll end up with people that are perfectly happy using decades-old software and visiting only internal web sites.
Companies need their employees to take on the risk of trying new applications and web sites without constantly asking for permission. It's a big driver of growth and advancement. For that they are willing to expose themselves to some small risk.
The biggest problem of all is that there is no standard to what should be allowed in a password. I have had banks tell me that punctuation is not allowed in passwords.
Some require uppercase, lowercase and numbers.
Some require specific complexity; most do not
Some require a symbol.
Some don't allow a symbol.
Some require at least 8 characters.
Some allow at most 8 characters.
Really, it's just stupid. Until some standards body issues requirements in internet password practices that financial institutions are required to implement, it is just a lost cause.
SunOS was BSD. Solaris is full-on SysV. And as others have already noted, de-dupe is on the wish list, not implemented. People don't read through Sun's marketing literature very well in these parts. Just yell "ZFS! ZFS! OMG!! ZFS!" and you'll get along fine here.
Don't get me wrong, ZFS is a nice, modern file system. But the hype around it is just bizarro. I don't think most folks really get what it can do today and what Sun *says* it will do at some undefined point in the future. It is certainly better than anything previously available as part of the core Solaris OS. People shelled out megabucks to Veritas to deal with the lack LVM and a decent file system in older versions of Solaris.
I would not discourage potential developers like this, we all know that GCC is not perfect and that is (partly) because there is no real open source project to compete with GCC.
I would and do, because I fundamentally disagree with your premise. If developers are going spend time on a compiler, do it on a compiler that targets multiple platforms, not just slightly different operating systems on the same CPU. Getting an optimizing compiler right across multiple CPU architectures is HARD. GCC has already forked twice in my experience (pgcc, egcs). If needed, it will happen again. In this way all open source programs are their own competition.
The real problem with GCC is that there are not enough developers working on it. The number of people that can usefully contribute to a compiler like GCC is vanishingly small. Even those that have compiler experience rarely have experience with handling the subtle and not so subtle differences between completely different CPU families. Encouraging that group to fracture even further is an even bigger sin in my book.
Lest anyone think otherwise, I don't see any need to fork GCC. I have not seen the developers reject reasonable enhancements from contributors. On the contrary; they don't have enough developers working to support new chips, keep up with new language features, and fix outstanding issues.
Yes, when Intel and MSFT make compilers that target UltraSPARC, Itanic, and POWER (all, not some) then I'll have a look-see again.
Open Watcom enjoys virtually no support. It is not going anywhere. It's another sucky piece of code that was no longer competitive in the marketplace. It needs developers like a fish needs a bicycle. No one in their right mind would waste time adding support for this compiler to KDevelop.
You know, the only people that I know that seriously dislike GCC are the commercial compiler venders. It's not perfect, but it has a major advantage that no other compiler has -- it frees the developer from worrying about vendor specific compiler issues when writing cross-platform code. One less thing to worry about.
I like it, but it is not C++ (yet). auto, for-range loops, and lambda functions are going to do wonders for making C++ less verbose and more expressive.
Property taxes don't pay to keep sea lanes open or air traffic well controlled. They don't pay for border guards, GPS and weather satellites nor a myriad other things we rely on every day to get groceries in our pantry.
Oh -- come on! Terror?!? Hardly. Bloody bodies in the street is terror. Attacking a corporation's infrastructure (even when it is depended upon by the public) without the intent to harm individuals is not terrorism.
This is classic sabotage. It has a long and noble history.
No need for a bunch of hand-waving and off the cuff guesses. The article says 192GB in 12 slots (12 x 16GB). At ~5W per, that's a whopping 60W of power, 200% more than your average 4 slot, 20W power consumption from the RAM in the average home PC.
I don't know why companies just don't get *BSD working for them instead Linux. It would save them a lot of headaches.
Because the primary reason for the success of Linux is that it forces everyone to share their improvements. You get an exponential return on investment. The best you can ever hope for with BSD is an incremental return.
Then you might know of a product called PowerTier, later renamed to DataXtend CE. That was an ORM for C++ and Java from Persistence, which was also acquired by Progress. We started using that at version 5 or 6 around 2000/2001 time frame.
GLBA covers the bank data fiasco you mention. What we don't have is an enforcement arm. Laws against rape and murder are fairly useless without cops on the street. Same goes for laws governing corporate conduct.
We already to do a greater degree than most realize. Sure, there's HIPAA and others for data security that many folks know about. But there are other regulations on data quality, such as the U.S. postal service requiring a certain standard of data hygiene, called CASS certification, in order to do bulk mailings.
We use RT at my company. It's been in use for over three years. We're at the 150K ticket mark at this point with 300+ users. We use it for production processes, production support, CIT/helpdesk, systems admin, software development process and more. We use it a ton. The complaint that it slows down with a large number of tickets is a valid one. We also have a ton of ticket queues and a very busy home page which makes it even slower. But we're pushing something like 60K tickets a year right now so it's not slowing us down too much.
One thing that helped was to have it start feeding a Google Search Appliance with content on every update. Now we use the power of Google to index & search the content, which makes searching through tickets much more bearable.
WRT to item C on your list: birth control pills. It would be a completely different world without that medical wonder. Suddenly having hundreds of millions more fertile women in this world would cause lots o' problems.
Slashdot Mirror
My MythTV makes my viewing habits network accessible. I may not publish it for general consumption, but that's a choice, not a patentable design decision.
Companies need their employees to take on the risk of trying new applications and web sites without constantly asking for permission. It's a big driver of growth and advancement. For that they are willing to expose themselves to some small risk.
Some require uppercase, lowercase and numbers.
Some require specific complexity; most do not
Some require a symbol.
Some don't allow a symbol.
Some require at least 8 characters.
Some allow at most 8 characters.
Really, it's just stupid. Until some standards body issues requirements in internet password practices that financial institutions are required to implement, it is just a lost cause.
Don't get me wrong, ZFS is a nice, modern file system. But the hype around it is just bizarro. I don't think most folks really get what it can do today and what Sun *says* it will do at some undefined point in the future. It is certainly better than anything previously available as part of the core Solaris OS. People shelled out megabucks to Veritas to deal with the lack LVM and a decent file system in older versions of Solaris.
Sounds like a perfect use of the stimulus money Texas is getting from Uncle Sam.
I would not discourage potential developers like this, we all know that GCC is not perfect and that is (partly) because there is no real open source project to compete with GCC.
I would and do, because I fundamentally disagree with your premise. If developers are going spend time on a compiler, do it on a compiler that targets multiple platforms, not just slightly different operating systems on the same CPU. Getting an optimizing compiler right across multiple CPU architectures is HARD. GCC has already forked twice in my experience (pgcc, egcs). If needed, it will happen again. In this way all open source programs are their own competition.
The real problem with GCC is that there are not enough developers working on it. The number of people that can usefully contribute to a compiler like GCC is vanishingly small. Even those that have compiler experience rarely have experience with handling the subtle and not so subtle differences between completely different CPU families. Encouraging that group to fracture even further is an even bigger sin in my book.
Lest anyone think otherwise, I don't see any need to fork GCC. I have not seen the developers reject reasonable enhancements from contributors. On the contrary; they don't have enough developers working to support new chips, keep up with new language features, and fix outstanding issues.
Open Watcom enjoys virtually no support. It is not going anywhere. It's another sucky piece of code that was no longer competitive in the marketplace. It needs developers like a fish needs a bicycle. No one in their right mind would waste time adding support for this compiler to KDevelop.
You know, the only people that I know that seriously dislike GCC are the commercial compiler venders. It's not perfect, but it has a major advantage that no other compiler has -- it frees the developer from worrying about vendor specific compiler issues when writing cross-platform code. One less thing to worry about.
I like it, but it is not C++ (yet). auto, for-range loops, and lambda functions are going to do wonders for making C++ less verbose and more expressive.
Fluorescent Monkey Overlords would be a great name for a band.
Property taxes don't pay to keep sea lanes open or air traffic well controlled. They don't pay for border guards, GPS and weather satellites nor a myriad other things we rely on every day to get groceries in our pantry.
Oh, they accomplish more than that. Taxes provide infrastructure that allow people access to consume those goods and services.
As the maintainer of GLIBC, he has to be the steward for the greater good of all users. And sometimes that means pissing off a vocal constituency.
Oh -- come on! Terror?!? Hardly. Bloody bodies in the street is terror. Attacking a corporation's infrastructure (even when it is depended upon by the public) without the intent to harm individuals is not terrorism.
This is classic sabotage. It has a long and noble history.
That's just sad.
Oh, come on. Being funny isn't an achievement. Being modded "+5 Troll" is an achievement!
I'm more interested in what IBM will do with the SPARC processor and Solaris, and how that affects Fujitsu.
No need for a bunch of hand-waving and off the cuff guesses. The article says 192GB in 12 slots (12 x 16GB). At ~5W per, that's a whopping 60W of power, 200% more than your average 4 slot, 20W power consumption from the RAM in the average home PC.
I don't know why companies just don't get *BSD working for them instead Linux. It would save them a lot of headaches.
Because the primary reason for the success of Linux is that it forces everyone to share their improvements. You get an exponential return on investment. The best you can ever hope for with BSD is an incremental return.
Then you might know of a product called PowerTier, later renamed to DataXtend CE. That was an ORM for C++ and Java from Persistence, which was also acquired by Progress. We started using that at version 5 or 6 around 2000/2001 time frame.
We've moved on to KDevelop vs Eclipse. Don't even get me started about those Code::Blocks posers.
GLBA covers the bank data fiasco you mention. What we don't have is an enforcement arm. Laws against rape and murder are fairly useless without cops on the street. Same goes for laws governing corporate conduct.
We already to do a greater degree than most realize. Sure, there's HIPAA and others for data security that many folks know about. But there are other regulations on data quality, such as the U.S. postal service requiring a certain standard of data hygiene, called CASS certification, in order to do bulk mailings.
We use RT at my company. It's been in use for over three years. We're at the 150K ticket mark at this point with 300+ users. We use it for production processes, production support, CIT/helpdesk, systems admin, software development process and more. We use it a ton. The complaint that it slows down with a large number of tickets is a valid one. We also have a ton of ticket queues and a very busy home page which makes it even slower. But we're pushing something like 60K tickets a year right now so it's not slowing us down too much.
One thing that helped was to have it start feeding a Google Search Appliance with content on every update. Now we use the power of Google to index & search the content, which makes searching through tickets much more bearable.
Who needs friend tracking? What we need is Foe Tracking (tm).
WRT to item C on your list: birth control pills. It would be a completely different world without that medical wonder. Suddenly having hundreds of millions more fertile women in this world would cause lots o' problems.