It's actually both, and a file system.
1,054 karma · joined November 21, 2014
That's really interesting, I'd love to hear how people overcome similar problems.
isn't that true for any CP store in any "cloud" provider?
They simply used what they knew best:
> If step one had been "learn the GCC or LLVM toolchains well enough to add segmented stacks", I'm not sure we'd have gotten to step two.
> Honestly, if we'd built on GCC or LLVM, we'd be moving so slowly I'd probably have left the project years ago.
It has an very long way ahead to catch up with Lucene, but it's a very promising start.
Also remember that while not very widely used, Go does provide support against this problems via custom URLs and canonical import paths [0].
And most importantly, whatever your programming language, remember to vendor your dependencies.
[0] https://texlution.com/post/golang-canonical-import-paths/
Really? have you never seen unix pipes?
Those are mostly neutrino detectors https://en.wikipedia.org/wiki/Neutrino_detector
That could not have been more graphically enlightening.
Chaining does work, but obviously the function needs the same signature as the return values, which limits things since most APIs don't accept errors as input. But within your code you can structure it to get error values for things you know you will be chaining. Or create wrappers to make your types chainable.