oddevan

Similarly, I've lost count of how many times I've hit "log in with Facebook" and accidentally created a new account.

Probably something Oauth-like, say Facebook, Twitter, GitHub, tumblr., Google, Yahoo...

You can also look up the runs from years past on YouTube; great way to lose a few hours.

Last year's Super Mario World exploit can be found here: https://www.youtube.com/watch?v=ioQmbEoYL0M

That's fair. By "do-gooders" I was referring to rude people that make it their business to point out all of your problems. Their motivation is not to "do good," it's to be right, and I totally understand not wanting to accept unsolicited input from them because, well, they're rude. :)

So basically I was trying to sidestep the strawman argument.

Out of curiosity, what's the harm in accepting the pull request after someone's already done the work?

Edit: I get not wanting unsolicited input from "do-gooders," but if someone on the project made such a change, would you still reject it?

I think the truth lies somewhere in the middle. You don't want "money-driven people" in the sense that all they care about is doing the least amount of work required to get paid. You want people that are "games-driven" in the sense that they care about putting out a quality product and making a fun game; because of that, they will work harder and should be paid accordingly.

You are absolutely correct in that using the "passion" excuse to force 80-hour weeks and/or underpay workers is BS. An employee being passionate makes them more valuable, not less.

Not looking for dirt or anything, but why the fork? What makes this different from Node?

(Only clue so far is the "open governance model"; is that in contrast to Joyent maintaining Node?)

EDIT: Based on their CONTRIBUTING.md page[1], it looks like this is intended to be a more "community-driven" version of Node. A strike against is that SEVERAL (if not most) links in README.md and CONTRIBUTING.md still reference the joyent/node GitHub project.

[1]: https://github.com/iojs/io.js/blob/v0.12/CONTRIBUTING.md

As a born-and-raised-and-still-living-here South Carolinian, it's always nice to see "positive" coverage of my state.

Speaking to the article itself, I can't imagine having gone through one of these instead of college; I was too set in the college mindset at the time and still treasure the experience (though I'm well aware of its shortcomings). On the other hand, any sort of "learn on the job" scenario would have been TREMENDOUSLY welcome a year and a half ago when I was suddenly without work and struggling to break out of the ".NET Programmer" label. Keeping this sort of option open to everyone can only be a good thing.

Agreed. I'm on a low-data-plus-throttling plan on AT&T's prepaid subsidiary Cricket. I was on their lowest-tier 200MB plan for $15, and if I went over by even 1KB, I was "conveniently" given another 200MB for $15, effectively doubling my data bill. Now, if I go over my limit, I can still get texts and emails while I'm out-and-about, but I can't visit tumblr. I much prefer that, especially if I hit my limit the day before my billing cycle restarts.

The investors have to have some way to convert their ownership in the company into liquid assets at some point. Either that's on the open market through an IPO, by another company through an aquisition, or maybe Ello can have enough cash-on-hand to buy back those shares or pay dividends to their investors.

If there's other ways, please tell me; I'm genuinely curious about this! But as far as I can tell, even "run[ning] an actual business" has to have some sort of "exit" for the investors. It's my hope that Ello can buck the "acquire or IPO" trope, but their investors have to be on board with it. And with $5,500,000 invested, even the most patient investors have a limit.

With the amount of custom chips they needed for the display, it wouldn't surprise me if there are issues getting it to work as an external display that they haven't solved yet.

I was disappointed too, but it was basically "screw off" money. At face value, it doesn't seem like the developer needed to do anything, but I could see it being something along the line of "here's what I've done so far, and in return for me giving this to you, you never talk to me again." The developer is paid in sanity, and while it seems like a bum deal from the outside, I could see myself doing something similar in order to get out of a toxic situation.

I'm not sure about the overdraft charges, but they did require the default for debit cards to "deny" a charge if it would result in an overdraft. So I won't overdraft my account by accident if, for example, I try to buy a $2 drink before my paycheck clears. (Happened once...)

Square tried it. It (sadly) never caught on.

I know I'm being dismissive, but the title of the article is equally dismissive.

I think traditionally Apple has disallowed IAP for real-world goods. I'm assuming Apple Pay will be for those real-world goods while IAP is still used for digital goods.

I'll second this. Bias and prejudice are an unavoidable part of human nature. I wish that wasn't the case, but it's the reality we live in. The most ANY of us can do is 1) Recognize our biases and work to look past them, and 2) Apologize when we get it wrong and try to improve

#2 is the difference between acting like an asshole and being an asshole.

Having a 128GB Air, it would be nice if the client could do selective sync but also sync to more than one volume. I keep my iTunes stuff on a separate drive, but that's one of the first things I would want to sync with 1TB of space.

Excellent proof-of-concept. I want to say Nintendo had a patent that implied something like this for the Wii Virtual Console, but they never delivered on it.

Anyone have any idea if Christian Whitehead's Retro Engine[1] (used in the recent Sonic 1/2/CD remakes) does something like this?

[1] http://christianwhitehead.com/?page_id=51

Thanks for this. I do need to remind myself about victories, even small ones. Especially when it comes time for annual performance reviews. :D

Same here; I would lose eligibility for several (all?) of my scholarships by taking a year off, without which I could not have attended the college I went to (or maybe any college).

If it was anything other than a blanket "don't do this," maybe. It's also like a crowd of new software engineers being told on day one, "By the way, you probably know this, but don't hack the payroll server to boost your paycheck." It's something the average person would never seriously consider, but in the event someone is boneheaded enough to actually do it, it negates the "I didn't know I couldn't" excuse. You can feel insulted if you want, but it's not a message _personally directed at you_, it's a general warning that, because of a few extreme incidents, needs to be explicitly stated out loud.

What if they tell you before you sign up?

Can you elaborate? For example, what is the end-goal of technological innovation? What's the end-goal of any job?

To me, the point of innovation is to make people's lives better. Growing pains, a temporary loss of one type of job, those are inevitable when talking about innovation. But people adapt, they get new jobs, sometimes enabled by the very innovations that displaced them in the first place. That's fine, that's the pattern in the world so far.

A blanket statement like this seems to say that progress for its own sake should be prioritized over the people said progress is supposed to help.

Thanks for the correction!

Which was the bigger tie-in, as the episode the week before ended with the already-released scene of Nick Fury's car chase, and the episode the week after dealt with the (very significant) aftermath.

For many reasons, it was one of the best moments in the series.

IIRC, only if it's statically linked. If it's on the disc as two different binaries that only talk to each other through the OS at runtime, then no, MK8 isn't required to be GPL.

(It's the same principle that allowed Apple to include GCC with Xcode before LLVM came along.)

As far as I know, this is providing a better answer to "How do we know this is valid PHP code?" Currently, the answer to that question is "Because it does/doesn't compile using the standard PHP interpreter." When this spec is finalized, the answer will change to "Because it does/doesn't follow the rules laid out in the PHP specification."

In practice, there is a PHP spec, it's just an "unwritten" spec that is defined in the code of the PHP interpreter. With an official "written" spec, it will open the door to alternative PHP interpreters (like HHVM), since they will be able to say that they also support "PHP" as defined in the spec.

Hope this helps!

If NFC ever takes off as a must-have in the payments world, I'm sure Square would try to use the NFC in phones through their app.

But given that they've already tried a "Just use the app, forget your wallet" approach that didn't take off like they wanted, I'm guessing they're not ready to try anything outside of mainstream payment cards.

But there's also the iOS model to consider:

"Why buy this game if it's not $1?"

I know there's other factors at work, but this is what publishers are (understandably) afraid of.

I think that's also the thinking behind Apple having CloudKit in iOS 8: as I understand, it's a set amount of space/processing per user.