Deutsch   English   Français   Italiano  
<lngi3pFs9nrU1@mid.individual.net>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.advocacy
Subject: Re: Qualcomm cancels Windows dev kit PC
Date: 19 Oct 2024 01:59:21 GMT
Lines: 33
Message-ID: <lngi3pFs9nrU1@mid.individual.net>
References: <lne5rqFh2g9U3@mid.individual.net> <vesq10$35da7$1@dont-email.me>
	<lne969Fh72qU5@mid.individual.net> <vesrvb$35nh1$1@dont-email.me>
	<lnfq59Fog9vU1@mid.individual.net> <veukcm$3fkh5$8@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net vOKtTxMZS8KVY/CCsvdV9QVv0upuBMiO1ZiTRu7hLWQ1jtZeJ9
Cancel-Lock: sha1:CnjtW0OZxdnklaeVO/mXfObj0wY= sha256:KaKgSSW/p0mQeiqARyaH32deXGEXKiTrUDgKNHvkdSE=
User-Agent: Pan/0.149 (Bellevue; 4c157ba)
Bytes: 2236

On Fri, 18 Oct 2024 21:36:22 -0000 (UTC), Lawrence D'Oliveiro wrote:

> The *nix ecosystem also has thousands of “must have” applications, and
> it is older than Windows or even MS-DOS. Yet it has evolved in a much
> more graceful fashion.

MS has done their best to preserve backward compatibility. Others aren't 
as reluctant to break stuff.

I upgraded my work Windows box to Python 3.13 Wednesday. For a quick and 
dirty test I went into a project that used CherryPy.

https://docs.cherrypy.dev/en/latest/

It's old and doesn't have all the bells and whistles of Django (and 
opinions) and has been overtaken by Flask. It didn't work. Deep in the 
bowels of CherryPy there was a reference to 'cgi'. When they shook the 
tree for 3.13 'cgi' fell out. 

Fuck! After a little side expedition to StackExchange and other sites, 

'python -m pip install legacy-cgi' 

rescued the day. 

I realize it's a trade between move fast and break stuff and being stuck 
in the mud forever but there are trades. It caught up in the last release 
but QGIS wasn't happy with 'Wayland only'. It worked for what I was doing 
but it did warn some dialogs might not work correctly. iirc Qt6 was 
delayed a bit while the maintainers tried to get it to play nice. 

I've said it before but my production Linux box is boring old Debian 
because i don't like surprises.