borlak
On boot as it's loading players, their file descriptor ID was saved, so it loads it up and resumes talking to the socket. It also loads the ID of the server socket descriptor. No need to send information to a new process as it just loads the previous game state.
If you're curious: https://github.com/borlak/acmud/blob/7c2442dfccfc28364fc399a...
And: https://github.com/borlak/acmud/blob/7c2442dfccfc28364fc399a...
I found a couple examples that do the scrypt part with GPU in browser, but your browser has to support custom shaders, I think (I forget the details), and the version most browsers support doesn't allow this (again, my memory is sketchy about the details).
Anyway Here you go, NJ! https://github.com/borlak/cryptocoin_scrypt_stratum
Basically, "it depends". having dealt with extremely DB-intensive applications, I have developed a personal motto of "be nice to the DB".
Let the DB be a secure storage of your data, not a calculating part of your application. But like the top answer says, sometimes it is not practical to do a calculation within the application. In my case, we had a few database servers set aside just for reporting, so we could slam them with difficult queries and not worry about affecting data.
The Microsoft installation progress bars are the ones I remember as being ridiculous. Often going backwards, showing ridiculous install times, etc.
The human history of inventing has one very consistent theme: making things easier for ourselves. "Computers" will only become easier to use, and require less knowledge of the humans that are using them.
When "computers" go wrong, a human with that specialty will fix it. You have that specialty. Why can't everyone fix their own cars or HVACs or bake their own bread?
Growing pains -- the kind of pains we all want to endure some day. If you are planning to grow, why wouldn't you start with something you know has an end game (like PHP or Java)?
The often cited slowness of Rails, mixed with companies rewriting their codebases, and the flurry of vulnerabilities in the past year has caused me to take Rails less seriously.
Parts of your application may rely on the expiration feature. But the biggest change is the inability to overwrite a current cache key. Every application I've used does this constantly (object updates).
Groupcache in its current form is useful for a very narrow set of applications.
Some things that we did: autoplaying videos. enormous graphics and big text. lots of "as seen on !". landing page was probably 6000-7000 pixels high and the form was near the bottom.
At a previous company our target audience was older women. We A-B tested every single element on our landing page, and I can tell you, using the advice on this site would be a complete disaster.
You could even argue that an API would not be 'direct access'
Responding to petitions by telling the petitioners to petition harder is kind of pointless.
The only thing I would complain about is the lack of a proxy or load balancer in front of their Multi-AZ setup. With any failover you are forced to have a downtime of 3-5 minutes while DNS propagates.
TheRoyalInstitution (science stuff, professionally done)
periodicvideos (excellent channel, chemistry stuff)
numberphile (math)
minutephysics (physics)
sixtysymbols (physics/math stuff)
DeepSkyVideos (space stuff, not updated often)
psyfile (psychology, not updated often)
engineerguyvideo (was really good, now rarely updates)
computerphile (brand new channel, no content yet, from same guys as the other *phile channels)
and for fun: JoergSprave (the slingshot guy, but his creations are quite cool if you like physics)
Going through the HN job postings, my findings are:
Ruby with 6.5 jobs
Python with 4
Java and ObjC each with 2
Node.js and CoffeScript each with 1
Sorry for not sourcing anything, I don't want a massive post. Seems Ruby is still pretty cool. Anyway, this is quite the normal distribution here from my experience. And in the interest of full disclosure -- I am not a Ruby developer.
You can have all the view you want and believe in yourself -- but willpower doesn't equal success.
You play your game, and if you want to do something social and the servers are down -- it sucks, but you can still play, and take part in the social stuff when it is up and working.
For online saves -- there is a local backup for when the online system is down.
These are not difficult things. They are just trying to fight an ever-losing battle against piracy.