1,407 karma · joined November 9, 2010
To reach me: contact.ycombinator [at] tomyrealemail [dot] com And yes the domain for the email above is ‘tomyrealemail.com’; it is not a mistake.
This is why the VP of MobileMe was let go soon after: he came from Microsoft/Starbucks, and did surround himself with various ex-microsoft folks.
If you know folks at Apple that were in that group at the time, you will find out that the failure did happen at the VP/Director level that didn't want to listen to the project managers / engineering leads / QA leads.
Basically the summary for iOS is really the push is received by the notification center -own by Apple, and your app has no access to it when it run. Technically too if you go in the iOS settings and decide to remove the app from the Notification Center screen, then the pushes start to be 'lost'.
The concept of push is good and iOS now are better than in the past but they are far from being perfect and the iOS settings screen is a mess/confusion when you start playing with it.
It is always a trade off when you are relying on API: on one side you can focus solely on the project core values knowing that the underlying data will be provided, on the other side if you build everything including what an API provides you are ending building up a different business.
Not associated to that site, simply got a few existing templates a few months back when there was a super promo discount.
Over the last year CloudFront charges did increase but still reasonable (in the $50 range usually). Since the users of my app are all around the world having a solid CDN was key, but what made me decide to stick with CloudFront was all the third party API/client lib.
If someone can point out another good CDN with good API/client lib (python/java) that can make me reconsider my current CloudFront usage.
Glad that the Mayan came up with the end of the world! That made my day!
Apple moved away from different binaries per platform by switching everything to Java which solve the portability question, and additionally solved the database connectivity issues since by bring a java solution any JDBC driver available to talk to a DB will work with WebObjects.
Overall the move to java was a good move, but Apple stopped the investment in the software that NeXT created and went back to focus on desktop and devices... But they kept WebObjects internally for their own benefits I think.
Sadly Apple stopped the development of that web solutions years ago and kept it for itself... I heard from various folks at Apple that there are still a few engineers improving it and it is being used a lot for iTunes. WebObjects got some bad reputation from many people that have no clue on how it works and citing that WebObjects can't even support database update and this why the Apple Online Store is often offline when Apple release a new product. This is total BS of course, since take the iTunes AppStore which serve the content for all stores: music, apps, books, movies, etc... And you barely see that iTunes Store is offline.
WebObjects was a great technology but Apple decided to keep it for itself.
Since then I had one bad HD crash and I was happy to be able to restore from CrashPlan... After a little bit over a day of syncing the restore was complete and I lost only around the last 10 minutes of my work which is not bad at all.
So happy customer here for over 2 years now, and I have already extended my subscription by one more year at regular price.
So I am extremely curious to know the license behind this tts-api? Can the OP provide such info or provide some of the tech behind it?
Doing a quick Whois for nodejs.org show that the name is expiring today:
Domain ID:D157222203-LROR
Domain Name:NODEJS.ORG
Created On:29-Sep-2009 14:50:55 UTC
Last Updated On:20-Sep-2011 00:04:23 UTC
Expiration Date:29-Sep-2012 14:50:55 UTC
Sponsoring Registrar:eNom, Inc. (R39-LROR)
Status:OK
Ouch!