Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #197844
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Newsgroups | comp.lang.lisp, comp.lang.c, comp.lang.python |
| Subject | Re: Resources to learn common lisp? |
| Date | 2026-07-31 22:46 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <114j8kl$34k3s$1@dont-email.me> (permalink) |
| References | (16 earlier) <1127cho$34rpg$3@dont-email.me> <112o4aa$cpek$2@dont-email.me> <87jyqdtumj.fsf@gmail.com> <tYQaS.4286$ZjVb.2337@fx12.ams4> <87bjbn2nhs.fsf@safunu.org> |
Cross-posted to 3 groups.
On Fri, 31 Jul 2026 12:21:51 -0300, Anton Antimo wrote: > Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes: > >> The tragedy is not using Common Lisp for everything. > > I loved this bit and I have a feeling you're correct. What a dumb idea. Common Lisp is full of legacy baggage to cater to proprietary pre-POSIX OSes which are now extinct. Python can offer basic facilities like these in its standard library: <https://docs.python.org/3/library/subprocess.html> <https://docs.python.org/3/library/select.html>; where are the Common Lisp equivalents?
Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-31 22:46 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-01 09:08 +0000
Re: Resources to learn common lisp? Paul <nospam@needed.invalid> - 2026-08-01 07:49 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-01 23:37 +0000
Re: Resources to learn common lisp? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-08-01 16:54 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-02 07:39 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-04 22:39 -0400
csiph-web