3 ms·
To me the Stdlib API looks unfixable. So imho there's only one way: * put the existing stdlib into a legacy gem * create a new stdlib with a new, good, (inc
by rmoriz 16y ago
To me the Stdlib API looks unfixable. So imho there's only one way:
* put the existing stdlib into a legacy gem
* create a new stdlib with a new, good, (incompatible) API from scratch
* deal with the incompatibilities that will happen
- bobbywilson0 16y agoI am not opposed to your solution, but sadly, I think it would be an extremely rare case. The ruby core team is very conservative with change, and I don't see some sweeping stdlib switch happening. James Edward Gray II was successful with ousting CSV for his improved implementation, and I think that's probably the way it will happen, if anything does happen. One library at a time.
- vorador 16y agoThis article should be of interest to you (it's about rewriting from scratch) : http://www.joelonsoftware.com/articles/fog0000000069.html http://www.joelonsoftware.com/articles/fog0000000069.html