Hacker Newsnew | past | comments | ask | show | jobs | submit | mbdev's commentslogin

All of it is because investment in Q4 of last year was lower than any Q after 2012.

Which is a ridicules reason given that Q3 was by far the highest ever.

With that being said given the state of the public market (going down + low dividends) startups will still look sexy for a long time. I wouldn't worry about it.


"With that being said given the state of the public market (going down + low dividends) startups will still look sexy for a long time. I wouldn't worry about it."

This is such a ridiculous comment that it needs to be highlighted for just how myopic it really is.

Angel-and-after VC investment has been driven, increasingly, by the effects of ZIRP. "Fuck it, we don't have anywhere else to put our money, we might as well gamble on 23 red" is basically the prime justification for a lot of money that's been put into, say, companies that deliver lunches in San Francisco.

Now that we are moving away from ZIRP, sinking money into glorified AWS-React-Node applications is going to dry up, naturally. There are huge institutional investors who will no longer be willing to take the risk, period.

The "state of the public market" is getting hammered by oil prices, and by China. I don't know how you read that as "startups will still look sexy". The roulette table looks sexy when the bank isn't giving your savings account any return. The moment it does, guess what happens.


Meanwhile, the stock market has been giving returns of 20% per year for the last couple of years. It's been crazy. And corporate bonds typically yield 5%. Savers don't need to care about what the interest rate is. The people who care are the people who lend to invest, for whom low interest rates means increasingly risky stuff is profitable.


I agree 100% with your analysis long-term, however it seems unlikely that interest rates will rise for the foreseeable future.


> it seems unlikely that interest rates will rise for the foreseeable future

Based on the past two weeks of the stock market? I'm not so sure. A choppy stock market may certainly slow down the Fed's plans for 2016, but Yellen seems hellbent on getting away from ZIRP (and the aforementioned weirdness it creates, like pension funds investing heavily in CRUD apps) before the end of this business cycle. If she doesn't, she's reliant on Congress to prop up the economy whenever it inevitably enters a recession, and given Congress's recent track record I doubt that's a gamble she wants to take.


This is actually not an issue at all, because even with native apps you can still load content from the web which apple has no control over, which is similar to Alexa.

But the big deal that no one talks about is that Alexa is not compatible with EC2 backends, this is the most bizarre limitation I've ever seen, you can host An Alexa app on your own PC at home, but not on EC2.


> Alexa is not compatible with EC2 backends

Source on this? I know last time I played with it, they weren't doing SNI (in 2015, what?) but I've never heard of it not being able to hit EC2 IPs.


I had weeks longs mail conversation with the support and engineering team there.

And at the end they gave up and said that yeah its something deep in the implementation and I should use something else.

I don't want to post the mails but anyone can try it out !


This is incorrect - you can absolutely host in EC2. Our two skills are running off of a single EC2 micro instance.

There is one really weird thing where you can't use US West to do an Amazon Lambda passthrough to your server, but as far as I know EC2 instances in any region should work for Alexa to call out to.


I'm sure that the issue can be fixed so it might have been.

But I have the mail conversation here (10 people at least and dozen of back and forth).

This was 2 months ago and I gave up on it for this specific reason.


Man, that's weird, I wonder what was different between our implementations. Our original POCs were about 4 months ago, and they were on EC2 at the time. We had plenty of other technical issues (don't get me started on SSL), but running on EC2 was never one of them.

That said, I'm curious how you managed to get an email conversation going with the team - the whole crux of the original article by Lawrence (and the forum thread which it cites) is that there's no way to have a direct conversation with anyone representing Alexa, so certification is a crapshoot.


I knew someone working at Amazon. That is why I'm reluctant to show the conversation or be more public about it at that time


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: