1. 2

    The advancements are very real and are definitely going to shake up the economy. However, the article is exactly right in pointing out that the narrative of powerlessness and inevitability play to the god-like fantasies of Silicon Valley chatter. Predicting the outcome isn’t easy – look at digital music – but there are many many futures to choose from.

    1. 4

      The major issue not addressed is deployment. This is where the benefits of a monorepo really kick in, but where most deployment systems break down. For example, say your system has 4 services, and they communicate with structures defined in a well defined location in the repo. Great, now you can change the data structure, and all the services that use it can be changed, compiled and tested all at once. Now, imagine that the change only affects 2 services, you want a way to deploy only those two services, simultaneously and safely, so that an old version of service1 never talks to a new version of service2. That’s a bit of a headache.

      1. 1

        I don’t see why this is a headache in a way unique to monorepos.

      1. 2

        Pretty cool. This contradicts a recent assertion made by ESR http://esr.ibiblio.org/?p=8223

        1. 2

          That assertion inspired my search. When people say it’s impossible, I start DuckDuckGoing for terms that might lead to the counter-example. I just typed each thing he said was sequential into search with “parallel” next to it. Found a few things. Here’s another found from that search.

          As side effect, you can tell he wasn’t fact checking those statements before publishing them. ;)