All OEM's manufacture their own. Got a Dell right in front of me with a Dell keyboard and a Dell mouse. No MS trademark anywhere on either of them. Again... not a big seller.
Java, Perl, Python applications and are not software?? News to IBM, Sun and all the others who do call them software. You seem to be the only retard in the room to disagree with them.
Oh hell no... I say let him stay. A few more decisions like Vista, Zune and the DRM and Microsoft just becomes another Novell; the only two things they make that people really HAVE to have are Xbox and Exchange. Even Office is becoming optional now.
If you want to make money you work in Windows?? LOL! Hate to tell you this pal but I've been a web developer since I was at Amazon in 95 and I have never once stepped foot onto a Microsoft platform. And I have 3-4 times the output and twice the pay.:)
Actually, I've been part of two Ziwbra installs at companies now and both were due to constant problews with Exchange. After switching to Zimbra, all users (mac, Linux and Windows) were able to interoperate smoothly and since the server was on Linux, we had no downtime. The stability in Zimbra and cross platform capabilities puts the original product to shame.
You assume that Ruby is ACTUALLY threaded when it is NOT. It FAKES threading and is supposed to be adding REAL threading in the NEXT version (or so they say). So you just proved my point.
ooohh semantics is what you have to argue on? fine. I have + 5, Insightful and you are still an anonymous coward... happy now? Ruby still isn't going to scale, semantic boy.:)
Processes throw errors, scripts catch errors and things that are questionable. Don't you have a log file for going through your log files? Don't you have a set of scripts already in place for maintaining this and grabbing most of the questionable stuff for analyzing and putting into a separate log so that you can create better script for better analysis? How long did you say you have been doing this job? Sheesh.
Well you seem to think Rails was written in Portuguese and not Ruby then and that somehow something other than the language it was written in is causing this mysterious scaling issue that people have been 'making up' for years about poor old Ruby. It must be a myth or else you would be wrong wouldn't you and thousands of other developers in Python and Java and C and PHP and companies that have adopted Ruby and then dumped it would all be so very right. What a horrible thing that would be.
If I built a house out of cheese with a hammer made from cheese and the house began to crumble, would you say it's because of the hammer made from cheese or because cheese isn't a stable building material? Because right now you are saying it's the cheesey hammer and you're sounding like an idiot.
Ruby os not the same thing as Rails? I'm sorry but what the hell do you think Rails is programmed in??? C #? PHP? No, it's programmed in RUBY as well... So if Ruby with Rails (Ruby) does not scale, I doubt another framework is going to do any better. It's funny though that other languages like Java and PHP have frameworks programmed in their native languages that scale just fine and Ruby doesn't... and yet Ruby developers STILL insist that Ruby scales perfectly well.
They don't know whether RUBY can or can't scale and threw it in just because they have dedicated so many resources and now have to evaluate it without the framework coded in RUBY... which seems odd as other languages which have frameworks coded in their native language seem to scale just fine. Hmmm.... 2+2, genius. Again... I'll give you some time to process. RUBY developers still haven't processed this and it seems they are in an infinite loop of denial.
They are debating on whether the language can scale. That's why they are thinking of using JAVA or PHP instead. If they thought the language could scale on it's own and they already had fully trained staff of RUBY developers, it wouldn't be a debate now would it? Think about it genius... I'll give you some time since you are a RUBY dev and it takes you twice as long to process.
And for all those Ruby people in denial to the fact that people have been saying this for years, here is your proof yet again. Of course I will be marked down as being a troll for pointing this out by the RUBY comunity but it is time that they acknowledge the inherent achilles heel of the language.
A non-admin looking at your logs? Great!! And that's beneficial HOW? So that they can spot only the thing you asked them to spot? A sys admin can also trouble shoot while looking through a log and spot additional problems. A non-admin will not. Boy, you are talking yourself further into that hole. This tool is looking more and more dumb all the time.
No I generally use grep. But yes a tool is useful when I have to do alot of tasks at once. My point is if you don't know the basics then, you are useless without your button. I cant ask you to manually config, grep a log or add a shell script to the crontab if you depend on GUI's. And I have (and still am in the process of) run across too many Windows sys admins who freak out when they have to do ANYTHING that does not have a GUI. They need to learn the basics and take the training wheels off before adding more tasks to make them dumber than before.
It's responding to people who want buttons. People who learned how to sys admin via buttons and don't know how to actually administer a system without a button. People who don't know how to build themselves a cert without a button. People who don't know how to check their logs without a button. People who should never have been hired as system administrators in the first place.
Well if PHP had a decent way to do prepared statements like JAVA, I'd say 'hallelujah brother'. But they don't... and the current methodology allows for the same error of byte code strings to be entered. Which is why you have to use mysql_real_escape_string to avoid byte code strings being used for sql injection.
JAVA on the other hand is far more prepared (no pun intended) for this.
PHP developers? Ha! The vast majority of them would ruin us all. It's just that having worked in heterogenous shops and monogomous shops (always all Microsoft), Linux people understand protocols and multiple platforms and undecstand what they are doing and the underlying mechanics far better than their Microsoft counterparts; Linux people can learn Microsoft technologies but Microsoft people freezeup, freakout and panic when they have to work with an open protocol or something not handled for them by Microsoft.
Simple answer. mysql_real_escape_string. Instead of sanitizing data through the language which will miss byte encoded strings, alot of applications have switched to using MySQLs native mysql_real_escape_string which will catch these. Java sanitizes byte code strings as well I believe.
So it may be partially C# or just that Microsoft web devs are inherently 'dumber'.
Slashdot Mirror
All OEM's manufacture their own. Got a Dell right in front of me with a Dell keyboard and a Dell mouse. No MS trademark anywhere on either of them. Again... not a big seller.
Java, Perl, Python applications and are not software?? News to IBM, Sun and all the others who do call them software. You seem to be the only retard in the room to disagree with them.
Get real! 90% of users use the mouse and keyboard that shipped with their computer. And everyone ships optical mice these days.
Oh hell no... I say let him stay. A few more decisions like Vista, Zune and the DRM and Microsoft just becomes another Novell; the only two things they make that people really HAVE to have are Xbox and Exchange. Even Office is becoming optional now.
If you want to make money you work in Windows?? LOL! Hate to tell you this pal but I've been a web developer since I was at Amazon in 95 and I have never once stepped foot onto a Microsoft platform. And I have 3-4 times the output and twice the pay. :)
Actually, I've been part of two Ziwbra installs at companies now and both were due to constant problews with Exchange. After switching to Zimbra, all users (mac, Linux and Windows) were able to interoperate smoothly and since the server was on Linux, we had no downtime. The stability in Zimbra and cross platform capabilities puts the original product to shame.
You assume that Ruby is ACTUALLY threaded when it is NOT. It FAKES threading and is supposed to be adding REAL threading in the NEXT version (or so they say). So you just proved my point.
Truth always comes as a bitter surprise to those who cannot handle it. Ask your mom for a hug.
So we finally agree... that Ruby is the cheese and therefore it can't scale. Now shutup and eat the cheese.
ooohh semantics is what you have to argue on? fine. I have + 5, Insightful and you are still an anonymous coward... happy now? Ruby still isn't going to scale, semantic boy. :)
Processes throw errors, scripts catch errors and things that are questionable. Don't you have a log file for going through your log files? Don't you have a set of scripts already in place for maintaining this and grabbing most of the questionable stuff for analyzing and putting into a separate log so that you can create better script for better analysis? How long did you say you have been doing this job? Sheesh.
I have 5 insightful mod points that say I more logical than you so nyah! :)
If I built a house out of cheese with a hammer made from cheese and the house began to crumble, would you say it's because of the hammer made from cheese or because cheese isn't a stable building material? Because right now you are saying it's the cheesey hammer and you're sounding like an idiot.
Ruby os not the same thing as Rails? I'm sorry but what the hell do you think Rails is programmed in??? C #? PHP? No, it's programmed in RUBY as well... So if Ruby with Rails (Ruby) does not scale, I doubt another framework is going to do any better. It's funny though that other languages like Java and PHP have frameworks programmed in their native languages that scale just fine and Ruby doesn't ... and yet Ruby developers STILL insist that Ruby scales perfectly well.
They don't know whether RUBY can or can't scale and threw it in just because they have dedicated so many resources and now have to evaluate it without the framework coded in RUBY... which seems odd as other languages which have frameworks coded in their native language seem to scale just fine. Hmmm.... 2+2, genius. Again... I'll give you some time to process. RUBY developers still haven't processed this and it seems they are in an infinite loop of denial.
They are debating on whether the language can scale. That's why they are thinking of using JAVA or PHP instead. If they thought the language could scale on it's own and they already had fully trained staff of RUBY developers, it wouldn't be a debate now would it? Think about it genius... I'll give you some time since you are a RUBY dev and it takes you twice as long to process.
And for all those Ruby people in denial to the fact that people have been saying this for years, here is your proof yet again. Of course I will be marked down as being a troll for pointing this out by the RUBY comunity but it is time that they acknowledge the inherent achilles heel of the language.
A non-admin looking at your logs? Great!! And that's beneficial HOW? So that they can spot only the thing you asked them to spot? A sys admin can also trouble shoot while looking through a log and spot additional problems. A non-admin will not. Boy, you are talking yourself further into that hole. This tool is looking more and more dumb all the time.
No I generally use grep. But yes a tool is useful when I have to do alot of tasks at once. My point is if you don't know the basics then, you are useless without your button. I cant ask you to manually config, grep a log or add a shell script to the crontab if you depend on GUI's. And I have (and still am in the process of) run across too many Windows sys admins who freak out when they have to do ANYTHING that does not have a GUI. They need to learn the basics and take the training wheels off before adding more tasks to make them dumber than before.
a button to check your logs...
It's responding to people who want buttons. People who learned how to sys admin via buttons and don't know how to actually administer a system without a button. People who don't know how to build themselves a cert without a button. People who don't know how to check their logs without a button. People who should never have been hired as system administrators in the first place.
You're the exception that proves the rule.
Well if PHP had a decent way to do prepared statements like JAVA, I'd say 'hallelujah brother'. But they don't... and the current methodology allows for the same error of byte code strings to be entered. Which is why you have to use mysql_real_escape_string to avoid byte code strings being used for sql injection.
JAVA on the other hand is far more prepared (no pun intended) for this.
PHP developers? Ha! The vast majority of them would ruin us all. It's just that having worked in heterogenous shops and monogomous shops (always all Microsoft), Linux people understand protocols and multiple platforms and undecstand what they are doing and the underlying mechanics far better than their Microsoft counterparts; Linux people can learn Microsoft technologies but Microsoft people freezeup, freakout and panic when they have to work with an open protocol or something not handled for them by Microsoft.
So it may be partially C# or just that Microsoft web devs are inherently 'dumber'.