4 ms·
You don't need to support multiple implementations when writing a library when there's only one Whereas to ignore CL & stick to SBCL will be working to fractur
by __s 9y ago
You don't need to support multiple implementations when writing a library when there's only one
Whereas to ignore CL & stick to SBCL will be working to fracture the community-- perhaps necessary, but CL is already a niche community
- sigjuice 9y agoIf Julia gets more popular, it is very likely that other Julia implementations will get developed.
- int_19h 9y agoNot necessarily. R doesn't have other implementations, for example, and Julia still has some way to go before it catches up with R popularity-wise. Or consider Python - it does have several implementations, but the vast majority of the ecosystem is centered around one, and many libraries don't work on the others in practice (especially anything written in other languages using the extensibility API).
- ACow_Adonis 9y agoWell, technically it can be argued that R is itself an implementation (of the language S). It's just that the alternative implementation has become defacto and replaced the original...
- kgwgk 9y agoThere are other R implementations, see https://radfordneal.wordpress.com/2013/07/24/deferred-evaluation-in-renjin-riposte-and-pqr/ https://radfordneal.wordpress.com/2013/07/24/deferred-evalua... for some pointers.
- int_19h 9y agoHow many of these are used in production?
- flavio81 9y ago>will be working to fracture the community-- The CL community knows one uses the implementation one needs. Lispers are using ECL whenever they need to embed with C code, ABCL to interact with JVM, CCL when they're with macs, this is not fragmentation at all, they are all compatible with the CL stanfard.