Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #77092 > unrolled thread
| Started by | c186282 <c186282@nnada.net> |
|---|---|
| First post | 2025-11-08 02:01 -0500 |
| Last post | 2025-11-09 19:08 +0000 |
| Articles | 20 on this page of 308 — 33 participants |
Back to article view | Back to comp.os.linux.misc
Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-08 02:01 -0500
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-08 11:31 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-08 12:15 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-08 13:32 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-09 00:08 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-09 19:51 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 00:38 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 07:35 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-08 12:50 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-08 12:57 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-08 23:58 -0500
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-09 11:25 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-09 12:48 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-09 23:29 -0500
Re: Python/C/Pascal ... How To Choose ? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-11-09 09:18 -0800
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-09 20:13 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 07:47 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-10 12:09 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 20:35 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-10 21:15 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-10 23:33 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 03:23 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 01:03 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-11 10:57 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:36 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-11 20:50 +0100
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-11 23:44 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:38 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-12 20:44 +0000
Re: Python/C/Pascal ... How To Choose ? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-11-12 16:38 -0800
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-13 04:29 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-13 05:07 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 01:09 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:42 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:37 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:46 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 05:31 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-12 06:00 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 02:08 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:55 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:30 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:56 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:54 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:17 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-13 10:38 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-12 12:20 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:50 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 03:18 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 00:54 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:28 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-11 23:25 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 04:35 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:49 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:49 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:31 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-12 20:44 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:33 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-11 21:07 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:21 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-12 20:44 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:13 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-13 05:40 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 01:20 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-10 23:31 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 03:39 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-10 19:48 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-10 20:35 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-10 21:53 +0100
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 20:37 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 23:51 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:40 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-11 23:01 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 04:33 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-12 12:27 +0100
Re: Python/C/Pascal ... How To Choose ? Andy Burns <usenet@andyburns.uk> - 2025-11-12 12:44 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-12 14:17 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:51 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-13 22:38 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 21:30 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-14 04:21 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 07:10 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 02:51 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 07:08 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 13:40 +0100
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-14 16:26 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 19:51 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 19:22 -0500
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-14 17:34 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 19:54 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 13:37 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 16:09 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-15 02:05 +0000
Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-15 09:59 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-15 17:32 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-15 18:48 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-15 21:38 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Eli the Bearded <*@eli.users.panix.com> - 2025-11-15 22:07 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-15 22:21 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Eli the Bearded <*@eli.users.panix.com> - 2025-11-15 23:14 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 00:29 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Eli the Bearded <*@eli.users.panix.com> - 2025-11-16 00:43 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 00:45 +0000
Re: Recent history of vi Pancho <Pancho.Jones@protonmail.com> - 2025-11-16 09:14 +0000
Re: Recent history of vi mechanicjay@sol.smbfc.net (Mechanicjay) - 2025-11-16 15:40 +0000
Re: Recent history of vi Joe Makowiec <makowiec@invalid.invalid> - 2025-11-16 18:38 +0000
Re: Recent history of vi mechanicjay@sol.smbfc.net (Mechanicjay) - 2025-11-18 03:55 +0000
Re: Recent history of vi Joe Makowiec <makowiec@invalid.invalid> - 2025-11-19 13:11 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-19 20:12 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 19:10 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 21:01 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose?) rbowman <bowman@montana.com> - 2025-11-16 03:43 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-16 09:35 -0500
Re: Recent history of vi mechanicjay@sol.smbfc.net (Mechanicjay) - 2025-11-16 15:47 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 05:15 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-16 19:31 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 20:27 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-16 20:30 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 21:04 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-17 04:08 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-17 11:39 -0500
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-16 09:31 -0500
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 19:03 +0000
Re: Recent history of vi Eli the Bearded <*@eli.users.panix.com> - 2025-11-17 02:32 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-15 21:51 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 05:11 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 05:13 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-11-16 12:15 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-16 19:24 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-11-17 08:24 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-17 19:57 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-11-18 08:02 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-18 12:09 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 20:56 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) rbowman <bowman@montana.com> - 2025-11-17 04:01 +0000
Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> - 2025-11-17 08:27 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-16 10:33 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-16 09:49 -0500
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 19:28 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 20:19 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 20:59 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 21:04 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 21:19 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 21:23 +0000
Re: Recent history of vi Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-16 23:13 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-16 23:18 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-17 00:43 +0000
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-21 19:55 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-21 20:27 +0000
Re: Recent history of vi Eli the Bearded <*@eli.users.panix.com> - 2025-11-22 03:20 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-22 05:57 +0000
Re: Recent history of vi Niklas Karlsson <nikke.karlsson@gmail.com> - 2025-11-16 23:51 +0000
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-11-18 20:04 +0100
Re: Recent history of vi Eli the Bearded <*@eli.users.panix.com> - 2025-11-18 20:29 +0000
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-11-19 08:24 +0000
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-21 19:58 +0000
Re: Recent history of vi Niklas Karlsson <nikke.karlsson@gmail.com> - 2025-11-21 21:14 +0000
ISO 8859-1, ISO 8859-15 and their names (was: Re: Recent history of vi) Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-21 23:20 +0000
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-11-21 19:10 -0700
Re: Recent history of vi Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-22 10:23 +0000
Re: Recent history of vi Johnny Billquist <bqt@softjar.se> - 2025-11-22 17:55 +0100
Re: Recent history of vi Alexander Schreiber <als@usenet.thangorodrim.de> - 2025-11-22 19:20 +0100
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-22 21:43 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-11-23 00:23 +0100
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-23 02:17 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-23 09:42 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-11-23 14:59 +0100
Re: Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-11-23 13:09 -0800
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-23 22:57 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-23 02:56 +0000
Re: Recent history of vi Peter Flass <Peter@Iron-Spring.com> - 2025-11-22 20:18 -0700
Re: typing in the mysterious East, Recent history of vi John Levine <johnl@taugh.com> - 2025-11-24 01:45 +0000
Re: typing in the mysterious East, Recent history of vi Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-11-23 18:06 -0800
Re: typing in the mysterious East, Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-24 02:13 +0000
Re: typing in the mysterious East, Recent history of vi John Levine <johnl@taugh.com> - 2025-11-24 02:23 +0000
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-11-22 20:25 +0100
Re: Recent history of vi "Carlos E.R." <robin_listas@es.invalid> - 2025-11-19 02:37 +0100
ISO 8859-1 ("Latin 1") (was: Recent history of vi) Michael Bäuerle <michael.baeuerle@stz-e.de> - 2025-11-19 14:58 +0100
Re: ISO 8859-1 ("Latin 1") (was: Recent history of vi) Eli the Bearded <*@eli.users.panix.com> - 2025-11-20 02:09 +0000
Re: ISO 8859-1 ("Latin 1") Peter Flass <Peter@Iron-Spring.com> - 2025-11-19 20:16 -0700
Re: ISO 8859-1 ("Latin 1") Richard Kettlewell <invalid@invalid.invalid> - 2025-11-20 08:47 +0000
Re: ISO 8859-1 ("Latin 1") The Natural Philosopher <tnp@invalid.invalid> - 2025-11-20 11:10 +0000
Re: ISO 8859-1 ("Latin 1") Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-20 17:57 +0000
Re: ISO 8859-1 ("Latin 1") Ralf Fassel <ralfixx@gmx.de> - 2025-11-21 12:24 +0100
Re: Recent history of vi Eric Pozharski <apple.universe@posteo.net> - 2025-11-19 13:02 +0000
Re: Recent history of vi antispam@fricas.org (Waldek Hebisch) - 2025-11-23 16:25 +0000
Re: Recent history of vi Anthk NM <anthk@disroot.org> - 2025-11-23 12:48 +0000
Re: Recent history of vi ted@loft.tnolan.com (Ted Nolan <tednolan>) - 2025-11-23 17:51 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-23 20:11 +0000
Re: Recent history of vi The Natural Philosopher <tnp@invalid.invalid> - 2025-11-16 20:26 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-17 11:44 -0500
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-16 20:57 +0000
Re: Recent history of vi antispam@fricas.org (Waldek Hebisch) - 2025-11-15 19:52 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-16 09:50 -0500
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 18:56 +0000
Re: Recent history of vi Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-11-17 11:24 -0500
Re: Recent history of vi Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-16 00:43 +0000
Re: Recent history of vi rbowman <bowman@montana.com> - 2025-11-16 03:20 +0000
Re: Recent history of vi Richard Kettlewell <invalid@invalid.invalid> - 2025-11-16 16:14 +0000
Re: Recent history of vi scott@slp53.sl.home (Scott Lurndal) - 2025-11-17 19:39 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:24 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 19:41 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:00 -0500
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-13 10:56 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 21:25 -0500
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-14 04:21 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 23:40 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-14 07:05 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 02:48 -0500
Re: Python/C/Pascal ... How To Choose ? Rich <rich@example.invalid> - 2025-11-16 03:53 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 13:45 +0100
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-14 19:29 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-14 10:22 +0000
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-14 10:35 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 15:55 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-15 02:07 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 15:47 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:36 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 20:04 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-10 08:57 +0100
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-10 08:13 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 20:50 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 21:01 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-10 22:40 +0100
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-10 23:14 +0100
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-10 22:21 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-11 00:21 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 00:43 -0500
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-11 00:35 +0000
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-11 01:40 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 00:48 -0500
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-11 08:53 +0000
Re: Python/C/Pascal ... How To Choose ? Farley Flud <fsquared@fsquared.linux> - 2025-11-11 11:42 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:25 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:21 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:56 +0000
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-11 08:38 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 19:43 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:43 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:50 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:11 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-13 10:24 +0000
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-12 16:22 +0000
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-11 10:59 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-11 17:14 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-11 23:28 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-12 10:48 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-12 11:20 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:31 -0500
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:08 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-13 10:22 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-10 09:05 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 00:29 -0500
Re: Python/C/Pascal ... How To Choose ? Farley Flud <fsquared@fsquared.linux> - 2025-11-10 11:56 +0000
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-10 22:23 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-10 22:38 +0000
Re: Python/C/Pascal ... How To Choose ? Pancho <Pancho.Jones@protonmail.com> - 2025-11-11 00:07 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-13 16:48 +0000
Re: Python/C/Pascal ... How To Choose ? Richard Kettlewell <invalid@invalid.invalid> - 2025-11-10 18:04 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-11 16:52 +0000
Re: Python/C/Pascal ... How To Choose ? Diego Garcia <dg@linux.rocks> - 2025-11-11 20:06 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-11 23:09 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-11 23:31 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 04:50 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-12 06:50 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 20:05 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-15 17:17 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-12 12:35 +0100
Re: Python/C/Pascal ... How To Choose ? Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-12 21:09 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:22 -0500
Re: Python/C/Pascal ... How To Choose ? Stéphane CARPENTIER <sc@fiat-linux.fr> - 2025-11-12 21:06 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 01:30 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-09 19:28 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 00:36 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-10 07:46 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-10 23:22 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-11 20:16 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 00:08 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 19:58 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-12 07:21 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 02:26 -0500
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-12 08:35 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 20:29 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 23:07 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-13 04:59 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 00:57 -0500
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-13 10:19 +0000
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-13 20:16 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 21:17 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 01:54 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-13 21:33 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 14:04 +0100
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 16:27 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-14 22:44 +0100
Re: Python/C/Pascal ... How To Choose ? Andy Burns <usenet@andyburns.uk> - 2025-11-14 13:24 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-14 17:03 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-12 20:10 +0000
Re: Python/C/Pascal ... How To Choose ? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-11 21:07 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-12 00:56 -0500
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-08 13:28 +0100
Re: Python/C/Pascal ... How To Choose ? The Natural Philosopher <tnp@invalid.invalid> - 2025-11-08 12:45 +0000
Re: Python/C/Pascal ... How To Choose ? "Carlos E.R." <robin_listas@es.invalid> - 2025-11-08 14:35 +0100
Re: Python/C/Pascal ... How To Choose ? Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-08 22:15 +0000
Re: Python/C/Pascal ... How To Choose ? c186282 <c186282@nnada.net> - 2025-11-09 00:28 -0500
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-08 20:29 +0000
Re: Python/C/Pascal ... How To Choose ? vallor <vallor@vallor.earth> - 2025-11-09 01:11 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-09 02:37 +0000
Re: Python/C/Pascal ... How To Choose ? Nuno Silva <nunojsilva@invalid.invalid> - 2025-11-09 09:11 +0000
Re: Python/C/Pascal ... How To Choose ? rbowman <bowman@montana.com> - 2025-11-09 19:08 +0000
Page 1 of 16 [1] 2 3 … 16 Next page →
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-08 02:01 -0500 |
| Subject | Python/C/Pascal ... How To Choose ? |
| Message-ID | <CtydnVqzjrtfd5P0nZ2dnZfqn_adnZ2d@giganews.com> |
I posted recently on a simple video recording pgm that mostly uses ffmpeg to get it done. Re-did the other day, it's really good now. However, just because, I started a 'C' and Pascal version. The ffmpeg command line required is long and complicated. Some literal stuff, some vars. Then I remember that 'C' is a total BASTARD when it comes to strings. Have done complicated 'C' apps that fool with complicated strings - but didn't LIKE it. Pascal is much easier with strings ... easy concats and such. Some of the number->string stuff is a bit weird, but nothing as bad as 'C'. SO ...... I'm going to abandon the 'C' version and make a Free Pascal basic pgm instead. Don't know if it will be simpler/faster right now, but due to the requirements WILL be easier than 'C', and far fewer chances of weird errors. Frankly, at this point, I like Python. Yea, it's interpreted, ergo a bit slow, but it has a LOT of conveniences that make up for that most of the time. Note neither 'C' or FP have a straight-up equiv for 'sleep()'. This is critical to my app. Turbo had something like it ... but it was like a legacy lib and not sure to be as accurate or versatile as Python sleep().
[toc] | [next] | [standalone]
| From | Diego Garcia <dg@linux.rocks> |
|---|---|
| Date | 2025-11-08 11:31 +0000 |
| Message-ID | <pan$6b026$dd2599d1$b6e2fd67$717fe5b4@linux.rocks> |
| In reply to | #77092 |
On Sat, 8 Nov 2025 02:01:12 -0500, c186282 wrote: > > The ffmpeg command line required is long and > complicated. Some literal stuff, some vars. > Then I remember that 'C' is a total BASTARD > when it comes to strings. > > Have done complicated 'C' apps that fool with > complicated strings - but didn't LIKE it. > That's why there are option parsers like "getopt()" or "getopt_long()" from GLIBC. Then there are libraries like "popt:" <https://github.com/rpm-software-management/popt> Digitally speaking, strings are a very unnatural construct and that's why C doesn't deal with them in a "nice" fashion. But then that's what C libraries are for. And that's why incompetent programmers flock to Python.
[toc] | [prev] | [next] | [standalone]
| From | Diego Garcia <dg@linux.rocks> |
|---|---|
| Date | 2025-11-08 12:15 +0000 |
| Message-ID | <pan$2b37a$dfab07b8$f51ffd3a$144f568c@linux.rocks> |
| In reply to | #77098 |
On 8 Nov 2025 12:03:43 GMT, Stefan Ram wrote: > Diego Garcia <dg@linux.rocks> wrote or quoted: >>And that's why incompetent programmers flock to Python. > > If "incompetent programmers" built most of the modern AI, data > science, and automation pipelines using Python - the same language > through which most research and real-world models are prototyped, > trained, and deployed - what does that make everyone else? > Python is written in the C language. What does that tell you?
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-11-08 13:32 +0100 |
| Message-ID | <orp3ulx3s8.ln2@Telcontar.valinor> |
| In reply to | #77106 |
On 2025-11-08 13:15, Diego Garcia wrote: > On 8 Nov 2025 12:03:43 GMT, Stefan Ram wrote: > >> Diego Garcia <dg@linux.rocks> wrote or quoted: >>> And that's why incompetent programmers flock to Python. >> >> If "incompetent programmers" built most of the modern AI, data >> science, and automation pipelines using Python - the same language >> through which most research and real-world models are prototyped, >> trained, and deployed - what does that make everyone else? >> > > Python is written in the C language. > > What does that tell you? Nothing. -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-09 00:08 -0500 |
| Message-ID | <qH6dnXZ6soQtvI30nZ2dnZfqnPednZ2d@giganews.com> |
| In reply to | #77110 |
On 11/8/25 07:32, Carlos E.R. wrote: > On 2025-11-08 13:15, Diego Garcia wrote: >> On 8 Nov 2025 12:03:43 GMT, Stefan Ram wrote: >> >>> Diego Garcia <dg@linux.rocks> wrote or quoted: >>>> And that's why incompetent programmers flock to Python. >>> >>> If "incompetent programmers" built most of the modern AI, data >>> science, and automation pipelines using Python - the same language >>> through which most research and real-world models are prototyped, >>> trained, and deployed - what does that make everyone else? >>> >> >> Python is written in the C language. >> >> What does that tell you? > > Nothing. An idea on how to improve 'C' :-)
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-09 19:51 +0000 |
| Message-ID | <mnc9leF4tpaU2@mid.individual.net> |
| In reply to | #77155 |
On Sun, 9 Nov 2025 00:08:03 -0500, c186282 wrote: > On 11/8/25 07:32, Carlos E.R. wrote: >> On 2025-11-08 13:15, Diego Garcia wrote: >>> On 8 Nov 2025 12:03:43 GMT, Stefan Ram wrote: >>> >>>> Diego Garcia <dg@linux.rocks> wrote or quoted: >>>>> And that's why incompetent programmers flock to Python. >>>> >>>> If "incompetent programmers" built most of the modern AI, data >>>> science, and automation pipelines using Python - the same >>>> language through which most research and real-world models are >>>> prototyped, trained, and deployed - what does that make everyone >>>> else? >>>> >>>> >>> Python is written in the C language. >>> >>> What does that tell you? >> >> Nothing. > > An idea on how to improve 'C' :-) No thanks. 'The C Programming Language' is a thin book and still relevant. Stroustrup's first edition C++ was thicker and has grown. I have an early edition of O'Reilly's 'Java In a Nutshell'. By the 8th edition it needed the mother of all coconut shells to fit the 'improvements'.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-10 00:38 -0500 |
| Message-ID | <-RycnTPdvP3t54z0nZ2dnZfqnPGdnZ2d@giganews.com> |
| In reply to | #77190 |
On 11/9/25 14:51, rbowman wrote: > On Sun, 9 Nov 2025 00:08:03 -0500, c186282 wrote: > >> On 11/8/25 07:32, Carlos E.R. wrote: >>> On 2025-11-08 13:15, Diego Garcia wrote: >>>> On 8 Nov 2025 12:03:43 GMT, Stefan Ram wrote: >>>> >>>>> Diego Garcia <dg@linux.rocks> wrote or quoted: >>>>>> And that's why incompetent programmers flock to Python. >>>>> >>>>> If "incompetent programmers" built most of the modern AI, data >>>>> science, and automation pipelines using Python - the same >>>>> language through which most research and real-world models are >>>>> prototyped, trained, and deployed - what does that make everyone >>>>> else? >>>>> >>>>> >>>> Python is written in the C language. >>>> >>>> What does that tell you? >>> >>> Nothing. >> >> An idea on how to improve 'C' :-) > > No thanks. 'The C Programming Language' is a thin book and still relevant. HAVE it ... and still stick pretty close. > Stroustrup's first edition C++ was thicker and has grown. I have an early > edition of O'Reilly's 'Java In a Nutshell'. By the 8th edition it needed > the mother of all coconut shells to fit the 'improvements'. C++ ... um ... no thanks.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-10 07:35 +0000 |
| Message-ID | <mndit3FbepuU1@mid.individual.net> |
| In reply to | #77229 |
On Mon, 10 Nov 2025 00:38:44 -0500, c186282 wrote: > C++ ... um ... no thanks. Not my favorite but when you're working with a C++ API you hold your nose. Esri prior to 11.x was COM based so it was a dialect of C++ anyway.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-11-08 12:50 +0000 |
| Message-ID | <10enea5$2hkmh$5@dont-email.me> |
| In reply to | #77106 |
On 08/11/2025 12:44, Stefan Ram wrote: > Diego Garcia <dg@linux.rocks> wrote or quoted: >> Python is written in the C language. > > Python is a programming language. Programming languages are not > written in anything. It is programming language /specifications/ > or /implementations/ that are written in some language. > > The specification of Python is written in English. > > There is one implementation of Python written in C indeed, viz., > "CPython". Other implementation are written in Python itself (PyPy, > partially faster than CPython!), Java (Jython), or C# (IronPython). > > So, you got that totally wrong. > > What does that tell you? > > That you have some axe to grind that I am not even interested in discovering the nature of. -- Labour - a bunch of rich people convincing poor people to vote for rich people by telling poor people that "other" rich people are the reason they are poor. Peter Thompson
[toc] | [prev] | [next] | [standalone]
| From | Diego Garcia <dg@linux.rocks> |
|---|---|
| Date | 2025-11-08 12:57 +0000 |
| Message-ID | <pan$d8008$873f42f$d869b130$6e7f97e9@linux.rocks> |
| In reply to | #77106 |
On 8 Nov 2025 12:44:40 GMT, Stefan Ram wrote: > > Python is a programming language. Programming languages are not > written in anything. > Ha, ha, ha, ha, ha, ha, ha, ha! Download the Python source: <https://www.python.org/downloads/source/> What do you find inside the tarballs? There are C source files all over the place. Python is written entirely in the C language. > > So, you got that totally wrong. > > What does that tell you? > It tells me that you are an ignoramus idiot that desperately wants to defend Python because Python defends ignoramus idiots.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-08 23:58 -0500 |
| Message-ID | <qH6dnXd6soTggo30nZ2dnZfqnPednZ2d@giganews.com> |
| In reply to | #77098 |
On 11/8/25 06:31, Diego Garcia wrote: > On Sat, 8 Nov 2025 02:01:12 -0500, c186282 wrote: > >> >> The ffmpeg command line required is long and >> complicated. Some literal stuff, some vars. >> Then I remember that 'C' is a total BASTARD >> when it comes to strings. >> >> Have done complicated 'C' apps that fool with >> complicated strings - but didn't LIKE it. >> > > That's why there are option parsers like "getopt()" > or "getopt_long()" from GLIBC. > > Then there are libraries like "popt:" > > <https://github.com/rpm-software-management/popt> > > Digitally speaking, strings are a very unnatural construct > and that's why C doesn't deal with them in a "nice" fashion. "Unnatural" ??? Nominally just fixed-length records with a variable number of significant bytes. Those go back to the very beginning .... > But then that's what C libraries are for. Not all compilers support the exact same libs alas. Anyway, complex dealings with strings can certainly be done ... but it's the tiny-step by tiny-step aspect that's just damned annoying to use. > And that's why incompetent programmers flock to Python. And you're SO superior to everyone else, right ? :-) Frankly I prefer Pascal - most of my stuff gets proto'ed in Python now and then, if worthy, gets re-done in Pascal. I save 'C' for the more 'systems level/utility' stuff these days - sockets and such. Programming is about getting it done properly, does not matter if that's LISP or 'C' or FORTRAN or any of three dozen other options.
[toc] | [prev] | [next] | [standalone]
| From | Diego Garcia <dg@linux.rocks> |
|---|---|
| Date | 2025-11-09 11:25 +0000 |
| Message-ID | <pan$7dc5f$fbfa874c$ab899d75$b4081fc4@linux.rocks> |
| In reply to | #77153 |
On Sat, 8 Nov 2025 23:58:40 -0500, c186282 wrote: > On 11/8/25 06:31, Diego Garcia wrote: >> >> Digitally speaking, strings are a very unnatural construct >> and that's why C doesn't deal with them in a "nice" fashion. > > "Unnatural" ??? > Yes, very unnatural. The x86_64 processor has several data types that reflect the hardware registers and "string" is not one of them. In fact, "string" is not a data type at all but rather a smooshing of existing types to be able to fit a popular concept. It may have been simpler in the past when "string" was defined as an array of char types (uint8), but now there is Unicode and this severely complicates the matter regarding lengths and comparisons. > > Anyway, complex dealings with strings can certainly > be done ... but it's the tiny-step by tiny-step > aspect that's just damned annoying to use. > Again, not so much with Unicode strings. Ever hear of Unicode string normalization? To deal with Unicode a dedicated library is absolutely essential. There is the standard "icu" library and also the wonderful GNU "libunistring:" <https://icu.unicode.org/> <https://www.gnu.org/software/libunistring/> > >> And that's why incompetent programmers flock to Python. > > And you're SO superior to everyone else, right ? :-) > It's a well known fact (except to the Python people). > > Programming is about getting it done properly, does > not matter if that's LISP or 'C' or FORTRAN or any > of three dozen other options. > The digital computer was borne out of a single necessity: SPEED, SPEED, and more SPEED. Thus, programming is about SPEED and only SPEED. Try to predict the weather using Python. You'll be getting tomorrows forecast next week, or even next month.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-11-09 12:48 +0000 |
| Message-ID | <10eq2j7$392o0$1@dont-email.me> |
| In reply to | #77164 |
On 09/11/2025 11:25, Diego Garcia wrote: > Try to predict the weather using Python. You'll > be getting tomorrows forecast next week, or even > next month. So about the same as now, then... :-) -- I would rather have questions that cannot be answered... ...than to have answers that cannot be questioned Richard Feynman
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-09 23:29 -0500 |
| Message-ID | <tIecnTmREu-A94z0nZ2dnZfqn_SdnZ2d@giganews.com> |
| In reply to | #77167 |
On 11/9/25 07:48, The Natural Philosopher wrote: > On 09/11/2025 11:25, Diego Garcia wrote: >> Try to predict the weather using Python. You'll >> be getting tomorrows forecast next week, or even >> next month. > > So about the same as now, then... :-) Heh, heh ... I had a cousin who wanted to be a meteorologist - warned her that those were the only group with a rep worse than lawyers :-) Anyway, modern Python is not terribly slow and has a function/fix for *everything*. It's a perfectly good and useful language for almost anything. If you need extreme speed then you have to go with compiled langs (had iffy experiences with Python compilers). However a lot of stuff does not require 'extreme speed'. Memory/CPU profile ... irrelevant these days. You can run a LOT of Python scripts all at once and barely see a blip. The thread here is answered by "Whatever you're doing a lot of". Python is great for dealing with strings, and lots of stuff uses/manipulates a lot of strings. Python string-slicing was brought over from FORTRAN and a good thing it is. Pascal is kind of the middle ground ... it's pretty good with strings but also better structured and fast. Most of my Python re-does are about a third smaller in Pascal and much nicer-looking/clearer. 'C' has a definite place of course, but if you're doing a lot of string work and want to stick close to the standard libs then, well ..... I always install GCC, Clang and Tiny C Compiler. I want my pgms to compile in ALL of those, ergo sticking pretty close to standard libs. TCC oft makes the tightest binaries by the way ... Made a file archiving/encrypting utility meant to be evoked from most any other lang with an os.system() equiv. Did it in 'C'. File names/paths/manips/params out the ass. It WORKS great ... but WHAT A PAIN !!! Thought about a Pascal re-do ... but that time has past, the job is over. DO still use that app for anything I save to Cloud though ... they're not getting anything they can steal !!!
[toc] | [prev] | [next] | [standalone]
| From | Bobbie Sellers <bliss-sf4ever@dslextreme.com> |
|---|---|
| Date | 2025-11-09 09:18 -0800 |
| Message-ID | <10eqid5$3du22$1@dont-email.me> |
| In reply to | #77164 |
On 11/9/25 03:25, Diego Garcia wrote: > On Sat, 8 Nov 2025 23:58:40 -0500, c186282 wrote: > >> On 11/8/25 06:31, Diego Garcia wrote: >>> >>> Digitally speaking, strings are a very unnatural construct >>> and that's why C doesn't deal with them in a "nice" fashion. >> >> "Unnatural" ??? >> > > Yes, very unnatural. > > The x86_64 processor has several data types that reflect > the hardware registers and "string" is not one of them. > In fact, "string" is not a data type at all but rather > a smooshing of existing types to be able to fit a popular > concept. > > It may have been simpler in the past when "string" was defined > as an array of char types (uint8), but now there is Unicode > and this severely complicates the matter regarding lengths > and comparisons. > >> >> Anyway, complex dealings with strings can certainly >> be done ... but it's the tiny-step by tiny-step >> aspect that's just damned annoying to use. >> > > Again, not so much with Unicode strings. > > Ever hear of Unicode string normalization? > > To deal with Unicode a dedicated library is absolutely > essential. There is the standard "icu" library and > also the wonderful GNU "libunistring:" > > <https://icu.unicode.org/> > > <https://www.gnu.org/software/libunistring/> > > >> >>> And that's why incompetent programmers flock to Python. >> >> And you're SO superior to everyone else, right ? :-) >> > > It's a well known fact (except to the Python people). > > >> >> Programming is about getting it done properly, does >> not matter if that's LISP or 'C' or FORTRAN or any >> of three dozen other options. >> > > The digital computer was borne out of a single necessity: > SPEED, SPEED, and more SPEED. > > Thus, programming is about SPEED and only SPEED. > > Try to predict the weather using Python. You'll > be getting tomorrows forecast next week, or even > next month. Yes digital equipment is faster and maybe much more accurate than interpolation of stuff from slide rules and other mechanical calculators... But programming being solely about Speed seems a bit off to me. But I don' t concern myself with digital computers in general but with personal computers not company computers to which i might be assigned to one to use for data entry or other activity. I use the tools most convenient to me generally speaking and so do many other users of personal computers. I imagine the IT people at big companies do much the same but try to get the most reliable tools. I don't do weather predictions but go to a web site and read the summaries of what the US Weather Service had predicted using whichever models they feel are appropriate. I do not concern myself with those tools and models they use. Speed though is another matter and of course modern devices are much faster than what I started with. Remember C=64 was a 1 Megahertz device only 8 bit bus with 64 kilobytes of ram. A VIC-1541 disk drive stored only 161 kilobytes of data or programs. Currently using a 64 bit wide 6 core processor runnig at 2.5 GigaHertz with up to 12 threads 16 Gigabytes of Memory and a 512 Gigabyte SSD for storage. So for me hardware takes care of speed and lets me use the very large KDE's Plasma 6 without much difference from Plasma 5 in apparent speed. Programmers create all the Desktop Environments and they did so for a reason which was to increase the popularity of GNU/Linux among the common run of users. Thank you very much especially to Gael Duval who created the GUI installation system first seen on Mandrake many years ago. Before Gael Duval did his work you had to be very knowledgeable about your equipment and about the Linux system to install a system. i got a relatively cheap laptop and got a sucessful install many years back using the XP Tools to read a DVD then made 6 install CDs from the iso files on the DVD to install Mandriva Linux on a drive shared with XP. bliss- Dell Precision 7730- PCLOS 2025.10 Linux 6.12.57-pclos1- KDE Plasma 6.5.2
[toc] | [prev] | [next] | [standalone]
| From | Diego Garcia <dg@linux.rocks> |
|---|---|
| Date | 2025-11-09 20:13 +0000 |
| Message-ID | <pan$dd285$4640e42e$fcac06fd$7a2c8b8f@linux.rocks> |
| In reply to | #77183 |
On Sun, 9 Nov 2025 09:18:26 -0800, Bobbie Sellers wrote: > > But programming being solely about Speed seems a bit off to > me. > All that I can say in response is that you must not do much audio/video processing or very large file processing or large software compiling because each of these activities can make a person SCREAM for more SPEED. I have an 8-core Xeon W machine at 4.0GHz (I can't afford much better yet) and a relatively simple POV-Ray simulation can take 10 minutes. Imagine having to do THOUSANDS of those to compile a video. As another example, compiling LibreOffice takes 40 minutes and GCC will demand maybe an hour. The issue of SPEED has dominated all hardware development for decades already. Intel, for example, faced with physical limits to clock speed, has implemented instruction pipelines and other "tricks" to squeeze more and more speed out of its processors. SPEED, SPEED, SPEED, SPEED. It's all about SPEED. Clock speeds and memory speeds are already maxed out and so there is now multi-threading and multi-processors. It's all about SPEED and it will always be about SPEED. Starting in World War II, with the need to rapidly decode German encrypted messages, the development of the digital computer was spurred only by SPEED. The next phase is quantum computing which hopefully will bring even more SPEED.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-10 07:47 +0000 |
| Message-ID | <mndjl0FbepuU3@mid.individual.net> |
| In reply to | #77194 |
On Sun, 09 Nov 2025 20:13:49 +0000, Diego Garcia wrote: > SPEED, SPEED, SPEED, SPEED. It's all about SPEED. 50 mg of crystal should do the trick.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-11-10 12:09 +0000 |
| Message-ID | <10esklj$3veh8$2@dont-email.me> |
| In reply to | #77238 |
On 10/11/2025 07:47, rbowman wrote: > On Sun, 09 Nov 2025 20:13:49 +0000, Diego Garcia wrote: > >> SPEED, SPEED, SPEED, SPEED. It's all about SPEED. > > 50 mg of crystal should do the trick. LOL! -- “The ultimate result of shielding men from the effects of folly is to fill the world with fools.” Herbert Spencer
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-10 20:35 +0000 |
| Message-ID | <mnf0k6Fit1cU4@mid.individual.net> |
| In reply to | #77255 |
On Mon, 10 Nov 2025 12:09:23 +0000, The Natural Philosopher wrote: > On 10/11/2025 07:47, rbowman wrote: >> On Sun, 09 Nov 2025 20:13:49 +0000, Diego Garcia wrote: >> >>> SPEED, SPEED, SPEED, SPEED. It's all about SPEED. >> >> 50 mg of crystal should do the trick. > LOL! https://www.youtube.com/watch?v=9uyrIDGut_I
[toc] | [prev] | [next] | [standalone]
| From | Charlie Gibbs <cgibbs@kltpzyxm.invalid> |
|---|---|
| Date | 2025-11-10 21:15 +0000 |
| Message-ID | <uBsQQ.821276$Fe_d.579703@fx09.iad> |
| In reply to | #77273 |
On 2025-11-10, rbowman <bowman@montana.com> wrote: > On Mon, 10 Nov 2025 12:09:23 +0000, The Natural Philosopher wrote: > >> On 10/11/2025 07:47, rbowman wrote: >> >>> On Sun, 09 Nov 2025 20:13:49 +0000, Diego Garcia wrote: >>> >>>> SPEED, SPEED, SPEED, SPEED. It's all about SPEED. >>> >>> 50 mg of crystal should do the trick. >> >> LOL! > > https://www.youtube.com/watch?v=9uyrIDGut_I https://www.youtube.com/watch?v=Ed6g6I2-wZc -- /~\ Charlie Gibbs | Growth for the sake of \ / <cgibbs@kltpzyxm.invalid> | growth is the ideology X I'm really at ac.dekanfrus | of the cancer cell. / \ if you read it the right way. | -- Edward Abbey
[toc] | [prev] | [next] | [standalone]
Page 1 of 16 [1] 2 3 … 16 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web