Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Re:DRM (Score 1) 206

This. I don't want any source code for the game (although it would be nice) but not getting anything but the right to play a game on a souped-up terminal server for the full price? No thanks. It's bad enough when companies decide to turn off the multiplayer servers for console titles while people still play the game online. All Onlive does is taking away your power in exchange for slightly better prices, worse image quality, higher latency and the need for a high-speed Internet connection.

Comment Re:eh? big surprise? (Score 1) 108

Instead they installed grass and waited ~six months for the students/professors to collectively define the necessary paths to and from the building. The University would then install the pavement, routing them to match the paths worn into the grass. This yielded some interesting walkways but they always seemed to make sense.

That is actually pretty cool, as far as sidewalks go. The ants are just being lazy with their sneakernet and so are we :>

Comment Re:How to accept the consequences (Score 1) 352

Not on my play through, no. My character never said anything like that and openly told some of the racist to shut their traps. Bioware should've made ME more aware of my previous actions or allowed me to explain myself instead of just whacking me over the head with renegade points. It basically went like this:
Council ship: OMG we're getting shot at, protect us while we flee!
Shepard: Nope, we need every ship to defeat Sovereign and I'm not going to sacrifice the life of civilians on the Citadel and soldiers on out ships just so you are guaranteed to get out of here in one piece. Sorry, you're on your own.
Council ship: FUUUUUuuuu*explodes*

Comment Re:How to accept the consequences (Score 1) 352

At the end of the first game I let the council die. It was for all the right reasons, there was a giant spaceship Cthulu about to destroy all life as we knew it and I didn't want to lose vital military assets and threaten the survival of the Galaxy for some symbolic gesture. Turned out to be the 'wrong decision' in the overall theme of being the good guy and uniting all races in mass Effect 2 but I stuck with it because I would always have made that decision with the knowledge I had to hand and it also made the storyline and reactions to you on the citadel more interesting in the 2nd game

Yeah, it's stupid that not saving the fleeing council but instead focusing on the dreadnought that's ripping apart the citadel where millions of people might die is a "renegade" action. It's a friggin' elected council, those guys aren't "worth" more than any other person. Just elect a new representative and carry on, geez.

Comment What happen? (Score 1) 352

I wonder if he lost some of the major NPCs by assigning them the wrong tasks and/or the crew of the ship.

Spoilers ahead!
On my first play through I messed around for a bit before starting the final mission and lost the entire Normandy II crew in a horrible, graphic way. I really didn't expect it and actually felt bad for them. Second time playing only Thane bit the dust because I don't want to see him in ME3 :>
Games

Balancing Choice With Irreversible Consequences In Games 352

The Moving Pixels blog has an article about the delicate balance within video games between giving players meaningful choices and consequences that cannot necessarily be changed if the player doesn't like her choice afterward. Quoting: "One of my more visceral experiences in gaming came recently while playing Mass Effect 2, in which a series of events led me to believe that I'd just indirectly murdered most of my crew. When the cutscenes ended, I was rocking in my chair, eyes wide, heart pounding, and as control was given over to me once more, I did the only thing that I thought was reasonable to do: I reset the game. This, of course, only led to the revelation that the event was preordained and the inference that (by BioWare's logic) a high degree of magical charisma and blue-colored decision making meant that I could get everything back to normal. ... Charitably, I could say BioWare at least did a good job of conditioning my expectations in such a way that the game could garner this response, but the fact remains: when confronted with a consequence that I couldn't handle, my immediate player's response was to stop and get a do-over. Inevitability was only something that I could accept once it was directly shown to me."

Comment Re:Haskell (Score 1) 728

It appears you are not familiar with Haskell or [this][http://en.wikipedia.org/wiki/Curry%E2%80%93Howard_correspondence].

I'm more familiar with Haskell than I'd like to be, thank you. What I meant is that programmers shouldn't use the horrible syntax you use in math for programming, e.G. no "funny" characters, descriptive names and all that.

Comment Haskell (Score 3, Interesting) 728

Haskell supports various unicode characters as operators and it makes me wanna to puke. http://hackage.haskell.org/trac/haskell-prime/wiki/UnicodeInHaskellSource IMO one of the great things about programming nowadays is that you can use descriptive names without feeling bad. Single character identifiers from different alphabets are something that rub me the wrong way in mathematics. Keep 'em out of my programming languages!

Bullshit from the article:

Unicode has the entire gamut of Greek letters, mathematical and technical symbols, brackets, brockets, sprockets, and weird and wonderful glyphs such as "Dentistry symbol light down and horizontal with wave" (0x23c7). Why do we still have to name variables OmegaZero when our computers now know how to render 0x03a9+0x2080 properly?

OmegaZero is at least something everybody will recognize. And why would you name a variable like that anyway? It's programming, not math, use descriptive names.

But programs are still decisively vertical, to the point of being horizontally challenged. Why can't we pull minor scopes and subroutines out in that right-hand space and thus make them supportive to the understanding of the main body of code?

Because we're not using the same IDE?

And need I remind anybody that you cannot buy a monochrome screen anymore? Syntax-coloring editors are the default. Why not make color part of the syntax? Why not tell the compiler about protected code regions by putting them on a framed light gray background? Or provide hints about likely and unlikely code paths with a green or red background tint?

... what?

For some reason computer people are so conservative that we still find it more uncompromisingly important for our source code to be compatible with a Teletype ASR-33 terminal and its 1963-vintage ASCII table than it is for us to be able to express our intentions clearly.

... WHAT? If you don't express your intentions clearly in a program it won't work!

And, yes, me too: I wrote this in vi(1), which is why the article does not have all the fancy Unicode glyphs in the first place.

vim does Unicode just fine. And from the Wikipedia entry on the author (http://en.wikipedia.org/wiki/Poul-Henning_Kamp):

A post by Poul-Henning is responsible for the widespread use of the term bikeshed colour to describe contentious but otherwise meaningless technical debates over trivialities in open source projects.

Irony? Why does this guy come off as an idiot who got annoyed by VB in this article when he clearly should know better?

Slashdot Top Deals

An authority is a person who can tell you more about something than you really care to know.

Working...