4 ms·
This is very sound advice. That being said it's incredibly hard to follow this advice in environments which encourage a polyglot stack and 'the best tool for t
by sid6376 6y ago
This is very sound advice.
That being said it's incredibly hard to follow this advice in environments which encourage a polyglot stack and 'the best tool for the job' mindset. The moment you have more than one language in your stack it becomes easier to build services than to maintain libraries in each language. You can of course write native C libraries with bindings to different languages but that's a bit weird.
It's also requires more discipline to maintain abstractions and boundaries properly with libraries in large code bases but that's another story.
- inter_netuser 6y agowhy weird? It also doesn't have to be C, just anything that compiles to a native binary lib.
- pedro2 6y agoNot everyone's cup of tea, but on Linux gobject-introspection allows for automatic or semi-automatic generation of bindings for X languages. .NET also -- and this is only my interpretation -- is following that path.
- viferga 6y agoI also think it's the way to go: https://github.com/metacall/core https://github.com/metacall/core