Thread

1. octoberfranklin · 1789787510 · focus · HN ↗

   Enter hell: LSP assumes that it's the source of truth, but you still need to access the filesystem yourself, and do it in a synchronized way

   LSP is an example of utterly horrid technical design.

   Stop letting Microsoft design protocols and APIs. They are so. bad. at. it.

   1. duttish · 1789787613 · focus · HN ↗

      I've never looked into LSP, how would you design it?

      1. mitxela · 1789787730 · focus · HN ↗

         Start with synchronous function calls instead of JSON. Microsoft knows how to do that - they invented COM and OLE. Function calls enable whatever data sharing is necessary to maintain a coherent view. Imagine trying to do OLE with JSON - just wouldn't work. (Does OLE still exist?)

         1. cyberax · 1789789000 · focus · HN ↗

            Stupid idea.

            So the LSP crashes and/or goes into a runaway memory consumption loop. And your main application dies with it.

            Or what if you want, you know, to be able to use the same LSP from TWO different applications at the same time?

            Never mind issues with other managed runtimes not expecting to deal with something else in their address space.

Unofficial Hacker News client; not affiliated with Y Combinator.