There are several EXT3 implementations for windows, which do you refer? I've had absolutely NO issues with the IFS driver, other than I have to manually add the drive letter each time I boot.
I pretty much use EXT3 for all drives that have to be shared between multiple operating systems, and have had no problems whatsoever.
Although, contrary to parent's comment, it's per CPU, not box, but it's 4 CPUs, and you don't find many system with more than 4 for that type of server.
Most XML I've seen (except, sadly, the IIS metabase.xml) is a significantly bigger pain in the ass to read than a plain old config file - and even the metabase.xml file is moderately more annoying to read. It's not hard to make a config file safely transmittable either.
If the do that, could this kill the atrocity that is XML? One can only hope.
Seriously - for formatting data, it's overly complex. For storing and transmitting data, plain old config files are easier to read AND easier to parse...
You make the assumption that they aren't developing a FOSS replacement while using the commercial app.
In the case of huge apps, where a couple-week dev marathon can't replace the original, then using the closed source app may be the only short term option.
That doesn't excuse pirating the app, in the cases where it's done, but at the same time, it's a perfectly reasonable course of action to use the CSA.
Or running java on the problematic platform, for whatever reason is non-trivial. In these cases, debugging takes a lot longer. Of course, the latter case can be blamed on bad business practices, and not the language itself. Still, when you expect something to be completely cross platform, it shouldn't rely on native implementations of anything, unless the code base is shared (ex. they could use OpenSSL instead of Sun's implementation since that seems to be everywhere).
Slashdot Mirror
Why do you have your own person to turn cows into orks in the next cubicle? Is that a big thing where you work?
I'm not sure why I would complain about no free coffee...
My work never supplied that :-(
Great, XML is better than SQL for some data manipulation tasks.
Last I checked, XML and SQL weren't the only options.
There are several EXT3 implementations for windows, which do you refer? I've had absolutely NO issues with the IFS driver, other than I have to manually add the drive letter each time I boot.
I pretty much use EXT3 for all drives that have to be shared between multiple operating systems, and have had no problems whatsoever.
Ahh, if they hired engineers like they hired software devs.
Actually, where's the guy with the woodpecker destroying civilization in his sig when you need him?
That's kindof what I think about XML.
And if human readable is your is your goal, extend that analogy to using a fresh loaf of bread as your screws.
He said "starts at", not "the ultra high end model".
$660 for the entry model "standard" server (non-upgrade): http://www.newegg.com/Product/Product.aspx?Item=N82E16832116452
Although, contrary to parent's comment, it's per CPU, not box, but it's 4 CPUs, and you don't find many system with more than 4 for that type of server.
Or $680 for the Itanium variant like what you mentioned - no processor limit mentioned: http://www.newegg.com/Product/Product.aspx?Item=N82E16832116806
Most XML I've seen (except, sadly, the IIS metabase.xml) is a significantly bigger pain in the ass to read than a plain old config file - and even the metabase.xml file is moderately more annoying to read. It's not hard to make a config file safely transmittable either.
OK, I do like DOM, but the only XML I've seen that I've actually not minded, was in the IIS configuration (metabase.xml)...
It's pretty sad when it's Microsoft that "did it right".
Then again, maybe it's just because *everyone* uses it for their configuration files, which is really not a place that XML should be used IMHO.
That still doesn't give it an advantage over a config file.
something=type ...
something.foo=a
something.bar=b
That would cover ColdFusion wouldn't it?
If the do that, could this kill the atrocity that is XML? One can only hope.
Seriously - for formatting data, it's overly complex. For storing and transmitting data, plain old config files are easier to read AND easier to parse...
What actual purpose does XML serve?
Definetly. It could have used a secure login setup (which, I think was planned for the next release...), but otherwise it was by far my favorite OS.
Fast, stable, needed more app support, UI was quiet an clean...
*sigh*
Vista was tolerable with SP1, albeit way to slow (I'm talking on a 2.0Ghz Core 2 Duo with 2GB memory).
XP, on the same machine, not surprisingly, was a *LOT* faster
7, on that machine, is between the two, but close enough to XP that I don't mind using it.
You can, but it costs a lot, usually. Unfortunately, I don't know if it will help your credit score or not.
You make the assumption that they aren't developing a FOSS replacement while using the commercial app.
In the case of huge apps, where a couple-week dev marathon can't replace the original, then using the closed source app may be the only short term option.
That doesn't excuse pirating the app, in the cases where it's done, but at the same time, it's a perfectly reasonable course of action to use the CSA.
Collectors harass you, your credit record goes to pot.
Eventually they take you to court and get the money from you, even if it's drawn straight from your account at the judges authority.
Not the open source community I've seen.
"Use open source, if for some reason it isn't possible, pirate the closed source app" seems to be the more common MO.
Slashdot always has good propagation on the WTF band!
I was trying to remember the method, since I no longer have the old code. It was either indexOf, or matches.
They are different, but both cause troubles.
I'm just saying that neither is perfect (or in my experience/practice significantly better than the other), both have pros and cons.
Actually, the string.find() method, I believe, was what differed for me between Win/Linux and HPUX.
That would be in the standard stack, right?
Thank you for saving me (and others) the necessity of correcting you.
Ahh, but the mono team developed drop-in replacements for many of the call, making it work in a lot of usual cases.
As i said, it isn't perfect, but it's not really bad either.
Addendum:
Or running java on the problematic platform, for whatever reason is non-trivial. In these cases, debugging takes a lot longer. Of course, the latter case can be blamed on bad business practices, and not the language itself. Still, when you expect something to be completely cross platform, it shouldn't rely on native implementations of anything, unless the code base is shared (ex. they could use OpenSSL instead of Sun's implementation since that seems to be everywhere).