Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
Newsgroups: comp.sys.ibm.pc.games.action
Subject: Re: Steam finally kills Win7/8 support
Date: Sun, 1 Dec 2024 21:00:08 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 49
Message-ID: <slrnvkpj65.32a2r.candycanearter07@candydeb.host.invalid>
References: <aba9kj9ilnm1s1rqj6e8iikhpg7tn4klea@4ax.com>
 <tjl9kj1h3svvu967vot5gp9acuomn4r723@4ax.com> <vi6ptr$3up8k$2@dont-email.me>
 <8oeekj1t1l2n2jpllv1b36jd5ofncv20b1@4ax.com>
 <gipekj1lrrglt9br5hs5qsouus8m8igl3q@4ax.com>
 <slrnvkkqe0.rdh.candycanearter07@candydeb.host.invalid>
 <krbmkjd9uj5f0bash31a6mrmqpgelskll2@4ax.com>
Injection-Date: Sun, 01 Dec 2024 22:00:08 +0100 (CET)
Injection-Info: dont-email.me; posting-host="f26f6481281c9784097093ad6805a85f";
	logging-data="2945738"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1953kFAWvQ/H2ttgrdKOheQSD3DYyQxdHhb4v6FRoa+PQ=="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:MXFj0YvsBD5Uz6cUe20iIwkh9PQ=
X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]%
 b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx
 `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e
 ZrQsWJ >|l^I_[pbsIqwoz.WGA]<D
Bytes: 3739

Spalls Hurgenson <spallshurgenson@gmail.com> wrote at 15:40 this Saturday (GMT):
> On Sat, 30 Nov 2024 01:30:07 -0000 (UTC), candycanearter07
><candycanearter07@candycanearter07.nomail.afraid> wrote:
>
>>Zaghadka <zaghadka@hotmail.com> wrote at 18:38 this Wednesday (GMT):
>>> On Wed, 27 Nov 2024 10:37:12 -0500, in comp.sys.ibm.pc.games.action,
>>> Spalls Hurgenson wrote: 
>>>
>>>>these deprecations aren't directly
>>>>caused by Valve, but by their use of Chromium as the underlying
>>>>framework in Steam.
>>>
>>> OH! Okay, that makes perfect sense. I forgot that there was 3rd party
>>> browser code in Steam.
>>>
>>> So they literally can't fix security holes. They'd have to release an "at
>>> your own risk" version.
>>
>>
>>Isn't chrome(ium) open source?
>
> Yes it is.
>
> So Valve _could_ retroactively add support for older operating systems
> into their client. Doing so would constitute an an entirely new branch
> of the browser, however, and half the point of using a third-party
> browser is so you don't have to maintain it yourself, but can just
> download the updated source to use in your project whenever you need
> it. Although there is actually already a branch of Chromium for 
> older Windows versions that is reguarly updated called Supermium that
> they could use. But I doubt that is as vigorously tested as the core
> Chromium code.
>
> But the Chrome thing also gives Valve excuse not to have to support
> older operating systems anymore. You don't need to worry about
> problems --and create workarounds-- for issues that only occur on
> older operating systems. From all we've heard about Valve's internals,
> they don't really have good structure for things like maintenance of
> older projects; it's all about the 'latest and greatest' fad, and
> infrastructure projects are lowest-totem-pole assignments. So ensuring
> old code remains good code isn't a priority there. Nobody there wants
> to ensure that Steam keeps running on old WinXP machines, so nobody
> does it. And if a few customers get shafted, well, them's the breaks.


We already know they don't do maintenance much, look at TF2's issues or
completely deleting CSGO for the sequel.
-- 
user <candycane> is generated from /dev/urandom