What is this, a crossover episode?

  • kibiz0r
    link
    fedilink
    English
    arrow-up
    10
    ·
    23 小时前

    It’s the problem, but also the strength. That fragmentation allows room to experiment.

    It also puts pressure on the underlying protocols/specs to be air-tight. If you have just one implementation to support, you can do whatever. If you have to support 15, all with different goals and constraints, you gotta be pretty damn careful.

    So in the end, we get foundational systems that are able to evolve over time instead of needing a breaking-change, ground-up rewrite every 2 years.