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 311 — 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 Eric Pozharski <apple.universe@posteo.net> - 2025-11-25 10:26 +0000
Re: Recent history of vi Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-25 20:05 +0000
Re: Recent history of vi c186282 <c186282@nnada.net> - 2025-11-25 23:04 -0500
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 14 of 16 — ← Prev page 1 … 12 13 [14] 15 16 Next page →
| From | Richard Kettlewell <invalid@invalid.invalid> |
|---|---|
| Date | 2025-11-10 18:04 +0000 |
| Message-ID | <wwvzf8t9331.fsf@LkoBDZeT.terraraq.uk> |
| In reply to | #77183 |
Bobbie Sellers <bliss-sf4ever@dslextreme.com> writes: > 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. Indeed, it’s not solely about performance. Other nonfunctionals like usability and security matter too. If comparing (pure) Python and C, Python can be developed much faster and eliminates whole categories of vulnerability, but performance will generally be lower. At work: - We prototype new algorithms in Python. Runtime performance is irrelevant and using a high-level language gets a lot of implementation detail out of the way. The Python implementations are useful for exploration/study and later to generate test vectors for the production implementations. - Production algorithm implementations are mostly in C. (I’d rather migrate to something safer but migration is a gigantic pain...) - Particularly performance-sensitive algorithms are additionally implemented in FPGA, which beats the C versions by a large factor. > 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. Our target is an embedded device, the application CPU is quite slow compared to a modern desktop or server CPU. We also have much lower power budget than a general-purpose computer. -- https://www.greenend.org.uk/rjk/
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@vallor.earth> |
|---|---|
| Date | 2025-11-11 16:52 +0000 |
| Message-ID | <10evpl2$rdcf$2@dont-email.me> |
| In reply to | #77183 |
At Sun, 9 Nov 2025 09:18:26 -0800, Bobbie Sellers <bliss-sf4ever@dslextreme.com> wrote: > > > 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. [...snip...] Agreed. The MILSPEC for telecommunications back when I was doing that was "secure, reliable, rapid". I think that applies to data processing in general. Meanwhile, "Mr. Speed" runs with all the security mitigations turned off in his kernel. Also turns off stack-smashing protections when compiling his Gentoo goodies. More power to him, I guess...but I'm pretty sure most people wouldn't do that. -- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090Ti 24G OS: Linux 6.18.0-rc5 D: Mint 22.2 DE: Xfce 4.18 NVIDIA: 580.105.08 Mem: 258G "Keep London tidy... Shoot a pigeon."
[toc] | [prev] | [next] | [standalone]
| From | Diego Garcia <dg@linux.rocks> |
|---|---|
| Date | 2025-11-11 20:06 +0000 |
| Message-ID | <pan$e5d8e$eaec6dfa$d774a958$17f58c9@linux.rocks> |
| In reply to | #77330 |
On Tue, 11 Nov 2025 16:52:50 +0000, vallor wrote: > > Agreed. The MILSPEC for telecommunications back when > I was doing that was "secure, reliable, rapid". > > I think that applies to data processing in general. > No it does not. Telecommunications is an entirely different situation that demands security but other areas of "data processing" simply do not. > > Meanwhile, "Mr. Speed" runs with all the security > mitigations turned off in his kernel. Also turns off > stack-smashing protections when compiling his Gentoo > goodies. > Let's not stop with "stack smashing." There are oodles of other unnecessary security "features" built in to distro software. Let's just consider a few: -mindirect-branch=keep -mfunction-return=keep This means keep your fucking hands off of my function calls, jumps, and function return values. -fcf-protection=none This means do not "instrument" my fucking code for your security theater purposes. -Wl,-z,norelro This means don't do that stupid "relocation read-only" shit. Just load the goddamned file "as is" and be done with it. > > but I'm pretty sure most people wouldn't do that. > "Most people" wouldn't do anything. "Most people," like you, just swallow what their distro gives them without question. Ignorance is bliss, and YOU must be ecstatic.
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@vallor.earth> |
|---|---|
| Date | 2025-11-11 23:09 +0000 |
| Message-ID | <10f0fn6$12d74$1@dont-email.me> |
| In reply to | #77341 |
At Tue, 11 Nov 2025 20:06:56 +0000, Diego Garcia <dg@linux.rocks> wrote: > On Tue, 11 Nov 2025 16:52:50 +0000, vallor wrote: > > > > > Agreed. The MILSPEC for telecommunications back when > > I was doing that was "secure, reliable, rapid". > > > > I think that applies to data processing in general. > > > > No it does not. https://www.youtube.com/shorts/hwzmqnngyrU -- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090Ti 24G OS: Linux 6.18.0-rc5 D: Mint 22.2 DE: Xfce 4.18 NVIDIA: 580.105.08 Mem: 258G "By all means, let's not confuse ourselves with the facts!"
[toc] | [prev] | [next] | [standalone]
| From | Nuno Silva <nunojsilva@invalid.invalid> |
|---|---|
| Date | 2025-11-11 23:31 +0000 |
| Message-ID | <10f0h0k$12iu1$3@dont-email.me> |
| In reply to | #77347 |
On 2025-11-11, vallor wrote: > At Tue, 11 Nov 2025 20:06:56 +0000, Diego Garcia <dg@linux.rocks> wrote: > >> On Tue, 11 Nov 2025 16:52:50 +0000, vallor wrote: >> >> > >> > Agreed. The MILSPEC for telecommunications back when >> > I was doing that was "secure, reliable, rapid". >> > >> > I think that applies to data processing in general. >> > >> >> No it does not. > > https://www.youtube.com/shorts/hwzmqnngyrU Is this fellow (Diego) the same as Farley Flud? Or is the linux.rocks at the end of their address merely a coincidence? -- Nuno Silva
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-12 04:50 +0000 |
| Message-ID | <mnii04F5v4gU1@mid.individual.net> |
| In reply to | #77350 |
On Tue, 11 Nov 2025 23:31:32 +0000, Nuno Silva wrote: > On 2025-11-11, vallor wrote: > >> At Tue, 11 Nov 2025 20:06:56 +0000, Diego Garcia <dg@linux.rocks> >> wrote: >> >>> On Tue, 11 Nov 2025 16:52:50 +0000, vallor wrote: >>> >>> >>> > Agreed. The MILSPEC for telecommunications back when I was doing >>> > that was "secure, reliable, rapid". >>> > >>> > I think that applies to data processing in general. >>> > >>> > >>> No it does not. >> >> https://www.youtube.com/shorts/hwzmqnngyrU > > Is this fellow (Diego) the same as Farley Flud? Or is the linux.rocks at > the end of their address merely a coincidence? Same. Looking through my Score file, Nux Vomica, Farley Flud, Diego Garcia, Lester Thorpe, Xavier Dominica, and Xavier Jones are the same critter. Once it a blue moon he (I assume) posts something worthwhile but then it's more of the same and back into the bozo bin for a month.
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@vallor.earth> |
|---|---|
| Date | 2025-11-12 06:50 +0000 |
| Message-ID | <10f1an2$18fo7$1@dont-email.me> |
| In reply to | #77350 |
At Tue, 11 Nov 2025 23:31:32 +0000, Nuno Silva <nunojsilva@invalid.invalid> wrote: > On 2025-11-11, vallor wrote: > > > At Tue, 11 Nov 2025 20:06:56 +0000, Diego Garcia <dg@linux.rocks> wrote: > > > >> On Tue, 11 Nov 2025 16:52:50 +0000, vallor wrote: > >> > >> > > >> > Agreed. The MILSPEC for telecommunications back when > >> > I was doing that was "secure, reliable, rapid". > >> > > >> > I think that applies to data processing in general. > >> > > >> > >> No it does not. > > > > https://www.youtube.com/shorts/hwzmqnngyrU > > Is this fellow (Diego) the same as Farley Flud? Or is the linux.rocks at > the end of their address merely a coincidence? Yes, same cuckoo guy. -- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090Ti 24G OS: Linux 6.18.0-rc5 D: Mint 22.2 DE: Xfce 4.18 NVIDIA: 580.105.08 Mem: 258G "Shin: A device for finding furniture in the dark."
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-12 20:05 +0000 |
| Message-ID | <mnk7koFf6c0U5@mid.individual.net> |
| In reply to | #77386 |
On Wed, 12 Nov 2025 06:50:10 +0000, vallor wrote: > At Tue, 11 Nov 2025 23:31:32 +0000, Nuno Silva > <nunojsilva@invalid.invalid> wrote: > >> On 2025-11-11, vallor wrote: >> >> > At Tue, 11 Nov 2025 20:06:56 +0000, Diego Garcia <dg@linux.rocks> >> > wrote: >> > >> >> On Tue, 11 Nov 2025 16:52:50 +0000, vallor wrote: >> >> >> >> >> >> > Agreed. The MILSPEC for telecommunications back when I was doing >> >> > that was "secure, reliable, rapid". >> >> > >> >> > I think that applies to data processing in general. >> >> > >> >> > >> >> No it does not. >> > >> > https://www.youtube.com/shorts/hwzmqnngyrU >> >> Is this fellow (Diego) the same as Farley Flud? Or is the linux.rocks >> at the end of their address merely a coincidence? > > Yes, same cuckoo guy. Add Joe Fantastic to the list. That one popped up in c.o.l.a today.
[toc] | [prev] | [next] | [standalone]
| From | Nuno Silva <nunojsilva@invalid.invalid> |
|---|---|
| Date | 2025-11-15 17:17 +0000 |
| Message-ID | <10facih$3kg0s$1@dont-email.me> |
| In reply to | #77419 |
On 2025-11-12, rbowman wrote: > On Wed, 12 Nov 2025 06:50:10 +0000, vallor wrote: > >> At Tue, 11 Nov 2025 23:31:32 +0000, Nuno Silva >> <nunojsilva@invalid.invalid> wrote: >> >>> On 2025-11-11, vallor wrote: >>> >>> Is this fellow (Diego) the same as Farley Flud? Or is the linux.rocks >>> at the end of their address merely a coincidence? >> >> Yes, same cuckoo guy. > > Add Joe Fantastic to the list. That one popped up in c.o.l.a today. Thanks everyone for all responses. I may have to appropriately update scoring rules then :-) -- Nuno Silva
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2025-11-12 12:35 +0100 |
| Message-ID | <q08eulx6bn.ln2@Telcontar.valinor> |
| In reply to | #77350 |
On 2025-11-12 00:31, Nuno Silva wrote: > On 2025-11-11, vallor wrote: > >> At Tue, 11 Nov 2025 20:06:56 +0000, Diego Garcia <dg@linux.rocks> wrote: >> >>> On Tue, 11 Nov 2025 16:52:50 +0000, vallor wrote: >>> >>>> >>>> Agreed. The MILSPEC for telecommunications back when >>>> I was doing that was "secure, reliable, rapid". >>>> >>>> I think that applies to data processing in general. >>>> >>> >>> No it does not. >> >> https://www.youtube.com/shorts/hwzmqnngyrU > > Is this fellow (Diego) the same as Farley Flud? Or is the linux.rocks at > the end of their address merely a coincidence? I was also wondering about that. -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-11-12 21:09 +0000 |
| Message-ID | <6914f7a1$0$31898$426a74cc@news.free.fr> |
| In reply to | #77402 |
Le 12-11-2025, Carlos E.R. <robin_listas@es.invalid> a écrit : > On 2025-11-12 00:31, Nuno Silva wrote: >> >> Is this fellow (Diego) the same as Farley Flud? Or is the linux.rocks at >> the end of their address merely a coincidence? > > I was also wondering about that. You shouldn't wonder any longer. There is no doubt about that. Sometimes he's answering his own messages with other pseudos but that changes nothing: he's the same guy. He's well known on cola where he doesn't even try to hide that. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-13 00:22 -0500 |
| Message-ID | <AJGdndG5-Kyg9oj0nZ2dnZfqnPWdnZ2d@giganews.com> |
| In reply to | #77432 |
On 11/12/25 16:09, Stéphane CARPENTIER wrote: > Le 12-11-2025, Carlos E.R. <robin_listas@es.invalid> a écrit : >> On 2025-11-12 00:31, Nuno Silva wrote: >>> >>> Is this fellow (Diego) the same as Farley Flud? Or is the linux.rocks at >>> the end of their address merely a coincidence? >> >> I was also wondering about that. > > You shouldn't wonder any longer. There is no doubt about that. Sometimes > he's answering his own messages with other pseudos but that changes > nothing: he's the same guy. Yep ... same self-superior insulting shit .... Guess that makes his wee-wee tingle.
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2025-11-12 21:06 +0000 |
| Message-ID | <6914f6bd$0$31898$426a74cc@news.free.fr> |
| In reply to | #77350 |
Le 11-11-2025, Nuno Silva <nunojsilva@invalid.invalid> a écrit : > > Is this fellow (Diego) the same as Farley Flud? Or is the linux.rocks at > the end of their address merely a coincidence? Yes. And the same as Fabian RUSSEL and the same as LARRY PIET and the same as a lot of others I don't remember all. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-12 01:30 -0500 |
| Message-ID | <rdmcndqsdIgTtIn0nZ2dnZfqnPadnZ2d@giganews.com> |
| In reply to | #77347 |
On 11/11/25 18:09, vallor wrote: > At Tue, 11 Nov 2025 20:06:56 +0000, Diego Garcia <dg@linux.rocks> wrote: > >> On Tue, 11 Nov 2025 16:52:50 +0000, vallor wrote: >> >>> >>> Agreed. The MILSPEC for telecommunications back when >>> I was doing that was "secure, reliable, rapid". >>> >>> I think that applies to data processing in general. >>> >> >> No it does not. > > https://www.youtube.com/shorts/hwzmqnngyrU Ummmm ... just an endless loop of someone fucking with an old Black Forest Coo-Coo clock ....... No, am NOT going to subscribe :-) I do have an old coo-coo clock ... do NOT use it however ... don't need it waking me up at 3AM ! Actually it needs some maint ... I think whatever oil was on the gearworks has frozen up .....
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-09 19:28 +0000 |
| Message-ID | <mnc8b1F4tpaU1@mid.individual.net> |
| In reply to | #77164 |
On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
> Try to predict the weather using Python. You'll be getting tomorrows
> forecast next week, or even next month.
How about in a second or two? The starting point is
url = f"https://api.weather.gov/points/{latitude},{longitude}"
The JSON response is processed to get the grid id necessary to build a URL
for the current observations, and to extract the URL for the forecast.
THE JSON responses are processed and the relevant data is printed. It is
46 lines of Python including white space. Feel free to do it in C.
Output:
temperature 37.4 dewpoint 28.40 humidity 69.69 pressure 30.47
Today
Patchy fog before 8am. Partly sunny, with a high near 45. West wind around
2 mph.
temperature: 45
wind 2 mph W
Tonight
Patchy fog after 5am. Mostly cloudy, with a low around 32. East southeast
wind 2 to 6 mph.
temperature: 32
wind 2 to 6 mph ESE
Monday
Patchy fog before 8am, then a chance of rain. Partly sunny, with a high
near 53. South southeast wind 2 to 8 mph. Chance of precipitation is 30%.
temperature: 53
wind 2 to 8 mph SSE
Monday Night
A chance of rain before 5am. Mostly cloudy, with a low around 38. West
wind 6 to 9 mph. Chance of precipitation is 30%.
temperature: 38
wind 6 to 9 mph W
Veterans Day
Partly sunny, with a high near 56. West wind 2 to 6 mph.
temperature: 56
wind 2 to 6 mph W
Tuesday Night
Mostly cloudy, with a low around 34.
temperature: 34
wind 2 mph SSE
Wednesday
Mostly cloudy, with a high near 55.
temperature: 55
wind 3 mph SSE
Wednesday Night
Mostly cloudy, with a low around 35.
temperature: 35
wind 2 to 8 mph SE
Thursday
A chance of rain after 11am. Partly sunny, with a high near 57.
temperature: 57
wind 7 mph SSE
Thursday Night
Rain likely. Mostly cloudy, with a low around 33.
temperature: 33
wind 6 to 9 mph SSW
Friday
A chance of rain. Mostly cloudy, with a high near 46.
temperature: 46
wind 6 to 9 mph W
Friday Night
A chance of rain before 11pm, then a chance of rain and snow. Mostly
cloudy, with a low around 29.
temperature: 29
wind 7 mph SW
Saturday
A chance of rain and snow. Partly sunny, with a high near 45.
temperature: 45
wind 5 to 8 mph SSW
Saturday Night
A chance of rain before 5am, then a chance of rain and snow. Mostly
cloudy, with a low around 29.
temperature: 29
wind 3 to 7 mph SSW
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-10 00:36 -0500 |
| Message-ID | <-RycnTDdvP2b54z0nZ2dnZfqnPGdnZ2d@giganews.com> |
| In reply to | #77188 |
On 11/9/25 14:28, rbowman wrote:
> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>
>> Try to predict the weather using Python. You'll be getting tomorrows
>> forecast next week, or even next month.
>
> How about in a second or two? The starting point is
> url = f"https://api.weather.gov/points/{latitude},{longitude}"
Keep getting "invalid point" :-)
At present I grab/micro-parse some more
conventional weather sites for at least
my local area. It's part of my rotating
security-cam pages I have running on at
least two PIs.
Getting harder to find weather radar loops
in GIF anymore alas ...
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-10 07:46 +0000 |
| Message-ID | <mndjhrFbepuU2@mid.individual.net> |
| In reply to | #77228 |
On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
> On 11/9/25 14:28, rbowman wrote:
>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>>
>>> Try to predict the weather using Python. You'll be getting tomorrows
>>> forecast next week, or even next month.
>>
>> How about in a second or two? The starting point is
>> url = f"https://api.weather.gov/points/{latitude},{longitude}"
>
> Keep getting "invalid point"
Try
https://api.weather.gov/points/42.934,-90.567
wherever the hell that is. You're in the western hemisphere and longitudes
are negative.
The browser should show the JSON formatted so you can grab the 'forecast'
URL
https://api.weather.gov/gridpoints/ARX/88,22/forecast
and get the daily forecasts. Doesn't look like paradise. Curiosity got the
better of me -- it's Left Moose Nut, Wisconsin.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-10 23:22 -0500 |
| Message-ID | <Nd6dnTbIQ9aUJ4_0nZ2dnZfqnPWdnZ2d@giganews.com> |
| In reply to | #77237 |
On 11/10/25 02:46, rbowman wrote:
> On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
>
>> On 11/9/25 14:28, rbowman wrote:
>>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>>>
>>>> Try to predict the weather using Python. You'll be getting tomorrows
>>>> forecast next week, or even next month.
>>>
>>> How about in a second or two? The starting point is
>>> url = f"https://api.weather.gov/points/{latitude},{longitude}"
>>
>> Keep getting "invalid point"
>
> Try
>
> https://api.weather.gov/points/42.934,-90.567
That works ... but change the coords a bit and
it won't. Seems it only knows a handful of
locations.
In USA, the most useful sites seem to revolve
around 'aviation weather' and center on certain
airports, typically a 3-letter abbreviation.
Immediate and some forecast data can be had - but
you'll badly want Python to slice and dice and
search that out of the html :-)
> wherever the hell that is. You're in the western hemisphere and longitudes
> are negative.
>
> The browser should show the JSON formatted so you can grab the 'forecast'
> URL
>
> https://api.weather.gov/gridpoints/ARX/88,22/forecast
>
> and get the daily forecasts. Doesn't look like paradise. Curiosity got the
> better of me -- it's Left Moose Nut, Wisconsin.
Ten years ago it was much easier to find comma/tab delim
tables of current/recent weather data. Now it's almost only
html or, worse, requires JS to build-up a page that's
impossible to get/parse. Not sure if it's just "newer
stupider people" or some PLAN. Anyway, now, your best
bets are obscure 2nd/3rd-line 'government' sites that
haven't changed anything since forever.
SOMEWHERE I have a link to US airport-related weather
that includes a more easily-parsed tab-delim table
which includes current and the past 24 hours temps,
pressures, humidity etc. Used it at The Office before
I retired for a multi-info display nobody, typically,
appreciated (complex TK touch-sensitive of cams/environment
and even a scrolling news feed at the bottom) all on PI.
Gotta search all the shit I took home .......
TK ... once created/destroyed windows as-needed ... but
soon found it better to just keep them open and position
off-screen until needed again. Easier, quicker, cleaner.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-11-11 20:16 +0000 |
| Message-ID | <mnhjt9F1ld6U4@mid.individual.net> |
| In reply to | #77312 |
On Mon, 10 Nov 2025 23:22:22 -0500, c186282 wrote:
> On 11/10/25 02:46, rbowman wrote:
>> On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
>>
>>> On 11/9/25 14:28, rbowman wrote:
>>>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>>>>
>>>>> Try to predict the weather using Python. You'll be getting
>>>>> tomorrows forecast next week, or even next month.
>>>>
>>>> How about in a second or two? The starting point is
>>>> url = f"https://api.weather.gov/points/{latitude},{longitude}"
>>>
>>> Keep getting "invalid point"
>>
>> Try
>>
>> https://api.weather.gov/points/42.934,-90.567
>
> That works ... but change the coords a bit and it won't. Seems it
> only knows a handful of locations.
I picked that at random.
https://api.weather.gov/points/36.934,-72.567
Chincoteague, VA
https://api.weather.gov/points/40.934,-94.567
Lenox, IA
https://api.weather.gov/points/36.934,-84.567
Burnside KY
https://api.weather.gov/points/58.114,-134.666
Juneau, AK
https://api.weather.gov/points/38.114,-134.666
no data, but it's 886 km off the coast of northern California.
https://api.weather.gov/points/19.66,-156.012
Kailua, HI
You do have to pick points in the US.
https://api.weather.gov/points/51.130,-114.218
is Calgary AB and no data.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-11-12 00:08 -0500 |
| Message-ID | <ysWdnVa7PO_8i4n0nZ2dnZfqn_WdnZ2d@giganews.com> |
| In reply to | #77342 |
On 11/11/25 15:16, rbowman wrote:
> On Mon, 10 Nov 2025 23:22:22 -0500, c186282 wrote:
>
>> On 11/10/25 02:46, rbowman wrote:
>>> On Mon, 10 Nov 2025 00:36:58 -0500, c186282 wrote:
>>>
>>>> On 11/9/25 14:28, rbowman wrote:
>>>>> On Sun, 09 Nov 2025 11:25:36 +0000, Diego Garcia wrote:
>>>>>
>>>>>> Try to predict the weather using Python. You'll be getting
>>>>>> tomorrows forecast next week, or even next month.
>>>>>
>>>>> How about in a second or two? The starting point is
>>>>> url = f"https://api.weather.gov/points/{latitude},{longitude}"
>>>>
>>>> Keep getting "invalid point"
>>>
>>> Try
>>>
>>> https://api.weather.gov/points/42.934,-90.567
>>
>> That works ... but change the coords a bit and it won't. Seems it
>> only knows a handful of locations.
>
> I picked that at random.
>
> https://api.weather.gov/points/36.934,-72.567
> Chincoteague, VA
>
> https://api.weather.gov/points/40.934,-94.567
> Lenox, IA
>
> https://api.weather.gov/points/36.934,-84.567
> Burnside KY
>
> https://api.weather.gov/points/58.114,-134.666
> Juneau, AK
>
> https://api.weather.gov/points/38.114,-134.666
> no data, but it's 886 km off the coast of northern California.
>
> https://api.weather.gov/points/19.66,-156.012
> Kailua, HI
>
> You do have to pick points in the US.
>
> https://api.weather.gov/points/51.130,-114.218
> is Calgary AB and no data.
My experience ... sometimes it works and sometimes it doesn't.
Used GM to get coords dead center of my local airport and
it does work. However it's a page of links that contain
more links that contain more (or self-referent) links.
Not sure yet WHAT is the forecast (hopefully table) or
even the current readings. Will keep looking.
Oh, DID find my old app that got weather info. It was
about seven years old and, naturally, the links don't
do anything useful anymore. Bummer - it WAS good easy
tabular data easy to parse.
Have to find SOME plan for pages that do naught but
run JS to build visible pages/tables. This is getting
kind of severe now.
Gimme a link to a nice clean CSV file any day !
[toc] | [prev] | [next] | [standalone]
Page 14 of 16 — ← Prev page 1 … 12 13 [14] 15 16 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web