Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #75447 > unrolled thread
| Started by | c186282 <c186282@nnada.net> |
|---|---|
| First post | 2025-09-30 00:12 -0400 |
| Last post | 2025-11-24 23:48 +0000 |
| Articles | 20 on this page of 306 — 22 participants |
Back to article view | Back to comp.os.linux.misc
AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-09-30 00:12 -0400
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-09-30 09:37 +0200
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-09-30 19:21 +0200
Re: AI-Based Coding Taking Over Richard Kettlewell <invalid@invalid.invalid> - 2025-09-30 19:35 +0100
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-09-30 22:45 +0000
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-09-30 22:41 +0000
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-09-30 22:44 +0000
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-09-30 23:46 +0000
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-01 01:05 +0000
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-01 01:06 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-01 03:53 +0000
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-01 04:57 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-01 21:41 -0400
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-01 21:40 -0400
Re: AI-Based Coding Taking Over candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> - 2025-10-10 18:00 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-11 02:41 -0400
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-11 11:00 +0100
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-11 19:39 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-11 22:31 -0400
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-12 12:09 +0100
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-11 19:03 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-11 22:28 -0400
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-12 12:04 +0100
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-12 19:40 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-13 03:24 -0400
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-13 10:19 +0100
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-13 19:05 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-14 01:24 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-14 07:09 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-14 20:35 -0400
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-14 10:04 +0200
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-14 10:04 +0100
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-14 12:06 +0200
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-14 11:32 +0100
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-14 12:45 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-14 22:05 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-14 23:31 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-15 14:30 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-14 21:47 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-14 23:31 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-15 06:41 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-15 03:30 -0400
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-15 16:57 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-15 21:31 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-16 18:43 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-16 18:59 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-16 13:43 -0700
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-17 02:02 +0000
Re: AI-Based Coding Taking Over Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-10-17 07:58 -0400
Re: AI-Based Coding Taking Over Pancho <Pancho.Jones@protonmail.com> - 2025-10-17 17:38 +0100
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-17 22:16 +0000
Re: AI-Based Coding Taking Over Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-10-18 08:53 -0400
Bikes [Was: AI-Based Coding Taking Over] "Carlos E.R." <robin_listas@es.invalid> - 2025-10-18 20:02 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-18 19:51 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-18 22:55 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-19 02:32 +0000
Nuisance fauna [Was: AI-Based Coding Taking Over] "Carlos E.R." <robin_listas@es.invalid> - 2025-10-19 13:31 +0200
Re: AI-Based Coding Taking Over Pancho <Pancho.Jones@protonmail.com> - 2025-10-19 08:41 +0100
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-19 11:15 +0100
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-19 20:57 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-20 00:23 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-20 05:44 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-20 03:32 -0400
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-20 10:34 +0200
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-20 23:22 -0400
Re: AI-Based Coding Taking Over Pancho <Pancho.Jones@protonmail.com> - 2025-10-21 08:54 +0100
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-21 21:22 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-22 05:45 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-22 02:21 -0400
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-22 14:07 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-22 21:05 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 10:42 +0200
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-24 10:11 +0100
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-24 19:47 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-24 19:45 +0000
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-25 10:47 +0100
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-25 19:46 +0000
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-22 08:19 +0100
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-21 20:05 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-21 23:50 -0400
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-22 11:32 +0100
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-20 20:12 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-20 11:53 -0700
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-21 03:32 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-20 21:52 -0700
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-21 01:44 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-21 19:34 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-21 23:41 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-22 05:40 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-22 02:23 -0400
Oil leaks "Carlos E.R." <robin_listas@es.invalid> - 2025-10-22 14:13 +0200
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-20 10:29 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-20 19:43 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-20 20:48 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-21 04:10 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-21 01:39 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-21 20:02 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-21 23:48 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-22 06:02 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-22 03:34 -0400
Vehicles "Carlos E.R." <robin_listas@es.invalid> - 2025-10-22 14:30 +0200
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-22 18:03 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-22 20:51 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-23 14:54 +0200
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-22 14:26 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-22 21:00 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-23 04:01 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-23 20:27 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-23 20:59 -0700
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-25 04:47 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-24 22:09 -0700
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-25 19:43 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-25 22:23 +0200
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-25 20:51 -0400
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-26 19:58 +0100
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-26 11:00 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-26 18:40 +0000
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-26 22:19 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-27 00:48 +0100
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-27 03:12 -0400
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-27 10:15 +0100
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-27 08:20 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-27 02:54 +0000
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-27 08:23 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-26 22:45 -0400
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-27 03:07 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-27 14:26 +0000
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-27 14:31 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-27 20:41 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-27 14:17 -0700
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-28 05:40 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-28 07:45 +0000
Re: AI-Based Coding Taking Over Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-10-28 06:18 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-28 19:19 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-28 19:08 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-27 22:30 -0400
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-28 07:45 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-28 11:25 -0700
The Good Ol' Days of Computing? Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-10-28 06:15 -0400
Re: The Good Ol' Days of Computing? c186282 <c186282@nnada.net> - 2025-10-29 02:12 -0400
Re: The Good Ol' Days of Computing? John Ames <commodorejohn@gmail.com> - 2025-10-29 08:43 -0700
Re: The Good Ol' Days of Computing? c186282 <c186282@nnada.net> - 2025-10-29 21:30 -0400
Re: The Good Ol' Days of Computing? rbowman <bowman@montana.com> - 2025-10-30 03:07 +0000
Re: The Good Ol' Days of Computing? c186282 <c186282@nnada.net> - 2025-10-30 00:49 -0400
Re: The Good Ol' Days of Computing? rbowman <bowman@montana.com> - 2025-10-30 06:29 +0000
Re: The Good Ol' Days of Computing? The Natural Philosopher <tnp@invalid.invalid> - 2025-10-30 07:00 +0000
Re: The Good Ol' Days of Computing? c186282 <c186282@nnada.net> - 2025-10-30 11:32 -0400
Re: The Good Ol' Days of Computing? The Natural Philosopher <tnp@invalid.invalid> - 2025-10-30 16:39 +0000
Re: The Good Ol' Days of Computing? c186282 <c186282@nnada.net> - 2025-10-30 11:29 -0400
Re: The Good Ol' Days of Computing? The Natural Philosopher <tnp@invalid.invalid> - 2025-10-30 16:37 +0000
Re: The Good Ol' Days of Computing? rbowman <bowman@montana.com> - 2025-10-30 20:21 +0000
Re: The Good Ol' Days of Computing? rbowman <bowman@montana.com> - 2025-10-31 04:01 +0000
Personal computer (was Re: AI-Based Coding Taking Over) John Ames <commodorejohn@gmail.com> - 2025-10-27 09:21 -0700
Re: Personal computer (was Re: AI-Based Coding Taking Over) The Natural Philosopher <tnp@invalid.invalid> - 2025-10-27 16:53 +0000
Re: Personal computer (was Re: AI-Based Coding Taking Over) Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-10-27 13:48 -0400
Re: Personal computer (was Re: AI-Based Coding Taking Over) rbowman <bowman@montana.com> - 2025-10-27 20:53 +0000
Re: Personal computer (was Re: AI-Based Coding Taking Over) John Ames <commodorejohn@gmail.com> - 2025-10-27 13:56 -0700
Re: Personal computer (was Re: AI-Based Coding Taking Over) Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-10-28 06:30 -0400
Re: Personal computer (was Re: AI-Based Coding Taking Over) John Ames <commodorejohn@gmail.com> - 2025-10-28 08:15 -0700
Re: Personal computer (was Re: AI-Based Coding Taking Over) rbowman <bowman@montana.com> - 2025-10-28 19:44 +0000
Re: Personal computer (was Re: AI-Based Coding Taking Over) John Ames <commodorejohn@gmail.com> - 2025-10-28 12:51 -0700
Re: Personal computer (was Re: AI-Based Coding Taking Over) John Ames <commodorejohn@gmail.com> - 2025-10-28 15:39 -0700
Re: Personal computer (was Re: AI-Based Coding Taking Over) rbowman <bowman@montana.com> - 2025-10-29 02:14 +0000
Re: Personal computer (was Re: AI-Based Coding Taking Over) rbowman <bowman@montana.com> - 2025-10-29 01:52 +0000
Re: Personal computer (was Re: AI-Based Coding Taking Over) rbowman <bowman@montana.com> - 2025-10-28 19:37 +0000
Re: Personal computer (was Re: AI-Based Coding Taking Over) Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-28 07:45 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-27 10:18 -0700
Re: AI-Based Coding Taking Over Chris Ahlstrom <OFeem1987@teleworm.us> - 2025-10-27 13:42 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-27 21:18 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-28 07:45 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-27 19:28 +0100
Re: AI-Based Coding Taking Over Robert Riches <spamtrap42@jacob21819.net> - 2025-10-24 03:30 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-24 05:44 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 10:21 +0200
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-23 14:57 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-23 20:23 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 10:35 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-24 19:30 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 22:13 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-25 02:38 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-25 15:17 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-25 19:40 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-23 00:29 -0400
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-23 14:59 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-23 20:20 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-23 19:09 -0700
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-24 05:49 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 10:38 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-24 19:41 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-24 13:05 -0700
Agriculture "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 22:25 +0200
Re: Agriculture rbowman <bowman@montana.com> - 2025-10-25 02:22 +0000
Vehicles "Carlos E.R." <robin_listas@es.invalid> - 2025-10-22 14:21 +0200
Re: Vehicles rbowman <bowman@montana.com> - 2025-10-22 20:14 +0000
Re: Vehicles "Carlos E.R." <robin_listas@es.invalid> - 2025-10-23 15:06 +0200
Re: Vehicles rbowman <bowman@montana.com> - 2025-10-23 20:01 +0000
Re: Vehicles "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 10:09 +0200
Re: Vehicles rbowman <bowman@montana.com> - 2025-10-24 18:40 +0000
Re: Vehicles "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 21:22 +0200
Re: Vehicles rbowman <bowman@montana.com> - 2025-10-25 01:54 +0000
Re: Vehicles "Carlos E.R." <robin_listas@es.invalid> - 2025-10-25 15:20 +0200
Re: Vehicles c186282 <c186282@nnada.net> - 2025-10-23 00:28 -0400
Re: Vehicles The Natural Philosopher <tnp@invalid.invalid> - 2025-10-23 08:55 +0100
Re: Vehicles "Carlos E.R." <robin_listas@es.invalid> - 2025-10-23 15:09 +0200
Re: Vehicles Rich <rich@example.invalid> - 2025-10-23 17:46 +0000
Re: Vehicles rbowman <bowman@montana.com> - 2025-10-23 20:08 +0000
Re: Vehicles Rich <rich@example.invalid> - 2025-10-23 22:28 +0000
Re: Vehicles rbowman <bowman@montana.com> - 2025-10-24 05:09 +0000
Re: Vehicles "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 01:43 +0200
Re: Vehicles "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 01:47 +0200
Re: Vehicles Rich <rich@example.invalid> - 2025-11-13 17:25 +0000
Re: Vehicles c186282 <c186282@nnada.net> - 2025-10-23 22:51 -0400
Pouring a coffee into a street drain. "Carlos E.R." <robin_listas@es.invalid> - 2025-10-24 09:59 +0200
Re: Pouring a coffee into a street drain. rbowman <bowman@montana.com> - 2025-10-24 18:43 +0000
Re: Vehicles c186282 <c186282@nnada.net> - 2025-10-23 22:45 -0400
Re: Vehicles rbowman <bowman@montana.com> - 2025-10-23 20:06 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-21 00:32 -0400
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-20 23:18 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-21 19:50 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-19 20:40 +0000
Re: AI-Based Coding Taking Over Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2025-10-19 14:24 -0700
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-20 06:04 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-20 10:48 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-20 19:52 +0000
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-21 01:02 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-21 03:39 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-21 01:33 -0400
Re: AI-Based Coding Taking Over "Carlos E.R." <robin_listas@es.invalid> - 2025-10-21 21:33 +0200
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-21 23:37 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-22 06:12 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-22 03:38 -0400
Vehicles. "Carlos E.R." <robin_listas@es.invalid> - 2025-10-22 14:35 +0200
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-21 19:42 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-17 17:36 +0000
Car inspections. "Carlos E.R." <robin_listas@es.invalid> - 2025-10-15 14:35 +0200
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-14 21:38 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-14 19:12 +0000
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-15 11:55 +0100
Re: AI-Based Coding Taking Over Robert Riches <spamtrap42@jacob21819.net> - 2025-10-16 03:07 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-16 02:56 -0400
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-14 21:06 -0400
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-15 11:59 +0100
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-16 01:00 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-16 07:29 +0000
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-16 11:22 +0100
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-17 22:34 -0400
Re: AI-Based Coding Taking Over Richard Kettlewell <invalid@invalid.invalid> - 2025-10-01 18:11 +0100
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-01 21:06 +0000
Re: AI-Based Coding Taking Over Nuno Silva <nunojsilva@invalid.invalid> - 2025-10-01 23:45 +0100
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-01 22:19 -0400
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-02 11:15 +0100
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-01 21:59 -0400
Re: AI-Based Coding Taking Over vallor <vallor@vallor.earth> - 2025-10-02 06:20 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-02 03:05 -0400
Re: AI-Based Coding Taking Over vallor <vallor@vallor.earth> - 2025-10-02 18:41 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-02 07:26 +0000
Re: AI-Based Coding Taking Over vallor <vallor@vallor.earth> - 2025-10-02 18:37 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-03 00:29 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-03 05:06 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-03 01:24 -0400
Re: AI-Based Coding Taking Over Bob Vloon <usenet@bananacorp.nl.invalid> - 2025-10-03 11:33 +0000
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-03 20:46 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-03 00:25 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-03 04:44 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-03 01:18 -0400
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-03 20:42 +0000
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-03 21:05 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-03 23:35 -0400
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-03 23:37 -0400
Re: AI-Based Coding Taking Over Richard Kettlewell <invalid@invalid.invalid> - 2025-10-03 08:54 +0100
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-10-03 10:02 +0100
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-10-03 20:41 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-03 23:24 -0400
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-03 23:21 -0400
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-03 23:20 -0400
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-04 17:04 +0000
Re: AI-Based Coding Taking Over not@telling.you.invalid (Computer Nerd Kev) - 2025-10-03 08:03 +1000
Re: AI-Based Coding Taking Over vallor <vallor@vallor.earth> - 2025-10-02 22:55 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-09-30 22:06 -0400
Re: AI-Based Coding Taking Over Jason H <jason_hindle@yahoo.com> - 2025-10-01 20:26 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-01 21:58 -0400
Re: AI-Based Coding Taking Over Farley Flud <fsquared@fsquared.linux> - 2025-09-30 11:25 +0000
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-09-30 12:56 +0100
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-09-30 22:48 -0400
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-01 03:53 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-01 21:36 -0400
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-09-30 22:16 -0400
Re: AI-Based Coding Taking Over John McCue <jmclnx@gmail.com.invalid> - 2025-10-31 16:52 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-10-31 20:19 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-10-31 22:45 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-10-31 22:35 -0400
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-24 23:42 +0000
Re: AI-Based Coding Taking Over The Natural Philosopher <tnp@invalid.invalid> - 2025-11-01 11:19 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-01 17:32 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-11-01 21:09 -0400
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-11-02 19:09 +0000
Re: AI-Based Coding Taking Over Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-11-02 19:30 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-11-03 02:28 +0000
Re: AI-Based Coding Taking Over rbowman <bowman@montana.com> - 2025-11-02 01:17 +0000
Re: AI-Based Coding Taking Over not@telling.you.invalid (Computer Nerd Kev) - 2025-11-03 07:52 +1000
Re: AI-Based Coding Taking Over John McCue <jmclnx@gmail.com.invalid> - 2025-11-02 22:21 +0000
Re: AI-Based Coding Taking Over Computer Nerd Kev <not@telling.you.invalid> - 2025-11-03 09:30 +1000
Re: AI-Based Coding Taking Over John McCue <jmclnx@gmail.com.invalid> - 2025-11-03 14:14 +0000
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-24 23:49 +0000
Re: AI-Based Coding Taking Over c186282 <c186282@nnada.net> - 2025-11-24 23:08 -0500
Re: AI-Based Coding Taking Over Lawrence D’Oliveiro <ldo@nz.invalid> - 2025-11-24 23:48 +0000
Page 13 of 16 — ← Prev page 1 … 11 12 [13] 14 15 16 Next page →
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-10-14 21:06 -0400 |
| Message-ID | <wpKcnU14_MwdbnP1nZ2dnZfqnPGdnZ2d@giganews.com> |
| In reply to | #76105 |
On 10/14/25 05:04, The Natural Philosopher wrote: > On 14/10/2025 09:04, Carlos E.R. wrote: >> On 2025-10-14 07:24, c186282 wrote: >>> On 10/13/25 15:05, rbowman wrote: >>>> On Mon, 13 Oct 2025 03:24:19 -0400, c186282 wrote: >>>> >>>>> Most USA cars, you can easily get to, replace, things like brake >>>>> drums/discs/bearings without getting more extreme. But not >>>>> EVERYBODY >>>>> thought that way. >>>> >>>> Yeah, sure... When the master cylinder on my '51 Chevy failed it >>>> became >>>> obvious that the cylinder had been bolted to the frame before the >>>> body was >>>> added. There was a small plate to allow replacing fluid but no >>>> provision >>>> for R&R. >>> >>> Hey, 1951 .... >>> >>> Drill the bolts and proceed. >>> >>>> I'm one of those strange people who looks under the hood when buying a >>>> car. I like to identify everything that may need maintenance and >>>> make sure >>>> it's accessible. >>> >>> THESE days ??? They INTENTIONALLY hide everything. >> >> These days what breaks are the electronic sensors. Mechanical is >> eternal, almost :-) >> > Not if its made of *plastic*. > > Inlet manifolds made of plastic at a $600 replacement cost? Who, ever, > broke a cast inlet manifold back in the day?... > > Composite timing belts that snap every 100,000 miles... > > Engines that destroy themselves in a manufacturer's attempt to get > better gas mileage or emissions? > > The cars are designed to last the warranty period and then be too > expensive to be worth fixing. Kind of, yes. 'Premium' brands may do a little better. Oh well, scan the antiques sites - if you want a 57 Nash you can BUY one still. Parts may be a bit few and far between now however. Ya know, with modern 3-D metal printing, somebody ought to sell one-off duplicates for almost every part for old cars. All they need are the original dimensions. Heat-treated parts, not that many in old vehicles, would be more of a challenge.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-10-15 11:59 +0100 |
| Message-ID | <10cnuqe$3jj2s$3@dont-email.me> |
| In reply to | #76154 |
On 15/10/2025 02:06, c186282 wrote: > Ya know, with modern 3-D metal printing, somebody ought > to sell one-off duplicates for almost every part for > old cars. All they need are the original dimensions. > Heat-treated parts, not that many in old vehicles, > would be more of a challenge. In the UK every part is available for 1970s era MGBs and the old Austin Healy Sprite, and you can build a brand new one. As long as you have the paperwork to say its really 50 years old, and so avoid emissions limits -- The New Left are the people they warned you about.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-10-16 01:00 -0400 |
| Message-ID | <sE2dnQ_UGeB05m31nZ2dnZfqnPqdnZ2d@giganews.com> |
| In reply to | #76182 |
On 10/15/25 06:59, The Natural Philosopher wrote: > On 15/10/2025 02:06, c186282 wrote: >> Ya know, with modern 3-D metal printing, somebody ought >> to sell one-off duplicates for almost every part for >> old cars. All they need are the original dimensions. >> Heat-treated parts, not that many in old vehicles, >> would be more of a challenge. > > In the UK every part is available for 1970s era MGBs and the old Austin > Healy Sprite, and you can build a brand new one. > As long as you have the paperwork to say its really 50 years old, and so > avoid emissions limits USA has no qualms about "how old". Too bad you live in a totalitarian country. Parts for vehicles maybe 1920 on CAN still be had. The problem is locating them and the PRICE. Of course "enthusiasts" care little for that. 1990 on, the ENGINES - the basic stuff - DID get much better. 1950s cars had a useful life of well under 100,000 miles - even assuming you did a couple of rebuilds. Of course in 1950 people didn't travel very far - and new cars were pretty cheap. So, in any case, I suggest the mentioned 3-D to-order fab as a viable business model. So long as you have the specs you can build compatible parts (esp if iron). Print, a little polishing, sell. As said, the enthusiasts WILL pay to keep that '47 Chevy truck running. I have no intention or will to START such a fab business - so I donate the idea. It is completely possible to do these days.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-10-16 07:29 +0000 |
| Message-ID | <mlbl79Fgmi0U8@mid.individual.net> |
| In reply to | #76218 |
On Thu, 16 Oct 2025 01:00:24 -0400, c186282 wrote: > 1990 on, the ENGINES - the basic stuff - DID get much better. 1950s > cars had a useful life of well under 100,000 miles - even assuming > you did a couple of rebuilds. Of course in 1950 people didn't travel > very far - and new cars were pretty cheap. My family and I made it from upstate NY to Seattle and back in a '51 Chevy. It was a little tired when we traded it for a '57. Most fleets tried to dump the vehicles by 75,000. Trucks were the same. Prior to the mid-90s you could plan on a in-frame rebuilt at 600-700 thousand. When the Detroit 60s hit the market they started getting million mile engines that had never been touched other than periodic maintenance.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-10-16 11:22 +0100 |
| Message-ID | <10cqh10$a1mj$3@dont-email.me> |
| In reply to | #76218 |
On 16/10/2025 06:00, c186282 wrote: > On 10/15/25 06:59, The Natural Philosopher wrote: >> On 15/10/2025 02:06, c186282 wrote: >>> Ya know, with modern 3-D metal printing, somebody ought >>> to sell one-off duplicates for almost every part for >>> old cars. All they need are the original dimensions. >>> Heat-treated parts, not that many in old vehicles, >>> would be more of a challenge. >> >> In the UK every part is available for 1970s era MGBs and the old >> Austin Healy Sprite, and you can build a brand new one. >> As long as you have the paperwork to say its really 50 years old, and >> so avoid emissions limits > > USA has no qualms about "how old". > > Too bad you live in a totalitarian country. > It is a very densely populated country and car exhaust pollution is a major issue. California piloted the use of fuel injection and catalytic converters and eventually the EU legislation caught up. So cars with high pollution (carburettors, no catalysts )are banned unless they are so old they count as 'classics' . > Parts for vehicles maybe 1920 on CAN still > be had. The problem is locating them and > the PRICE. Of course "enthusiasts" care > little for that. > Anything can be re-manufactured for a price...3D printing is excellent for simple little plastic parts. No one really makes carburettors for cars any more but they can be reconditioned > 1990 on, the ENGINES - the basic stuff - DID > get much better. 1950s cars had a useful life > of well under 100,000 miles - even assuming you > did a couple of rebuilds. Of course in 1950 > people didn't travel very far - and new cars > were pretty cheap. > > So, in any case, I suggest the mentioned > 3-D to-order fab as a viable business model. > So long as you have the specs you can build > compatible parts (esp if iron). Print, a > little polishing, sell. As said, the > enthusiasts WILL pay to keep that '47 Chevy > truck running. > lol > I have no intention or will to START such > a fab business - so I donate the idea. It > is completely possible to do these days. > Actually multi-axis CNC milling machines are good for short runs. Sand casting from 3D printed masters is possible Forged items are more a problem, as is pressed steel. You need big kit and expensive moulds to do those -- The biggest threat to humanity comes from socialism, which has utterly diverted our attention away from what really matters to our existential survival, to indulging in navel gazing and faux moral investigations into what the world ought to be, whilst we fail utterly to deal with what it actually is.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-10-17 22:34 -0400 |
| Message-ID | <2smdnYArA9BQYW_1nZ2dnZfqnPqdnZ2d@giganews.com> |
| In reply to | #76248 |
On 10/16/25 06:22, The Natural Philosopher wrote: > On 16/10/2025 06:00, c186282 wrote: >> On 10/15/25 06:59, The Natural Philosopher wrote: >>> On 15/10/2025 02:06, c186282 wrote: >>>> Ya know, with modern 3-D metal printing, somebody ought >>>> to sell one-off duplicates for almost every part for >>>> old cars. All they need are the original dimensions. >>>> Heat-treated parts, not that many in old vehicles, >>>> would be more of a challenge. >>> >>> In the UK every part is available for 1970s era MGBs and the old >>> Austin Healy Sprite, and you can build a brand new one. >>> As long as you have the paperwork to say its really 50 years old, and >>> so avoid emissions limits >> >> USA has no qualms about "how old". >> >> Too bad you live in a totalitarian country. >> > It is a very densely populated country and car exhaust pollution is a > major issue. Nonsense ... it all blows over onto the Frogs :-) > California piloted the use of fuel injection and catalytic converters > and eventually the EU legislation caught up. > > So cars with high pollution (carburettors, no catalysts )are banned > unless they are so old they count as 'classics' . Evil. "For political appearances" laws. >> Parts for vehicles maybe 1920 on CAN still >> be had. The problem is locating them and >> the PRICE. Of course "enthusiasts" care >> little for that. >> > Anything can be re-manufactured for a price...3D printing is excellent > for simple little plastic parts. > No one really makes carburettors for cars any more but they can be > reconditioned > > >> 1990 on, the ENGINES - the basic stuff - DID >> get much better. 1950s cars had a useful life >> of well under 100,000 miles - even assuming you >> did a couple of rebuilds. Of course in 1950 >> people didn't travel very far - and new cars >> were pretty cheap. >> >> So, in any case, I suggest the mentioned >> 3-D to-order fab as a viable business model. >> So long as you have the specs you can build >> compatible parts (esp if iron). Print, a >> little polishing, sell. As said, the >> enthusiasts WILL pay to keep that '47 Chevy >> truck running. >> > lol > >> I have no intention or will to START such >> a fab business - so I donate the idea. It >> is completely possible to do these days. >> > Actually multi-axis CNC milling machines are good for short runs. > Sand casting from 3D printed masters is possible Found a vid somewhere showing that being done ... the 'printer' makes the mold in fine detail and then you pour in the metal. Direct 3-D metal printing seems to be getting better faster and cheaper these days, so that may be better for 'short run' uses than CNC subtractive fabrication. > Forged items are more a problem, as is pressed steel. You need big kit > and expensive moulds to do those Fortunately the "heavy metal" is the least likely to go wrong unless you're in a serious crash.
[toc] | [prev] | [next] | [standalone]
| From | Richard Kettlewell <invalid@invalid.invalid> |
|---|---|
| Date | 2025-10-01 18:11 +0100 |
| Message-ID | <wwv3482h7ij.fsf@LkoBDZeT.terraraq.uk> |
| In reply to | #75500 |
ram@zedat.fu-berlin.de (Stefan Ram) writes:
> if (scanf("%259s", srcFile) != 1) {
> fprintf(stderr, "Failed to read source file name.\n");
> return EXIT_FAILURE;
> }
Mishandles filesnames with spaces in, or longer than the weird and
arbitrary 259-character limit.
--
https://www.greenend.org.uk/rjk/
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2025-10-01 21:06 +0000 |
| Message-ID | <10bk54h$k61q$2@dont-email.me> |
| In reply to | #75544 |
On 1 Oct 2025 17:21:55 GMT, Stefan Ram wrote: > That just shows, a coding chatbot really needs someone over its > shoulder who goes through the code, points out the flaws, and keeps > pressing on them until the code actually is written the way it > should. ... another chatbot?
[toc] | [prev] | [next] | [standalone]
| From | Nuno Silva <nunojsilva@invalid.invalid> |
|---|---|
| Date | 2025-10-01 23:45 +0100 |
| Message-ID | <10bkatm$l8iu$1@dont-email.me> |
| In reply to | #75569 |
On 2025-10-01, Lawrence D’Oliveiro wrote: > On 1 Oct 2025 17:21:55 GMT, Stefan Ram wrote: > >> That just shows, a coding chatbot really needs someone over its >> shoulder who goes through the code, points out the flaws, and keeps >> pressing on them until the code actually is written the way it >> should. > > ... another chatbot? Or maybe just get a competent programmer to do it and leave the boilerplate to proper automation if desired, not to Doubling-Down-As-A-Service. (Also, this naming choice explains why the approach of "pressing on them" may not work well with GenAI.) (Also: wouldn't this kind of pressing be a role for *training* the model, and not for users of an already trained model?) I'm starting to wonder if the regex "now you have two problems" remark [1] should be adapted for misuse of GenAI... and it seems I am not the first one to consider that [2] [3]. Paraphrasing Jamie Zawinski [1]: «Some people, when confronted with a problem, think "I know, I'll use GenAI!". Now they have two problems.» [1] https://regex.info/blog/2006-09-15/247 [2] https://mastodon.world/@GuyWithLag/112672830010202877 [3] https://ioc.exchange/@dabur/112247320088609260 -- Nuno Silva
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-10-01 22:19 -0400 |
| Message-ID | <saScnW9rz9WBfED1nZ2dnZfqn_adnZ2d@giganews.com> |
| In reply to | #75573 |
On 10/1/25 18:45, Nuno Silva wrote: > On 2025-10-01, Lawrence D’Oliveiro wrote: > >> On 1 Oct 2025 17:21:55 GMT, Stefan Ram wrote: >> >>> That just shows, a coding chatbot really needs someone over its >>> shoulder who goes through the code, points out the flaws, and keeps >>> pressing on them until the code actually is written the way it >>> should. >> >> ... another chatbot? > > Or maybe just get a competent programmer to do it and leave the > boilerplate to proper automation if desired NOT desired. Human coders are EXPENSIVE and ANNOYING and need health insurance and union pay and are infamous for telling bosses why you can't get there from here. > not to > Doubling-Down-As-A-Service. (Also, this naming choice explains why the > approach of "pressing on them" may not work well with GenAI.) > > (Also: wouldn't this kind of pressing be a role for *training* the > model, and not for users of an already trained model?) > > I'm starting to wonder if the regex "now you have two problems" > remark [1] should be adapted for misuse of GenAI... and it seems I am not > the first one to consider that [2] [3]. > > > Paraphrasing Jamie Zawinski [1]: > > «Some people, when confronted with a problem, think "I know, I'll use GenAI!". Now > they have two problems.» > > > [1] https://regex.info/blog/2006-09-15/247 > [2] https://mastodon.world/@GuyWithLag/112672830010202877 > [3] https://ioc.exchange/@dabur/112247320088609260 > IMHO, we're soon going to be in Deep Shit. AI code 'debugged' by other AIs ... sans any human sense of what is/can go wrong ....... Good code contains a lot of boilerplate to protect against what CAN go wrong - either with human input or odd-case errors and/or hack attempts. Some of those probs have to be 'intuited' - something no current AIs are good at. "If I was working for Vlad, how WOULD I attack this function/system ???" ... humans will have a clue. AI Claude won't. Note that even after all these years, M$ still posts warnings of simple buffer-overflow attacks every week. There are more sophisticated attack vectors than that. The upshot is that at any time Vlad and Xi can push the big shiny red button on their desks and Turn Off the 'west' - infrastructure, banking, govt, corps, comms, pretty much everything in an instant. We computerized everything for convenience - and now it can all be used against us. Tick, tick, tick ......
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-10-02 11:15 +0100 |
| Message-ID | <10bljbq$tpbv$5@dont-email.me> |
| In reply to | #75582 |
On 02/10/2025 03:19, c186282 wrote: > The upshot is that at any time Vlad and Xi can push > the big shiny red button on their desks and Turn Off > the 'west' - infrastructure, banking, govt, corps, > comms, pretty much everything in an instant. We > computerized everything for convenience - and now > it can all be used against us. Gosh. They really have done a good job with their US based agents, haven't they? Never mind. Even Vlad's favourite fawning propagandists are telling him its pretty much over... He will be gone reasonably soon Along with the Russian federation. -- Socialism is the philosophy of failure, the creed of ignorance and the gospel of envy. Its inherent virtue is the equal sharing of misery. Winston Churchill
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-10-01 21:59 -0400 |
| Message-ID | <m0qdnfTmQ-sXQUD1nZ2dnZfqnPhj4p2d@giganews.com> |
| In reply to | #75569 |
On 10/1/25 17:06, Lawrence D’Oliveiro wrote: > On 1 Oct 2025 17:21:55 GMT, Stefan Ram wrote: > >> That just shows, a coding chatbot really needs someone over its >> shoulder who goes through the code, points out the flaws, and keeps >> pressing on them until the code actually is written the way it >> should. > > ... another chatbot? Hmmmm ... code-writing bots being overseen by other code-writing bots ? :-)
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@vallor.earth> |
|---|---|
| Date | 2025-10-02 06:20 +0000 |
| Message-ID | <10bl5k2$qf1i$1@dont-email.me> |
| In reply to | #75569 |
At Wed, 1 Oct 2025 21:06:25 -0000 (UTC), Lawrence DâOliveir<ldo@nz.invalid> said: > On 1 Oct 2025 17:21:55 GMT, Stefan Ram wrote: > > > That just shows, a coding chatbot really needs someone over its > > shoulder who goes through the code, points out the flaws, and keeps > > pressing on them until the code actually is written the way it > > should. > > ... another chatbot? Not for my program. Someone in another group said they'd found a newsreader written in python, and had an LLM translate it to Rust. I figured, if he can do something like that, maybe I could do my newsreader project that I'd been thinking of. Call me quirky, but I wanted to write a newsreader in Tk/perl. Off and on, over the last 6 days, I've been writing it using ChatGPT5. Next feature I'm going to add is threading -- but not tonight. ;) I've learned 10 times more about Tk than I ever knew before. ObLinux: All its dependencies are available in the Linux Mint repositories, save one: Tk::MListbox. Fortunately, that is pure perl, and can live in as "vendor" subdirectory of the settings directory. (And it doesn't need it -- it's just that the overview pane looks and works much better with it.) Same screenshot, two sites: https://imgur.com/a/GQV0lhU https://ibb.co/BSqzXT5 -- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090Ti 24G OS: Linux 6.17.0 D: Mint 22.2 DE: Xfce 4.18 NVIDIA: 580.95.05 Mem: 258G "Is it ok to use my AM radio after NOON?"
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-10-02 03:05 -0400 |
| Message-ID | <saScnWVrz9WruUP1nZ2dnZfqn_YAAAAA@giganews.com> |
| In reply to | #75589 |
On 10/2/25 02:20, vallor wrote: > At Wed, 1 Oct 2025 21:06:25 -0000 (UTC), Lawrence DâOliveir<ldo@nz.invalid> said: > >> On 1 Oct 2025 17:21:55 GMT, Stefan Ram wrote: >> >>> That just shows, a coding chatbot really needs someone over its >>> shoulder who goes through the code, points out the flaws, and keeps >>> pressing on them until the code actually is written the way it >>> should. >> >> ... another chatbot? > > Not for my program. > > Someone in another group said they'd found a newsreader > written in python, and had an LLM translate it to Rust. > > I figured, if he can do something like that, maybe > I could do my newsreader project that I'd been thinking > of. > > Call me quirky, but I wanted to write a newsreader > in Tk/perl. Off and on, over the last 6 days, I've been writing > it using ChatGPT5. > > Next feature I'm going to add is threading -- but not tonight. ;) > > I've learned 10 times more about Tk than I ever knew before. > > ObLinux: > All its dependencies are available in the Linux Mint > repositories, save one: Tk::MListbox. Fortunately, > that is pure perl, and can live in as "vendor" subdirectory > of the settings directory. (And it doesn't need it -- it's > just that the overview pane looks and works much better with > it.) > > Same screenshot, two sites: > > https://imgur.com/a/GQV0lhU > > https://ibb.co/BSqzXT5 > But WHY would you want to do anything in Tk ??? And Perl :-( <puke>
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@vallor.earth> |
|---|---|
| Date | 2025-10-02 18:41 +0000 |
| Message-ID | <10bmh18$15kio$2@dont-email.me> |
| In reply to | #75591 |
At Thu, 2 Oct 2025 03:05:24 -0400, c186282 <c186282@nnada.net> said: > On 10/2/25 02:20, vallor wrote: > > At Wed, 1 Oct 2025 21:06:25 -0000 (UTC), Lawrence DâOliveir<ldo@nz.invalid> said> > > >> On 1 Oct 2025 17:21:55 GMT, Stefan Ram wrote: > >> > >>> That just shows, a coding chatbot really needs someone over its > >>> shoulder who goes through the code, points out the flaws, and keeps > >>> pressing on them until the code actually is written the way it > >>> should. > >> > >> ... another chatbot? > > > > Not for my program. > > > > Someone in another group said they'd found a newsreader > > written in python, and had an LLM translate it to Rust. > > > > I figured, if he can do something like that, maybe > > I could do my newsreader project that I'd been thinking > > of. > > > > Call me quirky, but I wanted to write a newsreader > > in Tk/perl. Off and on, over the last 6 days, I've been writing > > it using ChatGPT5. > > > > Next feature I'm going to add is threading -- but not tonight. ;) > > > > I've learned 10 times more about Tk than I ever knew before. > > > > ObLinux: > > All its dependencies are available in the Linux Mint > > repositories, save one: Tk::MListbox. Fortunately, > > that is pure perl, and can live in as "vendor" subdirectory > > of the settings directory. (And it doesn't need it -- it's > > just that the overview pane looks and works much better with > > it.) > > > > Same screenshot, two sites: > > > > https://imgur.com/a/GQV0lhU > > > > https://ibb.co/BSqzXT5 > > > > But WHY would you want to do anything in Tk ??? > > And Perl :-( <puke> Thank you for your well-thought and interesting reply. /s But seriously -- what programming in perl have you done for which you found it vomitorious? Also, see my recent post to answer the question "why?". -- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090Ti 24G OS: Linux 6.17.0 D: Mint 22.2 DE: Xfce 4.18 NVIDIA: 580.95.05 Mem: 258G "Read what I mean, not what I write."
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-10-02 07:26 +0000 |
| Message-ID | <mk6nq3F4kutU6@mid.individual.net> |
| In reply to | #75589 |
On Thu, 02 Oct 2025 06:20:50 +0000, vallor wrote: > I've learned 10 times more about Tk than I ever knew before. That's about 100 times more than I ever wanted to know. I've messed around with Tkinter a couple of times but greatly prefer PySide6. I'm pretty sure I have the O'Reily 'Learning Perl/Tk' around here someplace but I haven't used Perl in ages and see no reason to return to it.
[toc] | [prev] | [next] | [standalone]
| From | vallor <vallor@vallor.earth> |
|---|---|
| Date | 2025-10-02 18:37 +0000 |
| Message-ID | <10bmgot$15kio$1@dont-email.me> |
| In reply to | #75593 |
At 2 Oct 2025 07:26:59 GMT, rbowman <bowman@montana.com> said: > On Thu, 02 Oct 2025 06:20:50 +0000, vallor wrote: > > > I've learned 10 times more about Tk than I ever knew before. > > That's about 100 times more than I ever wanted to know. I've messed > around with Tkinter a couple of times but greatly prefer PySide6. > > I'm pretty sure I have the O'Reily 'Learning Perl/Tk' around here > someplace but I haven't used Perl in ages and see no reason to return > to it. Since the 90's, we (my company) have used perl on our backends. With a few caveats...for example, we have a special exception-handling class that Carp()'s if it goes out of scope without being checked-in with. And I think all the arguments (and hazards) for what Microsoft calls "managed code" apply to perl. The new fashion is to bag on perl because (reasons). One of those reasons is inscrutable code...which is more a testament to the programmer's ability than the language itself. Perl can be written to be less obtuse -- see "C" for another example of a language that can be made needlessly opaque. Anyway, because of several decades of experience writing perl, it's a good fit for my own personal project. I may translate it into C++/Gtk later, I don't know. As far as Tk goes, I picked that because it integrates well with perl, and everything needed is in the Linux Mint repositories. (Well, except one module, which is pure perl and readily available on cpan.) Also, Mrs. vallor has expressed interest in the project, and in Usenet in general. She has a new Linux workstation in her office, but her daily driver is (still?) a Mac Studio. MacOS has both Tk and perl. So once I've got this thing put together, I'm going to try to get it running on MacOS. (Worse comes to worse, she can use XQuartz and run it off a Linux workstation, either hers or mine.) If the project fizzles, she may end up running pan. We'll see. But the short answer is: perl has always been my go-to language, but I use C when I need high-performance. And finally: say what you will about him, I think Larry Wall is a genius. -- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090Ti 24G OS: Linux 6.17.0 D: Mint 22.2 DE: Xfce 4.18 NVIDIA: 580.95.05 Mem: 258G ""Apple" (c) Copyright 1767, Sir Isaac Newton."
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-10-03 00:29 -0400 |
| Message-ID | <7fidnTQOZKazzEL1nZ2dnZfqnPGdnZ2d@giganews.com> |
| In reply to | #75615 |
On 10/2/25 14:37, vallor wrote: > At 2 Oct 2025 07:26:59 GMT, rbowman <bowman@montana.com> said: > >> On Thu, 02 Oct 2025 06:20:50 +0000, vallor wrote: >> >>> I've learned 10 times more about Tk than I ever knew before. >> >> That's about 100 times more than I ever wanted to know. I've messed >> around with Tkinter a couple of times but greatly prefer PySide6. >> >> I'm pretty sure I have the O'Reily 'Learning Perl/Tk' around here >> someplace but I haven't used Perl in ages and see no reason to return >> to it. > > Since the 90's, we (my company) have used perl on our backends. Perl ... AAAAAAUUUGGGGGHH !!! Won't touch it. Camel dung. > With a > few caveats...for example, we have a special exception-handling class > that Carp()'s if it goes out of scope without being checked-in with. > And I think all the arguments (and hazards) for what Microsoft calls > "managed code" apply to perl. > > The new fashion is to bag on perl because (reasons). One > of those reasons is inscrutable code...which is more a testament > to the programmer's ability than the language itself. Perl > can be written to be less obtuse -- see "C" for another > example of a language that can be made needlessly opaque. > > Anyway, because of several decades of experience writing > perl, it's a good fit for my own personal project. I may > translate it into C++/Gtk later, I don't know. > > As far as Tk goes, I picked that because it integrates well > with perl, and everything needed is in the Linux Mint repositories. > (Well, except one module, which is pure perl and readily available > on cpan.) > > Also, Mrs. vallor has expressed interest in the project, > and in Usenet in general. She has a new Linux workstation > in her office, but her daily driver is (still?) a Mac Studio. > MacOS has both Tk and perl. So once I've got this thing put > together, I'm going to try to get it running on MacOS. > (Worse comes to worse, she can use XQuartz and run it > off a Linux workstation, either hers or mine.) If the > project fizzles, she may end up running pan. We'll see. > > But the short answer is: perl has always been my go-to > language, but I use C when I need high-performance. > > And finally: say what you will about him, I think Larry Wall is > a genius. Look, Tk is Just Fine and has all the tweaks you'll ever need. Also VERY well documented. My next Python GUI app - it'll be Tk.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-10-03 05:06 +0000 |
| Message-ID | <mk93veFj5bqU1@mid.individual.net> |
| In reply to | #75635 |
On Fri, 3 Oct 2025 00:29:32 -0400, c186282 wrote: > Perl ... AAAAAAUUUGGGGGHH !!! > > Won't touch it. > > Camel dung. https://www.tiobe.com/tiobe-index/ I don't remember a tiobe index for the month starting with WTF? I don't know if I buy the theory that someone finally drove a stake through Raku's heart. Only Hurd has been a bad joke longer than Perl 6. At this point I can't remember why I switched to Python. Maybe because Esri started using it as a scripting language? I did like the DBI concept and it doesn't have some of the annoying Python formatting quirks. However it had a bushel of its own quirks. I only have a passing familiarity with sed, awk, and some of the other stuff Wall rolled into the language.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2025-10-03 01:24 -0400 |
| Message-ID | <7fidnTMOZKa7w0L1nZ2dnZfqnPGdnZ2d@giganews.com> |
| In reply to | #75639 |
On 10/3/25 01:06, rbowman wrote: > On Fri, 3 Oct 2025 00:29:32 -0400, c186282 wrote: > >> Perl ... AAAAAAUUUGGGGGHH !!! >> >> Won't touch it. >> >> Camel dung. > > https://www.tiobe.com/tiobe-index/ > > I don't remember a tiobe index for the month starting with WTF? I don't > know if I buy the theory that someone finally drove a stake through Raku's > heart. Only Hurd has been a bad joke longer than Perl 6. > > At this point I can't remember why I switched to Python. Maybe because > Esri started using it as a scripting language? I did like the DBI concept > and it doesn't have some of the annoying Python formatting quirks. However > it had a bushel of its own quirks. I only have a passing familiarity with > sed, awk, and some of the other stuff Wall rolled into the language. Python is now VERY good ... can do almost anything you can do with 'C' - but with more comprehensible syntax. So, don't cuss Python. Anything I write, I always proto in Python. Then, maybe, I re-write in 'C' or Pascal. If it's not "too" I might re-do in FORTRAN just for fun. "Speed" is the main reason for re-do in compiled langs - not 'function'.
[toc] | [prev] | [next] | [standalone]
Page 13 of 16 — ← Prev page 1 … 11 12 [13] 14 15 16 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web