Blackdown has received more publicity than they ever would have if Sun had mentioned them in the first place. Some people are hearing about them for the first time, or are hearing names of Blackdown individuals for the first time. Don't count these guys out. They'll likely move ahead, and if not - they'll surely be successful whatever they do.
Excellent suggestion! I downloaded Mozilla as you said and this is my first (but surely will not be my last) post using it.
The interface is clean and the rendering is gorgeous. Of course, the build of the hour is a little less than beta quality (be gentle if you download tonight's build). However, this project is clearly on track to become a serious browser - there's hope, and I wish I was a contributor.
I see that the posts with the most optimistic tone have floated to the top and the doomsayers have been knocked to the bottom. So, moderate me down if you must.
I'd like to say I am the coolest hacker and have only ever written l33t c0de. But, the fact is I'm one of those programmers who spent most of the '80s and early '90s writing non-Y2K compliant code for systems that companies still count on today. So, I felt I had to have some input.
I feel that there is a possibility, albeit very small, that we will see serious trouble. There are not enough humans on the planet to wipe out the problem in time. Many companies like the one I work for are turning away customers, while other customers are unbelievably not calling for Y2K help at all (and we don't have the time to call them). So the question is, what will be the damage, if any? How closely linked are the banks of the world? Doomsayers in the bank industry have said (aside from the Y2K issue altogether) for years that a domino toppling effect is possible. Could a few non-prepared banks light the fuse?
I know that 5-10% of our client base will not be ready. That means that people will have downtime in January, period. One of our customers is the energy provider for the state I live in. The systems we Y2K-proofed for them only had to pass the most preliminary tests to be considered Y2K-OK. You want to talk about wacky people? Forget the militia, I took a trip in October to the aforementioned energy provider of power and natural gas and in the IS departments there were dozens of Y2K posters spread around - one poster with a big nasty fictitious insect (supposedly the Y2K bug), another with "Is YOUR department ready?", countdown clocks galore.
It has been well documented that the human nature is to insist that catastrophe cannot happen until it does. Look at people warned of volcanic activity, even at Mount St. Helen's that refused to evacuate and died as a result.
Back to my opening argument: the possibility is very minute, but as one of a large army of programmers who have together written millions or billions of lines of code that will be depended on in the new year, I refuse to stick my head in the sand. I personally know too many programmers who have written s@#! that won't work on Jan.1 So, what will happen? We can only speculate, and only time will tell.
Red Hat has stated that they are buying up whatever makes the most sense. Despite the big bag of money they've gained from their IPO, Bob Young has said that they can't buy everything they want. This is a Good Thing; we need room for the rest of us, rather than one giant buying everything in sight.
I enjoyed this section more than I thought I would. I'm always interested in info on available IDE's as well as their pros and cons. It was interesting to see how quickly KDevelop is gaining proponents. Whether or not it's an outstanding product in it's current form, kudos to SGI for contributing to open source, and being savvy enough to have Dean diligently peruse these./ postings. Oh and before I forget, the KDevelop boosters didn't seem to notice what seemed to be the most important potential with Jessie: it's "focus on scalability, providing multi-process and multi-thread support for large applications". We can only gain from this contribution.
VMWare is totaly cool and it's mind numbing to see NT boot in a window under Linux. I'm using the beta from http://vmware.com for Linux (so far slow like dog) to run a couple apps that are NT only (minor but necessary applications). Remember, MS buys only stuff that they see as important and can't duplicate (also see fear). They can't stand the thought of a Linux-only killer app, now or future.
Furthermore, MS can generate scripts from the logs: the NT scripts can be taken to their labs for debugging, the Linux scripts can be saved for future considerations. But not to worry, the only way Linux can be crushed is if _we stop developing it_
Slashdot Mirror
Surf within VMware with no personal info on file...then it doesn't matter (see VMware for Linux).
Blackdown has received more publicity than they ever would have if Sun had mentioned them in the first place. Some people are hearing about them for the first time, or are hearing names of Blackdown individuals for the first time.
Don't count these guys out. They'll likely move ahead, and if not - they'll surely be successful whatever they do.
The interface is clean and the rendering is gorgeous. Of course, the build of the hour is a little less than beta quality (be gentle if you download tonight's build). However, this project is clearly on track to become a serious browser - there's hope, and I wish I was a contributor.
I'd like to say I am the coolest hacker and have only ever written l33t c0de. But, the fact is I'm one of those programmers who spent most of the '80s and early '90s writing non-Y2K compliant code for systems that companies still count on today. So, I felt I had to have some input.
I feel that there is a possibility, albeit very small, that we will see serious trouble. There are not enough humans on the planet to wipe out the problem in time. Many companies like the one I work for are turning away customers, while other customers are unbelievably not calling for Y2K help at all (and we don't have the time to call them). So the question is, what will be the damage, if any? How closely linked are the banks of the world? Doomsayers in the bank industry have said (aside from the Y2K issue altogether) for years that a domino toppling effect is possible. Could a few non-prepared banks light the fuse?
I know that 5-10% of our client base will not be ready. That means that people will have downtime in January, period. One of our customers is the energy provider for the state I live in. The systems we Y2K-proofed for them only had to pass the most preliminary tests to be considered Y2K-OK. You want to talk about wacky people? Forget the militia, I took a trip in October to the aforementioned energy provider of power and natural gas and in the IS departments there were dozens of Y2K posters spread around - one poster with a big nasty fictitious insect (supposedly the Y2K bug), another with "Is YOUR department ready?", countdown clocks galore.
It has been well documented that the human nature is to insist that catastrophe cannot happen until it does. Look at people warned of volcanic activity, even at Mount St. Helen's that refused to evacuate and died as a result.
Back to my opening argument: the possibility is very minute, but as one of a large army of programmers who have together written millions or billions of lines of code that will be depended on in the new year, I refuse to stick my head in the sand. I personally know too many programmers who have written s@#! that won't work on Jan.1 So, what will happen? We can only speculate, and only time will tell.
same year! Coincidence? I think not!! :)
Red Hat has stated that they are buying up whatever makes the most sense. Despite the big bag of money they've gained from their IPO, Bob Young has said that they can't buy everything they want. This is a Good Thing; we need room for the rest of us, rather than one giant buying everything in sight.
I enjoyed this section more than I thought I would. I'm always interested in info on available IDE's as well as their pros and cons. It was interesting to see how quickly KDevelop is gaining proponents. ./ postings.
Whether or not it's an outstanding product in it's current form, kudos to SGI for contributing to open source, and being savvy enough to have Dean diligently peruse these
Oh and before I forget, the KDevelop boosters didn't seem to notice what seemed to be the most important potential with Jessie: it's "focus on scalability, providing multi-process and multi-thread support for large applications".
We can only gain from this contribution.
VMWare is totaly cool and it's mind numbing to see NT boot in a window under Linux. I'm using the beta from http://vmware.com for Linux (so far slow like dog) to run a couple apps that are NT only (minor but necessary applications). Remember, MS buys only stuff that they see as important and can't duplicate (also see fear). They can't stand the thought of a Linux-only killer app, now or future.
Furthermore, MS can generate scripts from the logs: the NT scripts can be taken to their labs for debugging, the Linux scripts can be saved for future considerations. But not to worry, the only way Linux can be crushed is if _we stop developing it_