Got a 500 error back from their API once and had an email from one of their engineers in my inbox almost immediately after to find out what happened and resolve it (my http lib was using stale DNS).
1,223 karma · joined September 20, 2010
Got a 500 error back from their API once and had an email from one of their engineers in my inbox almost immediately after to find out what happened and resolve it (my http lib was using stale DNS).
http://en.wikipedia.org/wiki/Gogo_Inflight_Internet
Last couple flights I've usually seen latency between 300ms and 3500ms, 8-10% packet loss. They also seem to use Squid proxy, which doesn't understand WebSockets.
The "the-view-is-the-controller" approach encourages a messy blend of logic and presentation, with lots of HTML ending up in your Scala code.
It's stateful in the extreme, using opaque callback identifiers to identify serialized closures, so rather than having a nice, clean, easy to reason about boundry between your app and the outside world (your routes file, controller methods, whatever), any code anywhere could be invoked by someone clicking something in their browser.
Validation now needs to be enforced in the models, since you no longer have a single place to check it as it comes in. It goes beyond that and embeds rendering logic in models, which have to toForm method which generates HTML.
The extreme statefulness also means you lose everything when you roll a server, you need sticky sessions, you spend way too much time GC'ing and you need far more RAM/user.
Almost as appealing as the screen is that I could charge my phone with any Micro USB cord, instead of these $20 Lightning cables.
When the price is determined, the shares are ready to publicly trade. The underwriter has to ensure that these shares do not trade below the offering price.
If the underwriter finds there is a possibility of the shares trading below the offering price, they can exercise the greenshoe option.
http://www.investopedia.com/articles/optioninvestor/08/green...
First, despite the simplification of the cables, physically connecting it can still be a challenge, for example if there's no convenient place to put a laptop within 6' of the TV. And power for the laptop there too.
Second, once its connected, it's no certainty that the external display will be correctly detected or set to the correct resolution. Is the picture streched? When you hit full-screen, does it only show on the laptop? Is sound going over HDMI too? Tinkering with settings and troubleshooting a multi-monitor setup can be intimidating for the "average consumer".
Even if you get everything setup, many laptops do no come with remote controls, and long HDMI cables are uncommon.
I've owned or own a Roku, a TV which had USB and could play anything FFMPEG could read, a PS3 with netflix and recently an AppleTV+iPad.
I'd consider myself reasonably technically inclined and have had an HDMI cable which comfortably reached my couch for quite awhile but I still use that as a last resort for content I can't play some other way.
Several teams competed, entering driverless cars which interacted with each other and some vehicles operated by real people on a closed course. Carnegie Mellon's Boss car completed all the DARPA conditions and won the grand prize.
I was surprised when I got an email the next day from my congressman thanking me for contacting them and promising a longer reply once they caught up on their backlog.
Whether they OCR'ed it or had some intern doing data entry, either way, they at least extracted my email address from the fax and emailed me, giving me the feeling someone noticed it.
And yet lots of shops pay 37signals for Campfire
I'd say skip the job fairs: In four years, I never considered attending one because they are mostly perceived as boring among your likely target demographic.
Some companies come and give talks about their infrastructure or technology -- these were always what got me excited and interested. I also really enjoyed a few of the competitions and challenges (like Facebook's and Yahoo's).
Just being on campus and doing events which give students a taste of the excitement of creating something would probably generate much more interest than you're seeing now.
I already knew I wanted to work at a startup a year ago, so I had to actively ignore the constant recruiting from the big names while putting effort into chasing down leads with startups. Had I not already known what I wanted (from past internships), it would have been much easier to just sit back and take the pitches which came my way.
Bottom line: come woo us with talks about the cool stuff you do. Send your engineers along too to talk shop with us. Run hack sessions and showcase the winning apps. Show us how much more fun we'd have doing things your way, as opposed to Microsoft's, and you'll have the students you want lining up to apply.
I completely understand if you'd rather wait and see if you can get revenue from it before making that choice, but just know that you do have an eager and ready audience if you decide to pursue other means of distribution.
http://arstechnica.com/tech-policy/news/2011/04/righthaven-r...