Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: Python/C/Pascal ... How To Choose ? Date: 10 Nov 2025 21:01:55 GMT Lines: 32 Message-ID: References: <10eqid5$3du22$1@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net wMUz1vdKCI5ddX4RQxA8HAHA9mxAv6YZed/V83lm31ILyizh5e Cancel-Lock: sha1:fJ1DLnjfjW9OkfOXwtQghEN9FLs= sha256:XFYVPNg0tDxfwAqvIKOHgXllMWPlL79cNtlVZ8Uo85k= User-Agent: Pan/0.162 (Pokrosvk) Xref: csiph.com comp.os.linux.misc:77279 On Mon, 10 Nov 2025 08:57:36 +0100, Carlos E.R. wrote: > On 2025-11-09 21:13, Diego Garcia wrote: >> On Sun, 9 Nov 2025 09:18:26 -0800, Bobbie Sellers wrote: >> >> >>> But programming being solely about Speed seems a bit off to me. >>> >>> >> All that I can say in response is that you must not do much audio/video >> processing or very large file processing or large software compiling >> because each of these activities can make a person SCREAM for more >> SPEED. > > Not really. > > Having waited hours for an 8086 to process a drawing in Autocad, that a > video takes a few minutes to process doesn't worry me. There was a point, maybe 8 to 10 years ago where most tasks including compiling our entire source tree went from 'go out for lunch' to a few minutes. Since then there have been performance improvements but unless you're timing the operation they really aren't noticeable. There are bottlenecks other than processor speed. Many of our sites used SQL Server for geodata, which meant network calls to the server. Esri came out with a FileGDB system where the geodata was stored on each client machine that was a good deal faster. The trade off in that case was changes to the geodata had to be copied to each machine rather than just in the SQL Server instance. The increasing trend to do everything in the 'cloud' introduces problems.