ameswarb
ameswarb on Hacker News
Many of those that flex their MRR on Twitter and participate in the "build in public" trend are also digital nomads who regularly travel to countries with a low cost of living. In some of these countries it's not uncommon for flight manifests to be illicitly sold so that would-be kidnappers can search the passenger list for potential ransom targets. I worry that it's only a matter of time before we hear about one of these makers being abducted.
Most communities rely on third party moderation services and tools which will also be impacted by the API changes. Many have said that moderating larger communities will be untenable without them.
Hopefully 3 will do a better job of syncing, I had so many sync issues with 2 that I switched to Todoist.
Their tagline "Mother knows everything" is terrifying.
In a gold rush, it's always best to be the one selling the shovels.
I wonder if this is mostly meant to get consumers' attention and gently nudge them towards paying $40 extra for the 3DS. i.e. "$130 for a Gameboy? That's not bad. well if I pay $40 extra I can get a much nicer one..."
Why is iPhone exclusivity still a Thing? With Android holding 70.4% of the current smartphone marketshare to iOS's 17.8%, it's ridiculous to launch a startup and ignore that large of a potential userbase.
Not only that, an app such as this is only going to truly be successful with the network effect. By shunning so many users you're basically guaranteeing that that will never happen.
Apache is a process- and thread-driven application, but Nginx is event-driven. The practical effect of this design difference is that a small number of Nginx "worker" processes can plow through enormous stacks of requests without waiting on each other and without synchronizing; they just "close their eyes" and eat the proverbial elephant as fast as they can, one bite at a time.Apache, by contrast, approaches large numbers of requests by spinning off more processes to handle them, typically consuming a lot of RAM as it does so. Apache looks at the elephant and thinks about how big it is as it tucks into its meal, and sometimes Apache gets a little anxious about the size of its repast. Nginx, on the other hand, just starts chomping.
The difference is summed up succinctly in a quote by Chris Lea on the Why Use Nginx? page: "Apache is like Microsoft Word, it has a million options but you only need six. Nginx does those six things, and it does five of them 50 times faster than Apache."
Source: http://arstechnica.com/business/2011/11/a-faster-web-server-...
Living in Texas and recently having bought a somewhat nice car, hail is a big concern for me. I have several recipes that monitor the weather.gov feeds of the counties in my area for the word 'hail' -- if it catches instances of that word, it'll send me a SMS.
Example feed: http://alerts.weather.gov/cap/wwaatmget.php?x=TXZ103&y=0
Can't they just be tried in absentia?