nate_martin

>The first problem every startup solves is scalability.

I don't think this is true at all. The first problem they solve is typically finding product market fit, which startups will do by sacrificing scalability and quality for speed of execution.

>The compiler itself is to be developed in OCaml.

These seems like a misstep that I've seen in a few other compiler implementation courses. For some reason these programming language professors always insist on completing the project in their personal favorite language (Haskell, OCaml, Standard ML, etc).

As a student this makes the project significantly more difficult. Instead of just learning how to implement a complier, you're also learning a new (and likely difficult) programming language.

It takes energy to remove carbon from the atmosphere. With abundant energy from fusion you could just remove the carbon added by humans.

Compared to Netflix and even YouTube, TikTok has an extremely tight dopamine feedback loop. Any buffering of a video after a scroll event could result in the user's attention being lost and the session ending. My guess is that they've spent a lot of time optimizing video load because of how correlated with their revenue it is. For Netflix doing this optimization might not be worth the increased infrastructure cost.

Crypto soaks up excess liquidity like a sponge.

This looks really cool, but I'm a little bit confused about why this needs to be decentralized. You could theoretically just implement this network as a saas instead of on top of a blockchain. You could even still do all the financials with ether but just maintain the state on servers somewhere.

The big fear I have is immutability of blockchain data in the case that something goes horribly wrong. If there's a problem with the ethereum core protocol, solidity compiler, wallet software, colony contracts you could lose everything. Vitalik already said that there probably wouldn't be anymore hard forks.

It's a little annoying when companies put framework names in their job titles. Asking for a "react engineer" or a "boost programmer" will likely turn away a lot of people who would actually be a good fit for the role. My suggestion is to just be open with the company and tell them what you do know and how quickly you can get up to speed. Something like: "I haven't used React on a paid project before, but I have a lot of experience with other frontend frameworks like x/y."

The online matches only allowed 30 seconds per move.

People have wildly different experiences there. Some hate it and burn out after a year. Others really like the work environment and get promoted quickly.

One good thing I'll say about Amazon is that it's a great way to break into the "big four" tech companies. If you didn't get into Google or Facebook initially but got into Amazon you can pretty much guarantee you'll get recruiter spam from lots of top companies.

Might be smart to remove their logo from your site. I would expect a cease and desist if this gets popular.

For someone familiar with the products, yes. But for someone new to AWS most of these options don't make sense. I'm looking at a menu with hundreds of options like Snowglobe and Beanstalk and I have no idea where to start. Are they trying to brand their trademarks as the defacto name for the service (like Kleenex and ChapStick have done)?

So many new named services. AWS will soon get to a point where their product dropdown wont fit on a laptop screen. Maybe it's time to consolidate some of these services into more general products.

This doesn't address the root comment at all. Does Amazon actually think MXNet is the best? Or did they simply choose the next best thing that isn't already backed by another "big four" company (Google -> TensorFlow, Facebook -> Torch). It's hard to believe this is actually about scalability without any data.