Even assuming that this is done on a tape backup or something as stupid as that, this is pointless and useless because it would be almost impossible to search through all of this info without having it easily importable into a database where you could search through records or have a universal format tha all these log files could be output into, for easy import and read, etc.
Also considering that these records are kept 'indefinitely' the storage and money spent on this should be subsidized in some sense and al that subsidized money will be for nothing because this will only end up in maybe a handful of minor arrests for hacking and NOT in 'world trade center' avoiding events.
No but it has everything to do with speed and use of resources. A couple hundred system cals (including redundant ones) in IIS verses maybe 70 in Apache would correlate to Apache using fewer resources, booting faster ad having a faster response time.
Also as I pointed out, IIS has loads of redundant system calls making for a bloated system.
This is what the graphs show. Not security, bloat, poor performance and bad development.
active directories can crash if a script kiddie farts just right. This was found out when the infamous Captain Crunch demonstrated how to crash a Microsoft server using a whoopee cushion.
If there were a time for Linux to be made into a tool of destruction to wipe out all mankind, to kick puppies, make children cry, steal candy from babies and import illegal aliens into our country to pay them pennies to work overtime, this would be it's opportunity.
I know what you mean. I used to download Mozilla regularly back before Firefox and use it but it still had bugs. Like someone said up above, the latest version is EXTREMEKY stable but the issue is backwards compatability. Current Microsoft docs have issues being compatable with older docs and there is no way around it for even OO as this is an issue that Microsoft created and has refused to resolve. If in newer versions of OO you have problems with word docs, do the same thing you would in Microsoft Word; save the file in a newer file format like Office 2000. This usually resolves the issue.
The Blackberry age? Blackberry's came around a bit after the 80's
And there's your clue (hint: it has something to do with the current year and how stupid one looks for trolling for spelling)
The clock is ticking. Lets see how long it takes for our contestant to figure this one out. Odds are since he has yet to figure out the secret as to why people like open source, the chances he will figure out the current year seems HIGHLY unlikely... especially since he's on windows and it's time formats do not conform with standards.:)
Open source advocates really need a better rallying cry than this. (And better spelling - compatability?)
And proprietary yes men need a better rallying cry than 'buy it because everyone else does'. And knocking for spelling is so 1980's. Get with the Blackberry age and buy a clue.
I'd rather have a choice that's compatibile with most than no choice thats only compatible with one. You choose your slave master, I'll choose freedom.
LOL. Well when you work in any doc in 2007, you won't be able to work with ANYONE right now considering the adoption rate. I can't say I know of a single person who yet uses 2007... and I live in Seattle, right across from Redmond. I used to work for a vendor and even they aren't switching over. Microsoft themselves haven't switched over and have no plans to in the immediate future.:)
People who sit on the bleeding edge can't complain about incompatibility because they are merely a small percentage. However, should the source code be open, they can do something about that compatability and try to fix it themselves. Until then, they just have to wait until the entire world adopts the same standard as you or the parent company decides to get off it's multi-billion dollar ass and make a product thats backwards compatible.:)
Notice the aim is looking at business, not your anecdotal stories about your fictional grandmother (I dont know if she exists, nor do I care). I care about facts, and this story aims at business usage of OO vs MS Office.
If you don't like me disproving your divergance from the point, then don't diverge from the point.
When companies and schools and governments are all saying that they are planning on staying away in droves, I don't think that will be much of an issue for at least another year maybe three. Considering that Microsoft Office has an entirely new interface and will require retraining of 100% of its user base, I expect it will be a much longer adoption rate and that it really won't be that much of a concern for even longer than that. Maybe within the next 5 years it will become a concern but the near future isn't.
As I said in another post, often the same forms that I have problems with in OO are the same forms my co-workers have problems with in Microsoft Office and they have to request the user send in a newer format. Microsoft has backward compatibility issues and as a result, the same issues exist in OO when trying to read older Microsoft Office dopcuments. Thats why they read well once converted.
Not an issue with OO but an issue with the backwards compatability of the Microsoft formats being used.
Notice the aim is looking at business, not your anecdotal stories about your fictional grandmother (I dont know if she exists, nor do I care). I care about facts, and this story aims at business usage of OO vs MS Office.
Oh I'm sorry. You stated that it would take a developer to use this and then when I refute it, you say 'lets not get side tracked'. How sad. So in other words, if I prove you wrong, you'd rather I keep my mouth shut? Are you sure you are Steve Ballmer in disguise? How long HAVE you been on the Microsoft payroll?:)
If you are an office of CPA's that haven't standardized on an application then you probably should figure out how to run a business first. If you standardize on one application or the other, you will be fine and the end goal is the output, not the tiny little scripts you run inside.
As for me, I have yet to get a excel doc from a CPA or any other person where their little scripts won't run. So i don't know what you are talking about. But if you want to avoid this guessing that you keep doing, just go to the Open Office website and read the docs.
You need that experience huh? Well funny thing is, I installed Kubuntu (the KDE version of Ubuntu) with Open Office on my 65 year old moms machine. She never noticed the difference between Microsoft Word and Open Office Word. And guess how many phone calls I get to help her work on her novel? Zero. This is comparison to the weekly trouble shooting I did before.
I know that you are trying to troll but honestly you are giving me a great chance to show how easy Open Office is. It doesn't take a developer to install or know about it or maintain it... only an open mind who takes the time to try it out and see for themselves. That how Firefox happened. People tried it and it just worked. Same thing with Open Office. It just works.
80% of scripts run fine but some scripting doesn't run... This is a known issue. And as most people only use 10% of the features anyway, most people will never have a problem with this. Microsoft has admitted that 90% of people don't use more than 10% of the functionality within Office anyway. So literally, since Open Office isn't the dominant player, they don't have to reach for that last 10%. They just have to duplicate the vast majority of functions that people use every day... and they do.
Parent is very wrong. I'm one of a couple of devs in my office using Ubuntu as my desktop. I use Open Office and can open all docs that people send to me: Powerpoint, Excel, Word docs. They all work fine. Plus I can export as PDF's and a variety of other formats. The only time I have run into a problem is when people are saving in a very old format like Word97. But then, even Microsoft Office users have the same problem and do the same thing I do... ask the user to resend in a more recent format.
So what you are REALLY saying is 'while 9 out of 10 MAC users prefer homosexuals, this is a diametrically opposing comparison to the closeting homophobes that are Windows users who long to be stylish and cool and dance with wild abandon in the street but fear that such behaviour will cause them to BURN IN HELL FOR ALL ETERNITY!'. Hmmm... I think I have to go. The is a Windows user at more door wishing to hand me a pamphlet and tell me all about how Jesus Mormon Jehovah Gates came to save my soul from the damnation f open source.
When users who don't understand the thing they are using take out their frustration on you, it is a natural response to return said frustration back on the object that scorns you. This isn't a problem with IT but with IT education of end users. If end users understood what they used a bit better and become a bit less technophobic/xenophobic (and this will happen with time just as with any introduction of new technology), this too will go away.
There I have summed it up without a book and saved you all a trip to Barnes and Noble.
Who said I was talking about Java? The principles and practices and methodologies that PHP could be using are ones adopted by Python, Java, C++, Ruby, Perl and many others.
I agree. One of the developers gave me the excuse' it would be too hard for developers to understand' as the excuse for not using better programming methodologies. The developer would adapt and if it was too hard, how come other developers in other languages aren't having a problem picking it up. It's really discouraging since I'm developing an MVC framework for PHP and am beginning to hate the language because the developers in it can't grow up because the maintainers of the language don't want them to.
I used to work with the Zend team and they seem determined o pander to the least common denominator of hobbiests and not allow the language to grow up. Things like nested classes and strongly types variab;es which should have been implemented in the latest version are strongly fought against. They things as well as other would help enforce good coding standards. But I have been told by the Zend developers themselves that they like to leave it up to the developer to code badly and to me that makes the language just as much to blame. I think the industry has established by now what are good programming habits and methodologies and what aren't.
Slashdot Mirror
Even assuming that this is done on a tape backup or something as stupid as that, this is pointless and useless because it would be almost impossible to search through all of this info without having it easily importable into a database where you could search through records or have a universal format tha all these log files could be output into, for easy import and read, etc.
Also considering that these records are kept 'indefinitely' the storage and money spent on this should be subsidized in some sense and al that subsidized money will be for nothing because this will only end up in maybe a handful of minor arrests for hacking and NOT in 'world trade center' avoiding events.
No but it has everything to do with speed and use of resources. A couple hundred system cals (including redundant ones) in IIS verses maybe 70 in Apache would correlate to Apache using fewer resources, booting faster ad having a faster response time.
Also as I pointed out, IIS has loads of redundant system calls making for a bloated system.
This is what the graphs show. Not security, bloat, poor performance and bad development.
LOL. Mod parent the hell up! Yeah!!!
active directories can crash if a script kiddie farts just right. This was found out when the infamous Captain Crunch demonstrated how to crash a Microsoft server using a whoopee cushion.
If there were a time for Linux to be made into a tool of destruction to wipe out all mankind, to kick puppies, make children cry, steal candy from babies and import illegal aliens into our country to pay them pennies to work overtime, this would be it's opportunity.
BUY one! Sponsored by the '$10 in your pocket to say Zune is great' campaign.
I know what you mean. I used to download Mozilla regularly back before Firefox and use it but it still had bugs. Like someone said up above, the latest version is EXTREMEKY stable but the issue is backwards compatability. Current Microsoft docs have issues being compatable with older docs and there is no way around it for even OO as this is an issue that Microsoft created and has refused to resolve. If in newer versions of OO you have problems with word docs, do the same thing you would in Microsoft Word; save the file in a newer file format like Office 2000. This usually resolves the issue.
The clock is ticking. Lets see how long it takes for our contestant to figure this one out. Odds are since he has yet to figure out the secret as to why people like open source, the chances he will figure out the current year seems HIGHLY unlikely... especially since he's on windows and it's time formats do not conform with standards.:)
I'd rather have a choice that's compatibile with most than no choice thats only compatible with one. You choose your slave master, I'll choose freedom.
They built one just for her, smartass. ;)
LOL. Well when you work in any doc in 2007, you won't be able to work with ANYONE right now considering the adoption rate. I can't say I know of a single person who yet uses 2007... and I live in Seattle, right across from Redmond. I used to work for a vendor and even they aren't switching over. Microsoft themselves haven't switched over and have no plans to in the immediate future. :)
:)
People who sit on the bleeding edge can't complain about incompatibility because they are merely a small percentage. However, should the source code be open, they can do something about that compatability and try to fix it themselves. Until then, they just have to wait until the entire world adopts the same standard as you or the parent company decides to get off it's multi-billion dollar ass and make a product thats backwards compatible.
When companies and schools and governments are all saying that they are planning on staying away in droves, I don't think that will be much of an issue for at least another year maybe three. Considering that Microsoft Office has an entirely new interface and will require retraining of 100% of its user base, I expect it will be a much longer adoption rate and that it really won't be that much of a concern for even longer than that. Maybe within the next 5 years it will become a concern but the near future isn't.
As I said in another post, often the same forms that I have problems with in OO are the same forms my co-workers have problems with in Microsoft Office and they have to request the user send in a newer format. Microsoft has backward compatibility issues and as a result, the same issues exist in OO when trying to read older Microsoft Office dopcuments. Thats why they read well once converted. Not an issue with OO but an issue with the backwards compatability of the Microsoft formats being used.
If you are an office of CPA's that haven't standardized on an application then you probably should figure out how to run a business first. If you standardize on one application or the other, you will be fine and the end goal is the output, not the tiny little scripts you run inside.
As for me, I have yet to get a excel doc from a CPA or any other person where their little scripts won't run. So i don't know what you are talking about. But if you want to avoid this guessing that you keep doing, just go to the Open Office website and read the docs.
You need that experience huh? Well funny thing is, I installed Kubuntu (the KDE version of Ubuntu) with Open Office on my 65 year old moms machine. She never noticed the difference between Microsoft Word and Open Office Word. And guess how many phone calls I get to help her work on her novel? Zero. This is comparison to the weekly trouble shooting I did before.
I know that you are trying to troll but honestly you are giving me a great chance to show how easy Open Office is. It doesn't take a developer to install or know about it or maintain it... only an open mind who takes the time to try it out and see for themselves. That how Firefox happened. People tried it and it just worked. Same thing with Open Office. It just works.
Maybe thats why Microsoft is so panicky.
80% of scripts run fine but some scripting doesn't run... This is a known issue. And as most people only use 10% of the features anyway, most people will never have a problem with this. Microsoft has admitted that 90% of people don't use more than 10% of the functionality within Office anyway. So literally, since Open Office isn't the dominant player, they don't have to reach for that last 10%. They just have to duplicate the vast majority of functions that people use every day... and they do.
Parent is very wrong. I'm one of a couple of devs in my office using Ubuntu as my desktop. I use Open Office and can open all docs that people send to me: Powerpoint, Excel, Word docs. They all work fine. Plus I can export as PDF's and a variety of other formats. The only time I have run into a problem is when people are saving in a very old format like Word97. But then, even Microsoft Office users have the same problem and do the same thing I do... ask the user to resend in a more recent format.
So what you are REALLY saying is 'while 9 out of 10 MAC users prefer homosexuals, this is a diametrically opposing comparison to the closeting homophobes that are Windows users who long to be stylish and cool and dance with wild abandon in the street but fear that such behaviour will cause them to BURN IN HELL FOR ALL ETERNITY!'. Hmmm... I think I have to go. The is a Windows user at more door wishing to hand me a pamphlet and tell me all about how Jesus Mormon Jehovah Gates came to save my soul from the damnation f open source.
Doesn't mean that it's better than being healthy...
When users who don't understand the thing they are using take out their frustration on you, it is a natural response to return said frustration back on the object that scorns you. This isn't a problem with IT but with IT education of end users. If end users understood what they used a bit better and become a bit less technophobic/xenophobic (and this will happen with time just as with any introduction of new technology), this too will go away. There I have summed it up without a book and saved you all a trip to Barnes and Noble.
Who said I was talking about Java? The principles and practices and methodologies that PHP could be using are ones adopted by Python, Java, C++, Ruby, Perl and many others.
I agree. One of the developers gave me the excuse' it would be too hard for developers to understand' as the excuse for not using better programming methodologies. The developer would adapt and if it was too hard, how come other developers in other languages aren't having a problem picking it up. It's really discouraging since I'm developing an MVC framework for PHP and am beginning to hate the language because the developers in it can't grow up because the maintainers of the language don't want them to.
I used to work with the Zend team and they seem determined o pander to the least common denominator of hobbiests and not allow the language to grow up. Things like nested classes and strongly types variab;es which should have been implemented in the latest version are strongly fought against. They things as well as other would help enforce good coding standards. But I have been told by the Zend developers themselves that they like to leave it up to the developer to code badly and to me that makes the language just as much to blame. I think the industry has established by now what are good programming habits and methodologies and what aren't.