Its actually a pretty fair little tool if you're working with.Not. I've used it a bit, although I generally prefer to use gvim, Dreamweaver or HTML-Kit when on windows. I think that if I used more ASP though, I would use it more seriously.
On a related note, though, it has one of the best online helps/docs for the.Net class hierarchy:)
Personally I don't think commenting about inappropriate modding and abusive and juvenile comments is offtopic in a discussion. You are not the one derailing the discussion, but someone attempting to correct some half-witted moron's hijack attempts.
I agree with you. The parent's poster had compiled and presented information pertinent to the OP's request. Unlike the twats who were belittling him.
What he had in his sig is his business. It is not as if he was hiding porn or anything else offensive behind a misleading link. The URL made it pretty damned obvious what was behind the link. If people clicked through and were upset then they are bloody idiots. They deliberately jumped in front of the truck so that they could sue the driver!
Whether or not you agree with the sig's sentiments, they are honestly presented and their viewing is optional. That is far more honourable than his detractors seem capable of.
Unfortunately, it is this kind of twattish behaviour that has had me neglect/. for the last few months. I have been an avid reader, almost daily, almost from the start. Frankly, because of this kind of behaviour it is becomming more "News for Turds" than "News for Nerds" and this is sad. It used to be a good, respectful and enjoyable community. Some people just need to grow up and get a life, preferably of their own!
Certainly, from the primary posting, I would agree that cross platform was very important in this case. Maybe additional information would help us be more specific.
" You should just never ignore the other side, there may be a lot to learn"
Well put!
Its a shame that these discussions get domminated by narrow viewed people with hobby-horses to promote:(
Personally I prefer the.Net platform to the Java platform, but I think that that is because of the kitchen sink mentality of the JCPs. As you mentioned, they are not always efficient.
In practice, however, I'll usually use the Java platform, despite my misgivings about it, since it allows me to use it on other operating systems that may be better suited to the job at hand.
One thing that people often forget when talking about portability is skills portability. A language that can be used on multiple platforms is a more valuable skill to the individual; it gives them more work opportunities:)
If you bothered to read my post, you would see that I was differentiating between the language (C#) and the platform (.Net). I also tried to point out that although the same linkage between language and platform existed with Java, the java 'platform' is virtualised and runs on many physical platforms.
C# is a good language. In fact I think both it and.Net are superior to Java in many ways, except portability of the combined platform is an issue, especially when people are too blind to differentiate between the language and the platform.
If C# standardisation is purely a marketing ploy, how come so many 'big-guns' of the Open Source movement have adopted it and have been involved in porting to unix/linux?
C# is an open standard. Java is not. Fact. Period!
Anyone can produce a C# compiler and call it C#. That cannot be said of Java. C# is a viable development language on many non-microsoft platforms and can be used with many native libraries. (gtk, for one) Tell me how that is not open?.Net is not open. Even Mono doesn't completely implement.Net..Net really only runs on M$ platforms. (although it does really well and it is a shame it isn't cross platform - M$ can do things well, sometimes:) )
So, C# +.Net is not an open platform. Most definately (and sadly) not. But C#+.Net is distinct from C#.
You're making a very big assumption that Microsoft will be the only platform that will be required.
If you take that away then a number of you C# pluspoints become irrelevant.
While I agree with you about C# being more open than Java (and I prefer it as a language) most people are thick and don't differentiate languages from associated APIs nowadays. With that thought in mind, how many people really mean "C# and.Net" when they say C#? While you may argue that this is similar to "Java" meaning "Java + Foundation Classes/Swing", the difference is that the Java APIs are cross platform while.Net is, in reality (despite mono) really only a Windows platform.
Personally, i think that there is much to commend C# as a language, but I think you'll find that those pushing for C# are really pushing the.Net framework rather than the language. While I think it is one of the best things that Microsoft have come up with, it is not portable and unless you wish to have code that runs purely on Windows, Java is the way to go.
The advantage of Java is that it has a standard API that is tailored to multiple platforms.
Seriously, though, the only thing you can do is to try and eat healthily and find time a couple of times a week for the gym. If you can get to cycle to/from work some of the time, it is a big help
Cut carrots into 'sticks'. about 1/3 inch by 3 inches.
Place on a sheet of foil and add a splash of oil (virgin sunflower, if you can get it, or light olive oil) and some honey. Finally, close the sheet of foil making a sealed envelope. It helps to turn the edges up to avoid any liquid escaping.
Put the envelope in the oven with whatever else is roasting. Time taken to cook will depend on how hot the oven is and how firm the carrots. I usually find 30-40 minutes is required.
The carrots can also be opened towards the end of cooking to brown if preferred.
This makes for the most amazingly sweet carrots and, unlike boiling, you don't lose a ton of nutrients in the water (they just get mangled by the heating:) )
Their adoption gives everyone a chance to get the service level they require. Free software can be written in the knowledge that it will interact with commercial software. Commercial software can be written to give the slick finish and support that the corporate or nervous user craves.
If an organisation as large as the collective EU were to take the open standard/OSS route, all compainies like Microsoft could do was jump on the bandwagon to compete on a more equal playing field.
It looks like they are taking a sensible migration path.
Adopting a new product (OOo) as the new standard, training people to use it and then insisting it be used for new work is the way to go.
Since they already have licensed copies of Office97, there is no cost involved in keeping it alongside to run legacy apps and handle legacy documentation.
Sending documents for other people to view can always be done by creating PDFs of them. This is the main way we do it and find that most people can read them regardless of platform. I can even read them on my telephone:)
The next step on migration would be to divert some of the cash that would have been spent on the upgrade to porting the legacy apps to use OOo. Even if this took the whole upgrade budget, in the medium to long run they will still benefit greatly.
Where there are people who cannot cope with PDF, or a PDF isn't adequate (i.e. they need an active spreadsheet) then encourage people to get OOo. The price is right:)
In the case of suppliers, then you tell them they have to use it. I doubt there will be any contractual issues regarding this - I've yet to see a contract that said 'all invoice to be submitted in Word97' or somesuch:) If they want your money, this is a minimal cost (and ultimately a saving) for them.
For other people, there can be problems, but even then how different are they to upgrading to a new version of Office? I remember incompatabilities between versions and having to save documents as Word 2.0 format, etc. OOo does produce passably decent Office code that is probably no waorse than those cases.
OOo is freely distributable. CD-Rs are cheap. Burn a few copies to give to these people. If you have an organisation of a few thousand (as many govt organs will), then you will have a tech support department. Give a few of these valued people access to your tech support for OOo issues. It won't cost anything extra in most cases.
While I write software commercially for a living, I also find advantage in OpenSource. Companies like Microsoft have, either by design or accident, gained a strong monopoly and thus have a stranglehold over us. For a piece of software that has become a 'standard', its cost is just too high for most people to afford. How many pirate copies because of this? How many feel justified in doing so? How many would agree with them?
Whatever the 'rights' or 'wrongs' of the situation, no commercial product should be in such a monopoly position (unless its mine and I get all the dosh, of course:) ) and it is good to see Microsoft Office alternatives given a chance.
Maybe it would be a good idea to at least have some knowledge of the subject you're berating someone for BEFORE opening your mouth. You're less likely to get egg splattered.
The original poster did the right thing in asking first. I used to do data recovery and there are times when a media has a very limited physical life left. While less common than with old floppies, even modern magnetic media can suffer from the magnetic material seperating from the disk. If this is the reason for failure then blindly doing something in the hope that it may work could seriously reduce the chances you have for recovery later.
Perhaps you are aware of how much an ass you are by posting as an AC?
I also am in security, as well as more general development and I never said they weren't dangerous, nor said they were less dangerous than Perl.
I doubt anyone would say playing Russian roulette wasn't dangerous, yet using a fully loaded gun is definately more dangerous.
The danger in Perl lies in the fact that its lack of strong typing and somewhat promiscuous behaviour when autoloading is used can lead to serious problems when not carefully audited or managed. There are also other possible problems and Perl is not really suited for writing large systems in, although many people do insist on doing so.
Remember, 'dangerous' doesn't only mean security. Up until a few years ago, for most computer systems it meant damaging data, giving wrong results or just plain blowing up. This definition hasn't changed, despite people now more commonly using it to mean internet security.
Personally I have a love/hate relationship with Perl.
The purist Computer Scientist in me loathes it. It is ugly, dangerous and has a weird botched together syntax.
Just as I self rightously convince myself of these self evident facts, some real cool trick saves the day and the wild inner hacker in me starts telling the CS part to stop being such a bore:)
Perl is a great language, though like all powerful tools it can be dangerous if misused. It is sometimes ugly, and just as often beautiful.
All that said, given the general trend within/. these days, I do suspect that most denigrators do so because they cannot handle all the squiggles:) God help them if they ever encountered APL:D
My guess is that by the time it reaches my side of the pond, the '$' will have changed to '£', so I'd guess we'll still be spluttering too much with horror to give you too much sympathy:D
I agree with much of what you say, but must say that for the most part these design decisions are dictated by power levels. Even non-volatile ram will take more power though little, admitedly. 802.11 really is a no-no. Unlike the Palm based PDAs, a phone has constant variable power drains while it natters away with its network. That already causes a not inconsiderable drain. Adding WiFi will slup juice away so fast that the device would end up a useless expensive brick far more regularly than is useful.
The same for a camera flash. They kill even dedicated cameras. What would be of more practical use would be better light sensitivity and balance control. 640x480 is more than adequate for quick snaps if the quality is improved. You wouldn't have to torture me to accept better resolution, though:)
My company specialises in WiFi and Bluetooth connectivity products via telephones and this has taught me a lot about the two. That class 2 BT is used isn't such a bad thing. in fact, in many cases the low power/range class2 is better than class 1 because it reduces interference - this is seriously valuable where gazillions of sad buggers congregate with their phones - being one of those sad sods has taught me why low power is sometimes good!
Slashdot Mirror
Its actually a pretty fair little tool if you're working with .Not. I've used it a bit, although I generally prefer to use gvim, Dreamweaver or HTML-Kit when on windows. I think that if I used more ASP though, I would use it more seriously.
.Net class hierarchy :)
On a related note, though, it has one of the best online helps/docs for the
Personally I don't think commenting about inappropriate modding and abusive and juvenile comments is offtopic in a discussion. You are not the one derailing the discussion, but someone attempting to correct some half-witted moron's hijack attempts.
/. for the last few months. I have been an avid reader, almost daily, almost from the start. Frankly, because of this kind of behaviour it is becomming more "News for Turds" than "News for Nerds" and this is sad. It used to be a good, respectful and enjoyable community. Some people just need to grow up and get a life, preferably of their own!
I agree with you. The parent's poster had compiled and presented information pertinent to the OP's request. Unlike the twats who were belittling him.
What he had in his sig is his business. It is not as if he was hiding porn or anything else offensive behind a misleading link. The URL made it pretty damned obvious what was behind the link. If people clicked through and were upset then they are bloody idiots. They deliberately jumped in front of the truck so that they could sue the driver!
Whether or not you agree with the sig's sentiments, they are honestly presented and their viewing is optional. That is far more honourable than his detractors seem capable of.
Unfortunately, it is this kind of twattish behaviour that has had me neglect
That is far too scary a thought to del with at this time of night :)
Its hardly lame shooting trolls who hide behind an AC.
:)
Especially those who can't read
As you've noted, balance is everything :))
Certainly, from the primary posting, I would agree that cross platform was very important in this case. Maybe additional information would help us be more specific.
" You should just never ignore the other side, there may be a lot to learn"
:(
.Net platform to the Java platform, but I think that that is because of the kitchen sink mentality of the JCPs. As you mentioned, they are not always efficient.
:)
Well put!
Its a shame that these discussions get domminated by narrow viewed people with hobby-horses to promote
Personally I prefer the
In practice, however, I'll usually use the Java platform, despite my misgivings about it, since it allows me to use it on other operating systems that may be better suited to the job at hand.
One thing that people often forget when talking about portability is skills portability. A language that can be used on multiple platforms is a more valuable skill to the individual; it gives them more work opportunities
If you bothered to read my post, you would see that I was differentiating between the language (C#) and the platform (.Net). I also tried to point out that although the same linkage between language and platform existed with Java, the java 'platform' is virtualised and runs on many physical platforms.
.Net are superior to Java in many ways, except portability of the combined platform is an issue, especially when people are too blind to differentiate between the language and the platform.
.Net is not open. Even Mono doesn't completely implement .Net. .Net really only runs on M$ platforms. (although it does really well and it is a shame it isn't cross platform - M$ can do things well, sometimes :) )
.Net is not an open platform. Most definately (and sadly) not. But C#+.Net is distinct from C#.
C# is a good language. In fact I think both it and
If C# standardisation is purely a marketing ploy, how come so many 'big-guns' of the Open Source movement have adopted it and have been involved in porting to unix/linux?
C# is an open standard. Java is not. Fact. Period!
Anyone can produce a C# compiler and call it C#. That cannot be said of Java. C# is a viable development language on many non-microsoft platforms and can be used with many native libraries. (gtk, for one) Tell me how that is not open?
So, C# +
Am I, indeed? I can fully understand why you would post as an AC. The shame of not being able to handle language properly must be overwhelming
You're making a very big assumption that Microsoft will be the only platform that will be required.
.Net" when they say C#? While you may argue that this is similar to "Java" meaning "Java + Foundation Classes/Swing", the difference is that the Java APIs are cross platform while .Net is, in reality (despite mono) really only a Windows platform.
If you take that away then a number of you C# pluspoints become irrelevant.
While I agree with you about C# being more open than Java (and I prefer it as a language) most people are thick and don't differentiate languages from associated APIs nowadays. With that thought in mind, how many people really mean "C# and
Personally, i think that there is much to commend C# as a language, but I think you'll find that those pushing for C# are really pushing the .Net framework rather than the language. While I think it is one of the best things that Microsoft have come up with, it is not portable and unless you wish to have code that runs purely on Windows, Java is the way to go.
The advantage of Java is that it has a standard API that is tailored to multiple platforms.
.. in chocolate, pizza and cola :)
Seriously, though, the only thing you can do is to try and eat healthily and find time a couple of times a week for the gym. If you can get to cycle to/from work some of the time, it is a big help
I find roasting them has very good results.
:) )
Cut carrots into 'sticks'. about 1/3 inch by 3 inches.
Place on a sheet of foil and add a splash of oil (virgin sunflower, if you can get it, or light olive oil) and some honey. Finally, close the sheet of foil making a sealed envelope. It helps to turn the edges up to avoid any liquid escaping.
Put the envelope in the oven with whatever else is roasting. Time taken to cook will depend on how hot the oven is and how firm the carrots. I usually find 30-40 minutes is required.
The carrots can also be opened towards the end of cooking to brown if preferred.
This makes for the most amazingly sweet carrots and, unlike boiling, you don't lose a ton of nutrients in the water (they just get mangled by the heating
If she already has a PDA, or can get one, then the best way would be to send data via SD media.
As for powering the PDA, there are a number of options using solar power
Last time I looked, Auschwitz was in Poland, so that kind of makes that comment pointless.
but, just maybe, it has gotten in the way of generating even more income ;)
Am I the only one that thinks this ought to be painted pink? With either 'FAB1' as the number plate, or a pink moggy in the back? :)
Open Standards are well worth encouraging.
Their adoption gives everyone a chance to get the service level they require. Free software can be written in the knowledge that it will interact with commercial software. Commercial software can be written to give the slick finish and support that the corporate or nervous user craves.
If an organisation as large as the collective EU were to take the open standard/OSS route, all compainies like Microsoft could do was jump on the bandwagon to compete on a more equal playing field.
It looks like they are taking a sensible migration path.
:)
:)
:) ) and it is good to see Microsoft Office alternatives given a chance.
Adopting a new product (OOo) as the new standard, training people to use it and then insisting it be used for new work is the way to go.
Since they already have licensed copies of Office97, there is no cost involved in keeping it alongside to run legacy apps and handle legacy documentation.
Sending documents for other people to view can always be done by creating PDFs of them. This is the main way we do it and find that most people can read them regardless of platform. I can even read them on my telephone
The next step on migration would be to divert some of the cash that would have been spent on the upgrade to porting the legacy apps to use OOo. Even if this took the whole upgrade budget, in the medium to long run they will still benefit greatly.
Where there are people who cannot cope with PDF, or a PDF isn't adequate (i.e. they need an active spreadsheet) then encourage people to get OOo. The price is right
In the case of suppliers, then you tell them they have to use it. I doubt there will be any contractual issues regarding this - I've yet to see a contract that said 'all invoice to be submitted in Word97' or somesuch:) If they want your money, this is a minimal cost (and ultimately a saving) for them.
For other people, there can be problems, but even then how different are they to upgrading to a new version of Office? I remember incompatabilities between versions and having to save documents as Word 2.0 format, etc. OOo does produce passably decent Office code that is probably no waorse than those cases.
OOo is freely distributable. CD-Rs are cheap. Burn a few copies to give to these people. If you have an organisation of a few thousand (as many govt organs will), then you will have a tech support department. Give a few of these valued people access to your tech support for OOo issues. It won't cost anything extra in most cases.
While I write software commercially for a living, I also find advantage in OpenSource. Companies like Microsoft have, either by design or accident, gained a strong monopoly and thus have a stranglehold over us. For a piece of software that has become a 'standard', its cost is just too high for most people to afford. How many pirate copies because of this? How many feel justified in doing so? How many would agree with them?
Whatever the 'rights' or 'wrongs' of the situation, no commercial product should be in such a monopoly position (unless its mine and I get all the dosh, of course
Well, what nice, well informed piece of sarcasm.
Maybe it would be a good idea to at least have some knowledge of the subject you're berating someone for BEFORE opening your mouth. You're less likely to get egg splattered.
The original poster did the right thing in asking first. I used to do data recovery and there are times when a media has a very limited physical life left. While less common than with old floppies, even modern magnetic media can suffer from the magnetic material seperating from the disk. If this is the reason for failure then blindly doing something in the hope that it may work could seriously reduce the chances you have for recovery later.
Perhaps you are aware of how much an ass you are by posting as an AC?
I also am in security, as well as more general development and I never said they weren't dangerous, nor said they were less dangerous than Perl.
I doubt anyone would say playing Russian roulette wasn't dangerous, yet using a fully loaded gun is definately more dangerous.
The danger in Perl lies in the fact that its lack of strong typing and somewhat promiscuous behaviour when autoloading is used can lead to serious problems when not carefully audited or managed. There are also other possible problems and Perl is not really suited for writing large systems in, although many people do insist on doing so.
Remember, 'dangerous' doesn't only mean security. Up until a few years ago, for most computer systems it meant damaging data, giving wrong results or just plain blowing up. This definition hasn't changed, despite people now more commonly using it to mean internet security.
Nice quote and so true.
Personally I have a love/hate relationship with Perl.
:)
/. these days, I do suspect that most denigrators do so because they cannot handle all the squiggles :) God help them if they ever encountered APL :D
The purist Computer Scientist in me loathes it. It is ugly, dangerous and has a weird botched together syntax.
Just as I self rightously convince myself of these self evident facts, some real cool trick saves the day and the wild inner hacker in me starts telling the CS part to stop being such a bore
Perl is a great language, though like all powerful tools it can be dangerous if misused. It is sometimes ugly, and just as often beautiful.
All that said, given the general trend within
Yet, somehow, you feel the need to post as a Coward
This is supposed to be "News for Nerds"! /. started off for a technically minded userbase.
:)
These acronyms are common enough that real nerds really ought to know what they mean.
The editors really don't need to dumb things down for people who aren't the target audience
My guess is that by the time it reaches my side of the pond, the '$' will have changed to '£', so I'd guess we'll still be spluttering too much with horror to give you too much sympathy :D
:)
I agree with much of what you say, but must say that for the most part these design decisions are dictated by power levels. Even non-volatile ram will take more power though little, admitedly. 802.11 really is a no-no. Unlike the Palm based PDAs, a phone has constant variable power drains while it natters away with its network. That already causes a not inconsiderable drain. Adding WiFi will slup juice away so fast that the device would end up a useless expensive brick far more regularly than is useful.
The same for a camera flash. They kill even dedicated cameras. What would be of more practical use would be better light sensitivity and balance control. 640x480 is more than adequate for quick snaps if the quality is improved. You wouldn't have to torture me to accept better resolution, though
My company specialises in WiFi and Bluetooth connectivity products via telephones and this has taught me a lot about the two. That class 2 BT is used isn't such a bad thing. in fact, in many cases the low power/range class2 is better than class 1 because it reduces interference - this is seriously valuable where gazillions of sad buggers congregate with their phones - being one of those sad sods has taught me why low power is sometimes good!