News for hackers. Stuff that matters.
Re:Switching from Common Lisp to Julia (2017) by rauhl on Monday August 05, 2019 @12:57PM (#20615733)
I absolutely love developing in Common Lisp, and I agree with you.

Some suggestions:

- Get rid of upcasing; 21st-century languages should be case-sensitive and case-preserving. Allegro’s modern mode is the Right Thing™ here IMHO.

- Fix things like order-of-argument inconsistencies in the standard library.

- Consider adding type to streams to indicate whether they are input, output or both and character, byte or both.

- Base the package system off of Go’s.

- More fully specify pathnames.

- Specify a standard library roughly equivalent to Go’s. At this point I think it’s the gold standard (Python’s used to be, but no longer).

Re:Switching from Common Lisp to Julia (2017) by vindarel on Monday August 05, 2019 @01:46PM (#20616336)
On upcasing:

    (setf *print-case* :downcase)
Re:Switching from Common Lisp to Julia (2017) by rauhl on Monday August 05, 2019 @01:49PM (#20616364)
Oh definitely — that is a must! But it doesn’t do you any good if e.g. you want to turn read symbols into shell commands. You can play some games with :invert, but at the end of the day it’s a hack.

I don’t blame them for upcasing back in the 90s, but … it’s not the 90s anymore.

Re:Switching from Common Lisp to Julia (2017) by rurban on Tuesday August 06, 2019 @06:07PM (#20630166)
Not downcase, modern. I.e case-preserving and case-sensitive. E.g. to be able to define native ffi calls into CamelCase functions. Downcasing is destroying information, Modern is keeping the original symbol names