3 ms·
> So the statement "libraries...do not exist in the Lisp ecosystem" is plainly false and it marks the speaker as someone not very familiar with Lisp. Sorry to
by tralarpa 5y ago
> So the statement "libraries...do not exist in the Lisp ecosystem" is plainly false and it marks the speaker as someone not very familiar with Lisp.
Sorry to be so blunt but this is ridiculous. You are mentioning hash tables and multithreading to prove your point. I am pretty sure this is not what parent meant when they wrote "The ecosystem is just not there". And what does "writing your own libraries because it's so easy to do" even mean? You still have to do it and it takes a lot of time and money. A library that talks a specific protocol to a medical devices. A library that writes some obscure data format used by some government somewhere on earth. This is the real world.
- andi999 5y agoWriting your own library also has the disadvantage that 100% of the new hires have never seen how to use that library.
- jhgb 5y agoAs opposed to "a library that talks a specific protocol to a medical devices" or "a library that writes some obscure data format used by some government somewhere on earth" which new hires wouldn't know how to use either because only a hundred people on Earth have ever used either of those?
- andi999 5y agoActually yes. While there are a lot of different medical devices if you have an engineer who worked with that specific device before (not unlikely if you hire for that) will most likely have worked with the vendor library, but not with yours.
- jhgb 5y agoIn that case, should you choose to write your application in Lisp for whatever reason, it's very likely that you'd be able to use that library from Lisp with a more-or-less isomorphic API and recycle that knowledge.