Ask HN: Git, JavaScript, Chrome, Redis etc. what next?
11–15 of 15 posts
Re: Ask HN: Git, JavaScript, Chrome, Redis etc. what next?
#12* Generally rebuilds everything from scratch, which get slow on large projects. Reducing overbuilding requires lots of manual work. * Hard to test, often you have to push a commit. * No flakey test detection and management.
There are some companies working on productionizing Bazel-based CI systems, like BuildBuddy, but there might be other ways of approaching this problem.
Re: Ask HN: Git, JavaScript, Chrome, Redis etc. what next?
#13Then you're not looking deep enough at problems that people have or you haven't been in the field long enough. There are tons of issues out there, and I wish I had a department full of me's who could work on all of the problems I want solutions to.
I wish I were a multi-millionaire so that I could hire programmers to help me build all of the things that I believe should exist in the world!
Re: Ask HN: Git, JavaScript, Chrome, Redis etc. what next?
#14Look at the products from startups accepted into YC. Few (if any) haven't been done before and the same goes for most open source. Your goal should be to identify something that the others missed.
Re: Ask HN: Git, JavaScript, Chrome, Redis etc. what next?
#15each of these tools have varying use cases and varying companies that use them into different industries.