The logistics for ensuring food arrives hot when you don't have any control over the cooking process and timing is hard, but they always managed to do it. I'm impressed.
1,760 karma · joined July 6, 2008
The logistics for ensuring food arrives hot when you don't have any control over the cooking process and timing is hard, but they always managed to do it. I'm impressed.
1) Turning off iMessage on old iPhone 2) Removing phone number from my Apple account 3) Friends removing my cell # from their address books
and a few other random things. Nothing has fixed it. The only way a friend with an iOS device can SMS me is if they turn of iMessage. This is a pretty huge bug on Apple's part.
prerender.io does do most of what we do. A few things we do differently are keeping a pool of PhantomJS workers always available, killing HTTP requests that never complete, putting it behind HAproxy and logging.
Create a spreadsheet, write some benchmarking tools, make sure you aren't actually benchmarking another service the instance depends on (db, API, etc) and go to town. Vary # of request/sec, # of parallel requests, # of app workers/threads/etc.
Write down all your results and then compute amount of 'work' (reqs/sec, computations, db inserts/updates, etc) vs hourly or RI pricing. That should get you some good numbers on what instance type is most cost effective for your workload.
This library could use error detection and handling as there are situations where fullscreen could be aborted or fail to start.
It's much better to attempt going fullscreen and have callbacks for errors and successfully entering fullscreen mode. Users can have preferences set to not allow it, press ESC during the transition or a number of other scenarios can occur.
There's also some CSS fixes between browsers that could be included. Safari and Chrome don't stretch the element to 100% monitor width and don't apply a background color by default so you can see 'through' the fullscreen window.
That being said it's good someone is working towards something that's relatively cross-browser. The fullscreen API right now is extremely varied but a really awesome tool for advanced web apps.
There's a reason why they don't send the latest and greatest camera or computer technology into space.
We're looking for QA, iOS developers, web developers (frontend and backend) and designers.
We created Camera Awesome, a top iTunes Store app, and are the leading photo website for pros who shoot everything from BMX to brides. We're proudly profitable, free and clear of VC investors.
Our core technologies are PHP, MySQL, Memcache, Go, EC2, S3 and YUI. We're also doing a lot of new work with iOS on Camera Awesome.
We have our own personal chef, awesome (private!) offices with at $500 decoration budget when you start, just about any hardware you desire and yearly company trips (http://cmac.smugmug.com/Photography/Jackson-Hole/1/18570755_...).
If you're interested send your resumes to jobs@smugmug.com
We're looking for QA, iOS developers, web developers (frontend and backend) and designers.
We created Camera Awesome, a top iTunes Store app, and are the leading photo website for pros who shoot everything from BMX to brides. We're proudly profitable, free and clear of VC investors.
Our core technologies are PHP, MySQL, Memcache, EC2, S3 and YUI. We're also doing a lot of new work with iOS on Camera Awesome.
We have our own personal chef, awesome (private!) offices with at $500 decoration budget when you start, just about any hardware you desire and yearly company trips (http://cmac.smugmug.com/Photography/Jackson-Hole/1/18570755_...).
If you're interested send me an email (rdoherty@smugmug.com).
Good documentation can easily trump bad code and architecture.
This seems like a cool idea but the harsh realities of battery life, weather, maintenance, etc will most likely prove it unfeasible.
Serving a plain HTML page over localhost via nginx. A medium length blog post with pretty much no real-world information.
Really? I've been pretty happy with IE9, generally 98% of my code works perfectly, it's just a matter of drop shadows, rounded corners, etc that don't work. I honestly want to know what breaks so horribly that it's like coding a site twice.
My memories of IE6 make IE9 seem like a completely different browser. It is somewhat, since they rewrote their rendering engine to fully support CSS 2.1 in IE8.
Also, considering saving money on hardware costs is a key factor in Backblaze staying competitive, they must be saving money elsewhere and/or have other competitive advantages. Otherwise releasing this information would be akin to publishing a restaurant's 'secret sauce'.