Not to be a party pooper but I believe that Corel was already in hot water before they received an infusion of cash from Microsoft. Their Corel Linux dsitribution was not receiving rave reviews and CorelOffice for Linux was less than stellar. I'm pretty sure that Corel was screwed before Microsoft got involoved.
Hmmm... read up on the LoadLibrary call in the Win32 SDK. You can solve the problem of DLL versioning by putting a copy of the DLL you need in the same directory as your application. It will be loaded first, before any of the libraries in Windows\System(32).
Boy, I am sure glad that we have _elitist_ SOBs on Earth that would rather nuke the rest of us than attempt to solve any of the problems. From those of us in the "trenches", doing charity work and other community service acts is one of the more worthwhile and rewarding things we do with our lives. Sorry sir, but _your_ attitude depresses me!
Ian Baird
1) Just because he's sentenced to 19 years, doesn't mean he'll do 19 years.
2) Breaking into a computer is viewed by many corporations in the same way as if you broke into their company headquarters, poked around in their file cabinets (if there are any), and then left a note with your name, address and home phone explaining who you were, what you had done, and that you "didn't see anything confidential, steal stuff, or otherwise molest important items."
I'm sorry to have to say it, but this kid was a friggin' idiot.
Yep, let's get the government in here. They were the "pioneers" of the 5-hour work day in the 1930's on the Tennessee Valley Authority projects. Yep, I want to live in a company cottage and be told when I have to go to bed as well. This idea takes the idea of the "nanny state" to another level and unfortunately won't solve the problem of sleeplessness by itself. Sleep is hard to come by unless it is also balanced with a healthy diet and a decent exercise regimen.
Let's leave the feds to the jobs that they were restricted to in the U.S. Constitution.
1) Access to the registry works
2) Linux applications frequently update stuff in/usr/lib (or equivalent) and/or/etc
The registry is basically a databse. It's optimized for the type of access that you are speaking of and it really won't slow down unless it becomes fragmented.
IMHO, one of the largest problems with Windows is a lack of a coherent versioning system for shared libs. Shared libs are often overwritten ad hoc causing failures in seemingly unrelated applications. *NIX's method of version numbering the file name (eg libc.x.y.z) seems to be quite sufficient.
Hmm, maybe if software giants like Microsoft were legally liable for the software products they sold, this wouldn't happen. What would happen to Masterlock if they sold locks that simply unlocked after one sharp tug, or all had the same combination? Their collective ass would end up in court, that's what. Thanks to the some of the recent laws passed in this country though, it looks like that might never happen to large companies selling crap software in the United States.
Please do not belittle the importance of the American Revolution by equating it to the Microsoft case. Microsoft, more than likely, would have been brought down by market forces and the eventual dominance of open-source.
Take it from me, a professional developer with 5 years of experience in creating software solutions for Windows 95, 98, and NT that developers are looking for any excuse they can to use open-source. An API to a developer is like a toolbox to a mechanic. Tools with a hard-to-use and non-intuitive interface do not help a auto-mechanic any more than they help a software developer. Unless your company has beaucoup bucks to shell out for the MSDN Universal Subscription, which is a far cry from the level of documentation one receives with Linux, FreeBSD, or any of the other open-source operating systems of note, it is very difficult to write good, dependable code for your customers. I don't approve of the anti-competitive actions Microsoft took, but I fear my government more than I fear a company led by a man with the foresight to predict that no user would ever need more than 64K of RAM.
People will write the most complex and featureful software they can that stays within the level of buggyness they can tolerate.
Unfortunately, you prove my point here. There is no "silver bullet" which will solve all of the problems and challenges of software engineering. The idea that sold people on OO was one of re-use and less complexity. The lesson that the industry should learn from this experience is that a paradig-shift is no substitute for engineering standards and quality-control. What good is a feature if it fails 1 time out of four?
OOP, componenent architectures, and open source are snakeoil solutions to a problem that begs for standardization and structure. They have their uses but not one of the group can be called the messiah of computer science. Standards are good.
Beware software "artists"! The honeymoon is almost over for us...
An excellent article by a man who obviously calls 'em as he sees 'em. The OO paradigm promised to save the world of software engineering from bugs, complexity, and maintenance difficulties, but if the last 5 or 6 years are to be considered as indicators for future performance, it's not worth the hype. Although Perl is often accused of having a "bolted-on" OO interface, the base language is stable, supported, and widely used. Standards will only help to push its acceptance with the suits.
Personally, I'd prefer to rely upon a language that delivers on the promise of "write once, run anywhere":) In my experience, Perl does just that.
Flames to/dev/null and let the language holy wars begin!
Re:No, it's something else
on
Boo No More
·
· Score: 1
Come over here and look at some of American society's poorest. I promise you, unless you starve yourself, it is impossible to starve in the United States now a days. As a matter of fact, it probably wouldn't hurt for about 60% of the population to lose some weight. As for healthcare, look at Medicard, Medicaid, etc.:) Just my two cents.
Also, on a similar note, if you have the slightest bit of flakiness with your hardware, Mandrake will die, and die badly. One of my friends was trying to set up IP Masq, and was using Mandrake. It was doing some sort of "ide optimization" crap that did only one thing - render the system unusable/unbootable. (hung during init cycle). Gave him a copy of RedHat 6.1, installed and ran like a charm.
Did you notice the little checkbox during the Mandrake install that enables hard drive optimisation and warns that it can cause problems??? Sounds like a case of RTFM to me.
It's people like you who want to censor the net. Who the hell gives you the right to say what is irrelevant? This isn't even your own damn website! Too bad some self-important sad sack feels that it's his duty to save us from April Fool's day. Sod off and die.
My friends, The action being taken by Andover.net is simply irresponsible and morally wrong. I will personally protest the action by setting myself on fire in front of the courthouse and running around screaming curses against the traitorous CmdrTaco. I may die, my body may be consumed by the hot flames, but my memory will live on in the hearts of all/.ers everywhere.
After living in Europe (especially the UK) for a few years I can tell you this: There is nothing we can do to prevent a determined individual or group from commiting an act of terrorism. Unfortunately, there is not a lot we can do except go after the supporters of the terrorists and hit them before they hit us. Also, we need to consider what we are paying our current airport security personnel. I believe it is Swissair that provides bonuses for security personnel that find contraband and when was the last time you heard of a Swissair jet being blown up or hijacked? No machine can fix the problem of poorly motivated people. My main problem with the deal is that in allowing ourselves to be searched so personally gives us a false sense of security. There will always be _bad_ people in the workd who will want to do us harm. Until the bad guys are dealt with, we will have no security. It always seems that whoever trades freedom for security usually ends up with neither.
I took the DeCSS stuff off of my site and replaced it with a link to OpenDVD.org, which has a much better tarball of _all_ the linux software they could scrounge up pertaining to DVDs. Hope it helps.
I bet a DOS box in a closet with a generator and a ups supplying it would rack up a very impressive uptime. Unfortunately the box running DOS would be about as useful to me as a box running *BSD would be. I use my computer as a workstation/development platform where hardware support is a priority. Now if I were to run a server, I'd probably use BSD or Solaris. Anyways, it's all pretty pointless because anyone with any experience in the field at all knows the relative strengths and weakness of each OS already.
Do you _actually_ enjoy urinating into the wind?
Offtopic: I've got the DeCSS stuff up on my site at http://www.rtmfd.net
I must beg to differ with you on this one. Borland C++ 5.0 was a piece of crap. As a commercial software developer, I found it all but useless for creating even the most rudimentary of Win32 GUI apps. Yes, some of these compiler issues were fixed in later patches, but I had deadlines to meet. It was too little, too late for a $500 product.
Slashdot Mirror
Dear God! Now the friggin lunatics on /. are blaming MS with killing kids! There are some people obviously foaming at the mouth here. Get a life.
Mmmm... shark!
:)
Maybe we can get humans to start growing fins as well, so we don't have to slaughter sharks for theirs
Not to be a party pooper but I believe that Corel was already in hot water before they received an infusion of cash from Microsoft. Their Corel Linux dsitribution was not receiving rave reviews and CorelOffice for Linux was less than stellar. I'm pretty sure that Corel was screwed before Microsoft got involoved.
It's tough to keep your government from taking away your inalienable rights when you can't threaten them with deadly force :)
Thanks for reminding me that it's time to renew that NRA membership of mine...
Hmmm... read up on the LoadLibrary call in the Win32 SDK. You can solve the problem of DLL versioning by putting a copy of the DLL you need in the same directory as your application. It will be loaded first, before any of the libraries in Windows\System(32).
It's not as nice as the *NIX way, but it works.
The reason to use JAVA is simple. The shit is so slow and resource intensive that you are just about forced to have a `n UltraSparc to run the crap :)
:)
Who sells UltraSparcs again???
Yep, but in the case of the intruder in my house, I reserve the right to kill the cocksucker. Just another 2 cents.
Boy, I am sure glad that we have _elitist_ SOBs on Earth that would rather nuke the rest of us than attempt to solve any of the problems. From those of us in the "trenches", doing charity work and other community service acts is one of the more worthwhile and rewarding things we do with our lives. Sorry sir, but _your_ attitude depresses me! Ian Baird
Great! Where's your sourceforge project and how can I compile your code? :)
Gcc, emacs, and vi are free...
Two things:
1) Just because he's sentenced to 19 years, doesn't mean he'll do 19 years.
2) Breaking into a computer is viewed by many corporations in the same way as if you broke into their company headquarters, poked around in their file cabinets (if there are any), and then left a note with your name, address and home phone explaining who you were, what you had done, and that you "didn't see anything confidential, steal stuff, or otherwise molest important items."
I'm sorry to have to say it, but this kid was a friggin' idiot.
Yep, let's get the government in here. They were the "pioneers" of the 5-hour work day in the 1930's on the Tennessee Valley Authority projects. Yep, I want to live in a company cottage and be told when I have to go to bed as well. This idea takes the idea of the "nanny state" to another level and unfortunately won't solve the problem of sleeplessness by itself. Sleep is hard to come by unless it is also balanced with a healthy diet and a decent exercise regimen.
Let's leave the feds to the jobs that they were restricted to in the U.S. Constitution.
You obviously don't understand how:
/usr/lib (or equivalent) and/or /etc
1) Access to the registry works
2) Linux applications frequently update stuff in
The registry is basically a databse. It's optimized for the type of access that you are speaking of and it really won't slow down unless it becomes fragmented.
IMHO, one of the largest problems with Windows is a lack of a coherent versioning system for shared libs. Shared libs are often overwritten ad hoc causing failures in seemingly unrelated applications. *NIX's method of version numbering the file name (eg libc.x.y.z) seems to be quite sufficient.
Anyway, that's my 2 cents.
Hmm, maybe if software giants like Microsoft were legally liable for the software products they sold, this wouldn't happen. What would happen to Masterlock if they sold locks that simply unlocked after one sharp tug, or all had the same combination? Their collective ass would end up in court, that's what. Thanks to the some of the recent laws passed in this country though, it looks like that might never happen to large companies selling crap software in the United States.
Please do not belittle the importance of the American Revolution by equating it to the Microsoft case. Microsoft, more than likely, would have been brought down by market forces and the eventual dominance of open-source.
Take it from me, a professional developer with 5 years of experience in creating software solutions for Windows 95, 98, and NT that developers are looking for any excuse they can to use open-source. An API to a developer is like a toolbox to a mechanic. Tools with a hard-to-use and non-intuitive interface do not help a auto-mechanic any more than they help a software developer. Unless your company has beaucoup bucks to shell out for the MSDN Universal Subscription, which is a far cry from the level of documentation one receives with Linux, FreeBSD, or any of the other open-source operating systems of note, it is very difficult to write good, dependable code for your customers. I don't approve of the anti-competitive actions Microsoft took, but I fear my government more than I fear a company led by a man with the foresight to predict that no user would ever need more than 64K of RAM.
People will write the most complex and featureful software they can that stays within the level of buggyness they can tolerate.
Unfortunately, you prove my point here. There is no "silver bullet" which will solve all of the problems and challenges of software engineering. The idea that sold people on OO was one of re-use and less complexity. The lesson that the industry should learn from this experience is that a paradig-shift is no substitute for engineering standards and quality-control. What good is a feature if it fails 1 time out of four?
OOP, componenent architectures, and open source are snakeoil solutions to a problem that begs for standardization and structure. They have their uses but not one of the group can be called the messiah of computer science. Standards are good.
Beware software "artists"! The honeymoon is almost over for us...
An excellent article by a man who obviously calls 'em as he sees 'em. The OO paradigm promised to save the world of software engineering from bugs, complexity, and maintenance difficulties, but if the last 5 or 6 years are to be considered as indicators for future performance, it's not worth the hype. Although Perl is often accused of having a "bolted-on" OO interface, the base language is stable, supported, and widely used. Standards will only help to push its acceptance with the suits.
:) In my experience, Perl does just that.
/dev/null and let the language holy wars begin!
Personally, I'd prefer to rely upon a language that delivers on the promise of "write once, run anywhere"
Flames to
Come over here and look at some of American society's poorest. I promise you, unless you starve yourself, it is impossible to starve in the United States now a days. As a matter of fact, it probably wouldn't hurt for about 60% of the population to lose some weight. As for healthcare, look at Medicard, Medicaid, etc. :) Just my two cents.
Also, on a similar note, if you have the slightest bit of flakiness with your hardware, Mandrake will die, and die badly. One of my friends was trying to set up IP Masq, and was using Mandrake. It was doing some sort of "ide optimization" crap that did only one thing - render the system unusable/unbootable. (hung during init cycle). Gave him a copy of RedHat 6.1, installed and ran like a charm.
Did you notice the little checkbox during the Mandrake install that enables hard drive optimisation and warns that it can cause problems??? Sounds like a case of RTFM to me.
Now smile like a doughnut... :O
It's people like you who want to censor the net. Who the hell gives you the right to say what is irrelevant? This isn't even your own damn website! Too bad some self-important sad sack feels that it's his duty to save us from April Fool's day. Sod off and die.
My friends, The action being taken by Andover.net is simply irresponsible and morally wrong. I will personally protest the action by setting myself on fire in front of the courthouse and running around screaming curses against the traitorous CmdrTaco. I may die, my body may be consumed by the hot flames, but my memory will live on in the hearts of all /.ers everywhere.
After living in Europe (especially the UK) for a few years I can tell you this: There is nothing we can do to prevent a determined individual or group from commiting an act of terrorism. Unfortunately, there is not a lot we can do except go after the supporters of the terrorists and hit them before they hit us. Also, we need to consider what we are paying our current airport security personnel. I believe it is Swissair that provides bonuses for security personnel that find contraband and when was the last time you heard of a Swissair jet being blown up or hijacked? No machine can fix the problem of poorly motivated people. My main problem with the deal is that in allowing ourselves to be searched so personally gives us a false sense of security. There will always be _bad_ people in the workd who will want to do us harm. Until the bad guys are dealt with, we will have no security. It always seems that whoever trades freedom for security usually ends up with neither.
I took the DeCSS stuff off of my site and replaced it with a link to OpenDVD.org, which has a much better tarball of _all_ the linux software they could scrounge up pertaining to DVDs. Hope it helps.
I bet a DOS box in a closet with a generator and a ups supplying it would rack up a very impressive uptime. Unfortunately the box running DOS would be about as useful to me as a box running *BSD would be. I use my computer as a workstation/development platform where hardware support is a priority. Now if I were to run a server, I'd probably use BSD or Solaris. Anyways, it's all pretty pointless because anyone with any experience in the field at all knows the relative strengths and weakness of each OS already.
Do you _actually_ enjoy urinating into the wind?
Offtopic: I've got the DeCSS stuff up on my site at http://www.rtmfd.net
:)
I must beg to differ with you on this one. Borland C++ 5.0 was a piece of crap. As a commercial software developer, I found it all but useless for creating even the most rudimentary of Win32 GUI apps. Yes, some of these compiler issues were fixed in later patches, but I had deadlines to meet. It was too little, too late for a $500 product.