Because bzip2 is horrendously slow, compared to gzip, and the space savings isn't that big a deal in these days of standard-issue 40GB drives? Nothing's stopping you from gunzipping and bzip2ing it.
It can't just be the dubbing. The constant stating (and repetition) of the completely obvious ("Raiden, I see an elevator. You should be able to move between floors..."), the infinite capacity of Our Hero to be stunned by anything said by another character ("..."), and the cheesy who-gives-a-damn interaction between Our Hero and the Love Interest ("Jack, why are you going out with me?") have to be equally lame in the original Japanese.
On the one hand, I don't play a video game for its "story" or its "character development"... I've never seen a single game where that was particularly well done. On the other, I do wish that game developers would figure it out, as the attempts are almost painful sometimes.
I bought a copy yesterday, and have been playing for most of the day today... Visually, the game is stunning, despite the occasional flicker. The storyline is even moderately interesting, which in the realm of video games means it's a "deep" and "involving" "plot". The dialogue still bites, but it's head and shoulders above the original MGS.
Speaking of the original MGS, this is the same game with an upgraded shiny factor. I bought it pretty much because of that, so I'm not disappointed... but if you're looking for any major changes, forget about it. This game also features about the same frustration level... sometimes a room is difficult because the controls are so overloaded, or the camera angle bites, or your timing has to be absolutely perfect.
All things considered, though, I'm having a fairly good time with it. Not nearly as much fun as with GTA3, though, and I'm beginning to wonder what else there is to look forward to on the PS2.
So, I realize that Red Hat is probably just being a smartass, and I'm cool with that. Everybody likes a smartass.
On the other hand, has it occurred to anyone that perhaps they have the same motives as Microsoft, when it comes to getting their software distributed to schools? It would give Red Hat a serious competitive advantage over other Linux distributions, just as it would give Microsoft an advantage over other software vendors in general.
Perhaps it is wise to rally around Red Hat at the moment, as maybe the most serious commercial contender "our camp" has to offer (though that's debatable, even, given their slim lead in actual market share)... or maybe it makes more sense to make deals with multiple software vendors (Apple, various Linux companies, and maybe even Microsoft), and force Microsoft to provide hardware from varying vendors (Apple again, Dell, Gateway, Sun, whoever). This may be difficult due to the price differences among these companies, but I'm sure they'd bend a little.
This way, you don't indoctrinate the children at a million schools in the use of a single vendor's products (diversity is good!), and you make Microsoft dish out some money to its various competitors (competition is good!)
Because unless they just randomly sacked your ass and hate your guts, you'll want to use them as a reference when you go for your next job.
Also, this doesn't just come up when you leave the company... it comes up if you're promoted or moved to another group within the company. What happens, then, if they can't find anyone to take over your weirdass code? It doesn't make you look like an asset, it makes you look like a liability.
Then you will also not have access to detailed information about water pipes, so that you can prevent the easy spread of bacteria.
When you start getting sick, the food processing plant on the edge of town that's pumping brown slime into a big pit swears it isn't them, and the government isn't on the ball, you're telling me you'll rest easy knowing that at least the terrorists don't know about those pipes, either?
Not true. Think about it in terms of competition... if I have a library of PS1 games, and I have a choice between a next-generation system that can play those games and one that can't, which am I more likely to choose?
Consider it from the point of view of a parent who's buying a system for their kid, even.
Also consider that the PS1 was by far the most popular system for years... tapping that existing user base is definitely not "minor" from a sales perspective, especially since it pulled in a lot of people at launch who would otherwise have waited for decent PS2 games to show up, or might have gone with another system by the time that happened.
A major feature of the PS2 is that it can play PSOne games. If the Dreamcast could play PSOne games, PS2 sales would suffer. If PS2 sales suffer, PS2 game and accessory sales suffer.
Take it from one who staffed a booth at the Linux Business Expo: it was a complete waste of time.
COMDEX is all about shiny doo-dads and free keychains. The only reason companies present at COMDEX is so that nobody could say they hadn't been there. LWCE is a better venue even of the shiny-bauble variety for Linux-related companies.
doh. that last post was me, I didn't mean to post anonymously. But no, I actually was referring to the distributions statistics... Red Hat isn't nearly dominant enough to be called a "standard", even if you lump Mandrake in with it (which would not be unreasonable). Debian in particular is giving them a serious run for their money, and that's nice to see. Furthermore, if you take a look at *nix systems in general and not just Linux, the "standardness" of Red Hat dwindles rapidly.
To address a point (to use the term loosely) someone made earlier: I use Slackware partially for the features some would consider "non-standard". Mostly, those features are what helped me get into Linux in a serious way, and now that I know what I'm doing I'd just adapt if they changed. Tarball-based packaging and BSDish init scripts are really nice, but they don't define Slackware any more than the version of grep or KDE that gets installed does.
Nobody uses Slackware because it's hip to be different.. we'd all be thrilled if the other major distributions would fall in line.;)
Well, the reality at the moment is that most people and systems use a Bourne-compatible shell, and/bin/sh is almost universally a Bourne-compatible shell.
So it makes sense to develop startup scripts and basic tools for Bourne. From there, it's a small step to "it makes sense to develop under Bourne", which is the point I was addressing in my original response.
Very few people use a strict Bourne shell on a regular basis. It's just the lowest [most-]common denominator. If something more featureful and less weird were to take its place, I'd be down with that.
(BTW, I obviously don't speak for Slackware. It'd be really nice if Slash would stop displaying that email address. I asked it to do so, even gave it a new one to display instead...)
There are a lot of Bourne-compatible shells that aren't bash-compatible. So sometimes it makes sense to develop for Bourne, if you have to do shell scripting.
On the other hand, sometimes you just don't care, and you can make full use of bash or ksh or whatever.
Slackware uses ash because (a) it's tiny and (b) it's restrictively Bourne-compatible, which means you won't write some tool that is accidentally dependant on bash.
Basically, Slackware uses ash for development for the exact reasons you're looking for a Bourne-compatible shell.
My mom's an elementary school principal. A few of the classes were reading the first Harry Potter book, because, well, they're good books and that's what elementary school is for.
So, one day, she gets a phone call from this horribly irate parent who claims to have a newspaper article detailing the link between Harry Potter and a rise in Satanism among children...
Slashdot Mirror
Hopefully (for everyone involved), more responsible providers will take its place soon.
Oh, wait...
They say it's made of cheese, not vegetable oil.
Bring back something useful, instead of a pest.
ah... sorry. You'd be amazed how many times people have made that argument in all seriousness.
Yeesh. Of all the weak complaints...
That turned out more caustic than I'd intended. Maybe I'm more disappointed in MGS2 than I'd realized. %-)
On the one hand, I don't play a video game for its "story" or its "character development"... I've never seen a single game where that was particularly well done. On the other, I do wish that game developers would figure it out, as the attempts are almost painful sometimes.
Speaking of the original MGS, this is the same game with an upgraded shiny factor. I bought it pretty much because of that, so I'm not disappointed... but if you're looking for any major changes, forget about it. This game also features about the same frustration level... sometimes a room is difficult because the controls are so overloaded, or the camera angle bites, or your timing has to be absolutely perfect.
All things considered, though, I'm having a fairly good time with it. Not nearly as much fun as with GTA3, though, and I'm beginning to wonder what else there is to look forward to on the PS2.
On the other hand, has it occurred to anyone that perhaps they have the same motives as Microsoft, when it comes to getting their software distributed to schools? It would give Red Hat a serious competitive advantage over other Linux distributions, just as it would give Microsoft an advantage over other software vendors in general.
Perhaps it is wise to rally around Red Hat at the moment, as maybe the most serious commercial contender "our camp" has to offer (though that's debatable, even, given their slim lead in actual market share)... or maybe it makes more sense to make deals with multiple software vendors (Apple, various Linux companies, and maybe even Microsoft), and force Microsoft to provide hardware from varying vendors (Apple again, Dell, Gateway, Sun, whoever). This may be difficult due to the price differences among these companies, but I'm sure they'd bend a little.
This way, you don't indoctrinate the children at a million schools in the use of a single vendor's products (diversity is good!), and you make Microsoft dish out some money to its various competitors (competition is good!)
Mix it up a little.
Also, this doesn't just come up when you leave the company... it comes up if you're promoted or moved to another group within the company. What happens, then, if they can't find anyone to take over your weirdass code? It doesn't make you look like an asset, it makes you look like a liability.
Some of us like having a regular employer... we didn't get suckered into The System.
The Matrix used an actual Nokia phone.
When you start getting sick, the food processing plant on the edge of town that's pumping brown slime into a big pit swears it isn't them, and the government isn't on the ball, you're telling me you'll rest easy knowing that at least the terrorists don't know about those pipes, either?
Consider it from the point of view of a parent who's buying a system for their kid, even.
Also consider that the PS1 was by far the most popular system for years... tapping that existing user base is definitely not "minor" from a sales perspective, especially since it pulled in a lot of people at launch who would otherwise have waited for decent PS2 games to show up, or might have gone with another system by the time that happened.
A major feature of the PS2 is that it can play PSOne games. If the Dreamcast could play PSOne games, PS2 sales would suffer. If PS2 sales suffer, PS2 game and accessory sales suffer.
COMDEX is all about shiny doo-dads and free keychains. The only reason companies present at COMDEX is so that nobody could say they hadn't been there. LWCE is a better venue even of the shiny-bauble variety for Linux-related companies.
ALS, of course, is where it's really at.
To address a point (to use the term loosely) someone made earlier: I use Slackware partially for the features some would consider "non-standard". Mostly, those features are what helped me get into Linux in a serious way, and now that I know what I'm doing I'd just adapt if they changed. Tarball-based packaging and BSDish init scripts are really nice, but they don't define Slackware any more than the version of grep or KDE that gets installed does.
Nobody uses Slackware because it's hip to be different.. we'd all be thrilled if the other major distributions would fall in line. ;)
So it makes sense to develop startup scripts and basic tools for Bourne. From there, it's a small step to "it makes sense to develop under Bourne", which is the point I was addressing in my original response.
Very few people use a strict Bourne shell on a regular basis. It's just the lowest [most-]common denominator. If something more featureful and less weird were to take its place, I'd be down with that.
(BTW, I obviously don't speak for Slackware. It'd be really nice if Slash would stop displaying that email address. I asked it to do so, even gave it a new one to display instead...)
On the other hand, sometimes you just don't care, and you can make full use of bash or ksh or whatever.
Basically, Slackware uses ash for development for the exact reasons you're looking for a Bourne-compatible shell.
Have fun.
No shit. Anyone who buys a luxury truck...
I've got some reading for you.
So, one day, she gets a phone call from this horribly irate parent who claims to have a newspaper article detailing the link between Harry Potter and a rise in Satanism among children...
You must be new.