Samus Aran does not count as the first female action hero. Because no one knew. I am certain that the designers of Metroid thought it was a guy inside that armor.
Oh, thought it was a guy and then accidentally brutally not only put a woman in the end credits, but also designed an alternate player sprite that was clearly a woman? (Start Metroid with code "000000 000020 000000 000020", or if you prefer the more famous code, "JUSTIN BAILEY" with the rest as space, and you'll get the alternate sprite.)
Also, it definitely didn't take that long until the word got out, and by the time Metroid II or Super Metroid came out, everyone knew, and those pre-date TR quite definitely too... =)
Sort of clever, but it'd be infinitely easier and more efficient to put that in a network drive, then put "./mnt/thatthingy/etc/aliases.sh" in their ~/.bash_profile. Pulling the thing with Lynx is kind of silly.
The only difference between open source and free software is the marketing philosophy, anyway. If something isn't free software, it's by definition not open source, either.
They are also not targeted due to the fact that they keep changing OSs, processors and whatnot such that any Mac (OSX PPC, OSX x86, OS9 PPC, OS9 Moto) is a subset of an already small market share.
MS-DOS on a 286, MS-DOS on a 386, Windows 3.1 on 386, Windows 3.1 on 486, Windows 95 on 486, Windows 95 on Pentium, Windows 98 on Pentium, Window 98 on Pentium II, Windows 2000 on Pentium III, Windows 2000 on AMD...
Granted, the assembly instructions subset needed to implement and run viruses probably got laid down in the 8088 era, but still =)
Actually I think EAX is catching up. Slowly, but they are.
And I think A3D was amazing also because it ran on the driver, not the card hardware - some tightly packed assembly wizardry, I believe. Also why Aureal was so reluctant to let people do open source drivers for Linux, and why OpenAL progressed so slowly initially when they were around =) Or that's just how I've heard.
What's so "Web 2.0" about Bloglines? It's a plain old CGI stuff with some JavaScript thrown on the interface.
Well, if it does have XMLHttpRequest stuff there somewhere, I have to indeed give it a little bit of credit - it's then one of the few "Web 2.0" websites I've tried that don't have small but weird user interface issues and works in the tried and true and logical way.
Except that bug a while ago when the whole thing turned Japanese while I wasn't looking.
May be so, but the Mikrobitti 1/89 review of a voice-activated controller called Lipstick Plus is still my favorite hardware review I've ever read. So funny that I can remember parts of it without even looking, and my copy of the mag is across the country, so the following may have some errors.
"The walls of ancient Jericho got destroyed by voice. The scientists have now closed the Ultimate Book, and produced the Ultimate Joystick Controller: Lipstick Plus." "...when you say 'FIRE', it is as if you have pressed the fire button. But in reality, it doesn't matter if you say 'Gnnip!', recite poetry or just blow into the microphone." "Going RATATATATATATAKABLOOM did produce amazing firepower, the biggest problem, though, was how the environment reacted" "The thing doesn't react to half-muttered 'come here, you nasty little *beep*, gramps got some nice things for you', but 'BITE LEAD!' will launch the missiles." "...one of the problem was that the throat of the sound signal generator got a bit dry."
Ratings should draw attention to the low quality of articles on topics that don't attract enough attention.
Which brings us to another social problem: It's one thing to list good articles, interesting articles, or like. There's always a few of them. I love browsing the Unusual Articles, for example. But then for the opposite end of the coin you can go look at the Articles for Deletion, or Dead-End Pages, or most of the cleanup or stub categories. What happens if you slap those on people's faces? "350,000 articles that don't draw attention, please fix these"? That's right: People say "damn that, there's too much work to do" and go away.
I like the current approach where we have WikiProjects and people can list articles that need work. I think it's better this way: I'm going somewhere, saying "this page needs work" I can comment on why the thing needs work. "here's what needs to be done." What you're proposing is a faceless system that just screams "this article needs attention" and doesn't tell why people should spend time fixing this particular article right now. It's easy to slap down a few stars, but it'd help a lot more if people would tell what's wrong with the article. An automated rating would just encourage faceless, unhelpful critique. It's not *always* obvious why you gave just one star - maybe it's just because you hate misplaced commas, maybe it's a political act against the incumbent president. (Hey, uncovering an NPOV problem with this approach, too.)
Most of the "rating" systems online don't measure quality; they measure popularity. You always get five stars on some popular topic that gets a lot of attention anyway, while marginal topics don't.
One way would be that you'd have to make sure each user would be subjected to mandatory daily "metamoderation" of random articles on their field of expertise, and the thing that kills that is that the "expertise" of all users varies depending on whether or not they've had their morning coffee, or whatever. Currently, Wikipedia works because editors are monitoring topics they care about when they care about.
I think it's not an original idea; if you mentioned that near anyone who knew anything about Plan 9, you'd probably get one of those famous Replies. =)
gnome-vfs, kioslaves, etc aren't the optimal approach to this stuff, either - they're accessed via libraries, meaning applications have to specifically support them. Wake me up when I can, for example, use KDE's leet CD ripper with nothing but/bin/bash and/bin/cp on my side. Can't do that right now - applications need to be wired up properly to understand those.
Well, fortunately, there's light ahead in this respect. Maybe in a few years.
Yeah, well, I know I personally did a really dark room for Doom 3 once, so I was certain about that game being supported. I kind of assumed Q4 would be supported because previous games sure were; I assume Q4 support is just in works then =)
GtkRadiant is also used by Crystal Space and Neverball, and probably some others too; I sure hope this means more OSS software adopts it in future =)
Though, parental controls are nothing new. MSIE has supported PICS since stone age. The funny thing is, I don't know how to get Mozilla browsers to react on PICS labels, but luckily, no one asks.
They also have long traditions in handling with massive videogame-related disasters. In the 1980s they even had superheroes to deal with them. Or cause them.
(A big grin from comics fans in Scandinavia, and wishing luck too =)
Also, what does this even mean? The boss is a point. You are a point. How is one point parallel to another? Did I sleep through half of the axioms of Euclidean geometry?
I have no idea what either of you is talking about, but I'd believe that the point where the player is (A) and the point where the player's guns are (B) are enough to define a line (AB) that the player is firing along (away from both points to the direction of B). Alternatively, B can represent some arbitrary point along the player's line of sight. And same goes for the boss (Boss location C, boss firing point D, line of fire CD). I believe the other poster was warning against the case where AB = CD or close enough.
I don't know damn about mathematics, but sometimes, elementary geometry keeps me awake, especially if it can be illustrated this way. =)
However, it's in Perl. And I really have to ask myself; Do I want to play games coded by people who started programming games in perl?
Yeah - do I want to play games coded by people who started programming games in pure assembler? I mean, even the best game programmers make indecipherable code, and then they had to do that in a cryptic language that few people have patience to learn... =)
But seriously, whenever you code a game, you always end up using a scripting language of some kind. Perhaps this just cuts out that virtual middleman that is c/c++?
I think that Perl/Python/Ruby + SDL is definitely going to be an interesting as a whole platform for simpler games.
The scripting languages have also proved to be excellent platforms to do all sorts of prototypes of humongous systems in. With SDL, also great for game prototypes, even full games.
And yes, they are also great as an embedded interpreter in "real" games.
Or rather, Theora's time, which not only is actually implemented in multiple popular cross-platform player softwares (VLC, RealPlayer) and has a nice converter (ffmpeg2theora), it's also - hopefully - proven to be free of patent issues. =)
A wild guess, but I guess they won't be going after them - just people who use ffmpeg binaries for profit (that is, put that thing in their own products). At least that's how things have been with MP3 licensing.
Of course, they could go silly and make license demands like Dolby does with AAC ("don't distribute compiled binaries or we'll get nasty", I think).
"Possibly later"? Probably going to be an understatement, knowing how slowly Nintendo releases stuff in Europe. March in Japan, May in US, and July in EU. (It would be easy to go cracking something about "yeah, but which year?", but I'm not going to... =)
I don't know when they're released, but one thing is sure, it won't be next weekend. =)
Oh, thought it was a guy and then accidentally brutally not only put a woman in the end credits, but also designed an alternate player sprite that was clearly a woman? (Start Metroid with code "000000 000020 000000 000020", or if you prefer the more famous code, "JUSTIN BAILEY" with the rest as space, and you'll get the alternate sprite.)
Also, it definitely didn't take that long until the word got out, and by the time Metroid II or Super Metroid came out, everyone knew, and those pre-date TR quite definitely too... =)
Sort of clever, but it'd be infinitely easier and more efficient to put that in a network drive, then put ". /mnt/thatthingy/etc/aliases.sh" in their ~/.bash_profile. Pulling the thing with Lynx is kind of silly.
Umm, they specifically say it's not open source!
The only difference between open source and free software is the marketing philosophy, anyway. If something isn't free software, it's by definition not open source, either.
MS-DOS on a 286, MS-DOS on a 386, Windows 3.1 on 386, Windows 3.1 on 486, Windows 95 on 486, Windows 95 on Pentium, Windows 98 on Pentium, Window 98 on Pentium II, Windows 2000 on Pentium III, Windows 2000 on AMD...
Granted, the assembly instructions subset needed to implement and run viruses probably got laid down in the 8088 era, but still =)
Actually I think EAX is catching up. Slowly, but they are.
And I think A3D was amazing also because it ran on the driver, not the card hardware - some tightly packed assembly wizardry, I believe. Also why Aureal was so reluctant to let people do open source drivers for Linux, and why OpenAL progressed so slowly initially when they were around =) Or that's just how I've heard.
What's so "Web 2.0" about Bloglines? It's a plain old CGI stuff with some JavaScript thrown on the interface.
Well, if it does have XMLHttpRequest stuff there somewhere, I have to indeed give it a little bit of credit - it's then one of the few "Web 2.0" websites I've tried that don't have small but weird user interface issues and works in the tried and true and logical way.
Except that bug a while ago when the whole thing turned Japanese while I wasn't looking.
Slightly silly placement? Definitely. Worst possible? Hell no.
At least the games tend to be designed so that you don't need that thing all the time and together with the other shoulder buttons.
GC controller is still the best controller I've ever had, even with that little silliness.
May be so, but the Mikrobitti 1/89 review of a voice-activated controller called Lipstick Plus is still my favorite hardware review I've ever read. So funny that I can remember parts of it without even looking, and my copy of the mag is across the country, so the following may have some errors.
"The walls of ancient Jericho got destroyed by voice. The scientists have now closed the Ultimate Book, and produced the Ultimate Joystick Controller: Lipstick Plus." "...when you say 'FIRE', it is as if you have pressed the fire button. But in reality, it doesn't matter if you say 'Gnnip!', recite poetry or just blow into the microphone." "Going RATATATATATATAKABLOOM did produce amazing firepower, the biggest problem, though, was how the environment reacted" "The thing doesn't react to half-muttered 'come here, you nasty little *beep*, gramps got some nice things for you', but 'BITE LEAD!' will launch the missiles." "...one of the problem was that the throat of the sound signal generator got a bit dry."
Commodore didn't make really good joysticks. My friend bought one of those C64G bundles and by the end of the week, the stick was busted.
I remember one of their "popular" sticks. Triangular handle. Triangular.
(But I hope everyone knows what's the best C64 stick. =)
Um, people who violate OSS licenses, perhaps? It shouldn't matter who gets paid, as long as the lawyers get paid, you know?
(I know you tried to be funny, and succeeded, too. =)
Which brings us to another social problem: It's one thing to list good articles, interesting articles, or like. There's always a few of them. I love browsing the Unusual Articles, for example. But then for the opposite end of the coin you can go look at the Articles for Deletion, or Dead-End Pages, or most of the cleanup or stub categories. What happens if you slap those on people's faces? "350,000 articles that don't draw attention, please fix these"? That's right: People say "damn that, there's too much work to do" and go away.
I like the current approach where we have WikiProjects and people can list articles that need work. I think it's better this way: I'm going somewhere, saying "this page needs work" I can comment on why the thing needs work. "here's what needs to be done." What you're proposing is a faceless system that just screams "this article needs attention" and doesn't tell why people should spend time fixing this particular article right now. It's easy to slap down a few stars, but it'd help a lot more if people would tell what's wrong with the article. An automated rating would just encourage faceless, unhelpful critique. It's not *always* obvious why you gave just one star - maybe it's just because you hate misplaced commas, maybe it's a political act against the incumbent president. (Hey, uncovering an NPOV problem with this approach, too.)
And how do you rate the articles?
Most of the "rating" systems online don't measure quality; they measure popularity. You always get five stars on some popular topic that gets a lot of attention anyway, while marginal topics don't.
One way would be that you'd have to make sure each user would be subjected to mandatory daily "metamoderation" of random articles on their field of expertise, and the thing that kills that is that the "expertise" of all users varies depending on whether or not they've had their morning coffee, or whatever. Currently, Wikipedia works because editors are monitoring topics they care about when they care about.
GPL 2. GPL 3 isn't released yet - it will be clarified further and there may be some other changes.
And the source code seems to have the upwards-compatibility clause too, so they may go for GPL 3 after it's out!
I think it's not an original idea; if you mentioned that near anyone who knew anything about Plan 9, you'd probably get one of those famous Replies. =)
gnome-vfs, kioslaves, etc aren't the optimal approach to this stuff, either - they're accessed via libraries, meaning applications have to specifically support them. Wake me up when I can, for example, use KDE's leet CD ripper with nothing but /bin/bash and /bin/cp on my side. Can't do that right now - applications need to be wired up properly to understand those.
Well, fortunately, there's light ahead in this respect. Maybe in a few years.
Yeah, well, I know I personally did a really dark room for Doom 3 once, so I was certain about that game being supported. I kind of assumed Q4 would be supported because previous games sure were; I assume Q4 support is just in works then =)
GtkRadiant is also used by Crystal Space and Neverball, and probably some others too; I sure hope this means more OSS software adopts it in future =)
"Hello, Hunam! What would you like to threaten me about today?" =)
Yep, I think it does Doom 3 and Quake 4. I hear the thing is pretty extensible.
apt-get install dansguardian.
Though, parental controls are nothing new. MSIE has supported PICS since stone age. The funny thing is, I don't know how to get Mozilla browsers to react on PICS labels, but luckily, no one asks.
They also have long traditions in handling with massive videogame-related disasters. In the 1980s they even had superheroes to deal with them. Or cause them.
(A big grin from comics fans in Scandinavia, and wishing luck too =)
I have no idea what either of you is talking about, but I'd believe that the point where the player is (A) and the point where the player's guns are (B) are enough to define a line (AB) that the player is firing along (away from both points to the direction of B). Alternatively, B can represent some arbitrary point along the player's line of sight. And same goes for the boss (Boss location C, boss firing point D, line of fire CD). I believe the other poster was warning against the case where AB = CD or close enough.
I don't know damn about mathematics, but sometimes, elementary geometry keeps me awake, especially if it can be illustrated this way. =)
You can use OpenGL in SDL. The net effect, with all of the SDL extra libraries is something along the lines of the entire DirectX toolkit already.
Yeah - do I want to play games coded by people who started programming games in pure assembler? I mean, even the best game programmers make indecipherable code, and then they had to do that in a cryptic language that few people have patience to learn... =)
I think that Perl/Python/Ruby + SDL is definitely going to be an interesting as a whole platform for simpler games.
The scripting languages have also proved to be excellent platforms to do all sorts of prototypes of humongous systems in. With SDL, also great for game prototypes, even full games.
And yes, they are also great as an embedded interpreter in "real" games.
Or rather, Theora's time, which not only is actually implemented in multiple popular cross-platform player softwares (VLC, RealPlayer) and has a nice converter (ffmpeg2theora), it's also - hopefully - proven to be free of patent issues. =)
A wild guess, but I guess they won't be going after them - just people who use ffmpeg binaries for profit (that is, put that thing in their own products). At least that's how things have been with MP3 licensing.
Of course, they could go silly and make license demands like Dolby does with AAC ("don't distribute compiled binaries or we'll get nasty", I think).
"Possibly later"? Probably going to be an understatement, knowing how slowly Nintendo releases stuff in Europe. March in Japan, May in US, and July in EU. (It would be easy to go cracking something about "yeah, but which year?", but I'm not going to... =)
I don't know when they're released, but one thing is sure, it won't be next weekend. =)