manuscreationis's comments

I think any attempt at curing cancer is to be commended, but the fact that they open with this being "The Cancer that killed Steve Jobs" kinds of turns me off...

They name drop him at least 3 times, and it just seems like they're going off his name to help get their (completely admirable and entirely worthwhile) project funded.

The sad fact is, it will probably be more effective than any approach that doesn't leverage someones famous name.

Apple should fund it, however, because of how much of an impact Jobs had on their success and organization as a whole. Funding research to prevent other people from suffering like he did seems like a socially responsible thing to do, especially for a company with a war chest larger than some economies.

In other words, this guy wants you to submit nude photos to his nude photo collector, so he doesn't have to go looking for porno on his own.

All under the thinly veiled guise of testing out an algorithm... Brilliant

Makes sense

Do you think the server would perform more effectively if they had enabled the Cluster configuration (assuming the server has multiple cores)?

I'm fairly new to toying around with Node, so i'd be interested to know if there are fairly obvious or simple reasons for poor performance here

I found a bug

In the Chasm of Fate, after you defeat B'Joril the TimeMaster, you're supposed to get 1 piece of Titan class armor, and a random roll for 1-3 Peacock Plumes, but every time my group only gets the armor, and never any Peacock Plumes.

The devs really rushed this one out. I can't believe they expect people to pay 12 dollars a month for this.

Good luck, hope to hear of whatever product you work on

I'm wondering if it's the age of the SIM card in use...

A few years ago, I upgraded to a new android phone. A day or two later, the SIM card couldn't be detected. Try as I might, it was as though the thing wasn't plugged in.

I took the phone to the nearest carrier store, and the clerk took a look at my SIM card and told me he knew the problem.

My SIM was an older model, and wasn't designed for the heavy amount of... I'll be honest, I don't remember exactly what he said, but the gist of it was the newer phone was activating and accessing the SIM card at a much higher frequency than my old phone did. It had burned the thing out in a manner of 24-48 hours.

They loaded up a new SIM card (which actually had a slightly different look to the connector pins) and everything worked just fine. I couldn't believe it, even though it technically seems plausible.

I'm wondering if this is a similar issue - the new phones are accessing the SIM more frequently, and thus burning them out?

Just a thought

I would go so far as to say VB.NET vs VB6 is the same as comparing any flavor of C++ to C#. It doesn't really make a lot of sense, even though they share the same pedigree.

VB.NET is effectively a different language entirely. It's programming .NET with VB-like syntax, not the VB language running on .NET (in my mind, anyways)

This looks really cool...

I'd like to add that I've used various parts of the ServiceStack suite of products before and I've always found them to be very easy to use, and reliable. Also, the maintainer was always good about responding to bug requests and following up about them.

Glad to see it's still moving forward.

While I agree with the sentiment you're expressing here on some levels (people don't like it when you insult things they like, as they feel they need to defend their choice or themselves because of it), I don't think that quite applies here.

This is a case where, although the ultimate complaint of the author is the behavior of the product (which is documented, but un-intuitive in nature unless you've read up on the issue), it's the way in which he chose to frame the problem that is getting people upset.

This is a known issue, even if it seems like a completely poor design decision. The issue I think most people here are taking is that because the author did almost no research on the topic, he got himself into a problem, and is trying to blame it on Mongo.

This may be a case when using the package manager is not always the best option.

If you're talking about Ubuntu, I can attest that the default PM there is several versions out of date for a lot of things, and thus to get the version you'd expect, you're forced to install by hand.

Also, even using the PM version, didn't you get a warning when you started the server? I thought Mongo threw up a warning at start time about this exact issue (the 2GB limitation, not the silent failures)

Does he have a point that it should have very vocally complained to him that his size limit have been reached, and records were not being stored?

Yes. Without question.

Is this his own fault for not reading the documentation and understanding that he should have opted for the 64bit version outright?

Yes. Without question.

And here I was hoping for some kind of thesis on the woeful state of affairs surrounding the fact they've had 2 major versions competing for developers attention, the with "older" fork being the more the widely supported one.

Equity, no matter how it is structured or offered to you, is a gamble.

Always get cash, and take equity if it's offered (so long as there aren't any strings attached).

Cash will pay your bills today

Lotto tickets may never pay you a dime, and can be a drain on you emotionally if you're constantly expecting one to pay off.

If you're using a framework like rails, it has built in functionality to manage database versioning, but you have to do everything "the rails way", or else you won't get the full benefit of it. The good thing there is, it'll also handle reversing out of a version as well (downgrading).

There are third party takes on this system as well, but I've never tried any of them.

Various places i've worked for have had a very similar (to each other, not to rails) approach to doing versions.

First and foremost, you need a core set of scripts that you are always updating to be the "latest", so that you can very easily spin up an empty db + required static data + any bells and whistles you wanna throw in (like a default user account, for example - although you don't want to run that script on production, clearly).

Then you need another set of scripts that you keep in directories named for their version. Those scripts either reference the scripts inside of your core script directory (for example, if in release 1.4 you're adding a new stored proc, you'd define the proc in your core folder, and in 1.4 you'd have a script that runs all the 1.4 changes, which references the file from the core location), or comprise the DDL changes you're making that are now reflected in your always-updated core scripts (for example, if you modify a table, you'd update the core script to have the latest definition, then add a modification script under 1.4 that just does the diffs to that table)

The most important piece here is an environment to run things in that will handle making changes in a transaction, and rolling things back if something fails (so you can safely do your updates and recover without putting any database in an incomplete or corrupted state). On Windows, Powershell works fine for this (although PS isn't the best thing in the world, it gets the job done). On *nix, i'd imagine you can accomplish the same thing with a bash script. You absolutely do not want to be running scripts by hand, 1 after another. You should have a light set of scripts built around whatever file structure for your sql files you have, that follows a convention based approach to locating an "upgrade.sql" file, which then invokes the rest of the sql files needed for that upgrade.

Hopefully this approach makes sense as I've described it. It's by no means perfect, but as I've said I've seen it in use in several places, and it seems to work just fine.

You could try calling Big Apple Pizza in Fort Pierce florida and try to get in touch with him that way. Frame it that you want to talk to him about a donation to his charity but have been unable to contact him, then once you get a hold of him, explain what the actual donation is.

If you try to go through his employees by saying you want to redo his website, they'd probably be less susceptible.

Just a thought - good luck, that's a rather noble endeavor of yours.

This is all great advice, thanks.

I've watched that video before, and it's a really great talk on a common problem. I'd recommend it to everyone.

Excellent advice about how to scope your hours in terms of your rate. Thanks

Thanks, i'll check it out

Oh crap...

Mine too!