Click-bait speculation. Word in the industry was that after two failed attempts to move from AWS to Facebooks metal failed spectacularly and massive attrition after vesting -- no one was left to make it work and Facebook lost the will to keep going. The more important lesson was that a failure to port a stack from AWS to FB servers caused Facebook to take a $1B write-down. Startups should reconsider their metal, as f…
Discouraging startups from using AWS is so strange, I had to look at your bio. A Googler eh. Perhaps you have some ulterior motive to encourage people to avoid the AWS stack, which is clearly becoming the infrastructure of choice for this generation of startups?
>Can you trust your platform of choice, or will they close shop on you tomorrow? I'm thinking about moving to IBM BlueMix with parts of my business and asking myself the same question. What do you guys think? Will BlueMix still be there in a couple of years (3,4)? I know nobody using it, but IBM is promoting it quite aggressively, and it makes sense for me to have an alternative for both self-made AWS clusters (IaaS)…
It will be around, for sure. But it will also be so expensive it might as well not be.
For what it's worth (and because someone said they were "hoping for an insider leak"), here's what a genuine insider had to say about this article: Just awful. followed by: I would write something but it would be so simplistic that nobody would believe it. Sorry it's anonymous, but it's the best I could squeeze out of them :)
Click-bait speculation. Word in the industry was that after two failed attempts to move from AWS to Facebooks metal failed spectacularly and massive attrition after vesting -- no one was left to make it work and Facebook lost the will to keep going. The more important lesson was that a failure to port a stack from AWS to FB servers caused Facebook to take a $1B write-down. Startups should reconsider their metal, as f…
Discouraging startups from using AWS is so strange, I had to look at your bio. A Googler eh. Perhaps you have some ulterior motive to encourage people to avoid the AWS stack, which is clearly becoming the infrastructure of choice for this generation of startups?
Attacking his integrity seems kind of uncalled for.
Parse never made sense to me. I could see a service like Parse being useful, but it would need to be owned / operated by a nonprofit in order to gain any adoption. Otherwise, it's just another proprietary platform that will get shut off or changed once Facebook (or whoever) pivots to another business model to address that market. There's certainly demand, but I think most developers are wary about putting their compa…
It didn't make sense to me until I had a.) started a company and b.) saw the historical tech stacks of a number of companies (eg. Google, Facebook, EBay) that had hit it big. I started my career with the belief that your company has one tech stack, the chief architect chooses it when the company is founded, and that you never ever rewrite it because you're in for a world of pain if you do. I learned that basically no…
This is frankly the best tech industry tech stack cycle explanation I've ever seen lol.
I've thought this myself but never put the words together so clearly
The "2-4 official languages" dictum is usually put in place after the company churns through those 2-4 languages in the first 2-4 years of its existence. Basically everybody realizes how costly it is and says "no more". At least that's how it was at Google, which is perhaps the most famous example of the "We have 4 official languages, and you're not introducing a new one" policy. I've worked in startups that tried to…
> Google, which is perhaps the most famous example of the "We have 4 official languages, and you're not introducing a new one" policy I believe those 4 languages were Java, C++, Javascript, and Python. Nowadays they also use Go, Dart, Groovy (in Android Studio), and I guess a lot more. (When I say Groovy, I mean the tiny non-Turing Complete subset of the syntax used as a DSL in typical Gradle build scripts.)
It's technically C++, Java, Python, and Go. There's always been an exception for client-side code (which encompasses Javascript on the web and Objective-C for iOS apps), and for DSLs (which includes Sawzall, Protobufs, Bazel, Gradle, and several that I don't believe are public. Haskell was also used as a DSL by one team, though their product unfortunately got canceled).
Click-bait speculation. Word in the industry was that after two failed attempts to move from AWS to Facebooks metal failed spectacularly and massive attrition after vesting -- no one was left to make it work and Facebook lost the will to keep going. The more important lesson was that a failure to port a stack from AWS to FB servers caused Facebook to take a $1B write-down. Startups should reconsider their metal, as f…
Discouraging startups from using AWS is so strange, I had to look at your bio. A Googler eh. Perhaps you have some ulterior motive to encourage people to avoid the AWS stack, which is clearly becoming the infrastructure of choice for this generation of startups?
Well in all humility, I know a lot less about this than you.
Yeah, it sucks Parse shut down. But that's not an argument to avoid SaaS. My startup is built on over 20+ different third-party tools. It will really, really suck if any of them shut down... but I'd rather deal with that possibility in the future when we have more money and time, than struggle to build everything out ourselves now. Like I said, it sucks Parse is shutting down. But in ~2 hours, you can get the open so…
> in ~2 hours, you can get the open source Parse clone they released going and be back to new I keep hearing this, and I have a hard time believing it. Are there any examples of a significant app/developer doing this? Sure a working Parse Server is easy to get up and running, but the reason someone wouold choose Parse was to avoid operations, and that's not a service you build in your company in 2 hrs. (as an aside,…
There's quite a few pieces missing from the open source Parse server. https://parse.com/docs/server/guide#migrating
Analytics, Push (a big one), Config, Jobs.
I've been building a mobile app platform on Parse for a while, so I'll have to re-build all the missing pieces for all my existing customers and to keep the new customers coming in. Its something I'd been planning/researching for a while for the next version anyway, the number of times I've said fcuk Parse! Now I have to hurry up and build the next Parse anyway at http://appstack.systems