Steam installieren
Anmelden
|
Sprache
简体中文 (Vereinfachtes Chinesisch)
繁體中文 (Traditionelles Chinesisch)
日本語 (Japanisch)
한국어 (Koreanisch)
ไทย (Thai)
Български (Bulgarisch)
Čeština (Tschechisch)
Dansk (Dänisch)
English (Englisch)
Español – España (Spanisch – Spanien)
Español – Latinoamérica (Lateinamerikanisches Spanisch)
Ελληνικά (Griechisch)
Français (Französisch)
Italiano (Italienisch)
Bahasa Indonesia (Indonesisch)
Magyar (Ungarisch)
Nederlands (Niederländisch)
Norsk (Norwegisch)
Polski (Polnisch)
Português – Portugal (Portugiesisch – Portugal)
Português – Brasil (Portugiesisch – Brasilien)
Română (Rumänisch)
Русский (Russisch)
Suomi (Finnisch)
Svenska (Schwedisch)
Türkçe (Türkisch)
Tiếng Việt (Vietnamesisch)
Українська (Ukrainisch)
Ein Übersetzungsproblem melden
Diskussionsregeln
Diesen Beitrag melden
im on about you and the other person, constantly spouting nonsense on a topic you have no clue what you are talking about.
That's ironic.
yep, sure is.
It is simply another "stop liking things that I hate" mentality post. Thankfully block exists.
ok..
892.2mb here... i dont seem to get drops
or steady ram usage or resets unless i reset steam..
always on the rise...
I mean, the post isn't against the rules.
they both tried saying steam doesnt have a memory leak and that no one aside from win 7 users are "having an issue", yet clearly people from 7/8/10/11 are all reporting the same issues, be it here on steam or outside of it.
one even saying that after being shown proof they were wrong and made a comment basically saying "honesty isnt part of this conversation".
but im still wondering... where this "hating things others dont like"? cause i didnt see any of that?
for what?
The decision to drop Win7 support is a political one, not a technical necessity.
How is it political?
First, by "political decision", I mean an arbitrary one. Possibly encouraged by monetary incentives from Microsoft, but who knows.
People are going to whine about development efforts and keeping things "safe" and whatnot, and that Valve cannot do that. Yes, but they don't have to either, so I'm not talking about that.
.. eh, why doesn't Valve need to? Because, basically, they can just go the "least effort" route. Win7 has been officially discontinued for some time now, so nobody is going to blame them if they don't give you a 100% Steam client.
So, what does our Win7 client actually need? Which features are absolutely must-have? There's really only just two: downloading games, and running games. It would probably be neat if they had a decent way to choose which game to download/run, though.
Even if that MVP requires an embedded web-browser to keep development costs down, that browser does not need to be "safe" because -- being a minimum client -- that webbrowser does not need to be able to access anything other than Steam servers. And we can assume Valve isn't going to put malware on their servers; they have easier ways to break into your system.
Development is rather simple, since they have a client that does everything and runs on Win7 -- we are all using it. They would just have to "freeze" that one, remove everything they don't need on the MVP, change the user agent and the version used for the client connection, give it a different update channel that will rarely be used, and bang -- done.
There is some need for support on their side, of course. If they want to change the way logins work, downloads, or how games/clients interact with Steam features such as achievements, they'll have to update the MVP client as well, or keep both systems active concurrently. This will certainly mean some extra work if they start using bleeding edge Javascript/HTML on stuff that the MVP client is using -- since they can't update the browser embedded into the MVP client, they will have to maintain two versions of these pages.
However, in reality, these pages are generated from a database; they'll just have to keep the old page generator around for the MVP client, and only use the new one for the big client. They will have to put in a few minutes of extra work the first time this diversion happens, though -- they'll have to add an "if (MVP) ... else ..." somewhere, to select between the MVP version and the bleeding-edge one.
If they put new stuff into the pages that the old generator doesn't know about... who cares, this is an MVP, and if we could survive without that new stuff for decades, we don't need it.
Also, compared to Apple, Microsoft has an excellent track record of keeping their operating systems compatible. The initial MVP-client, whether it targets Win7 or even WinXP, will likely not cause problems with Win12, Win14, Win15, Win17, ... if it does, I can't speculate on the best course of action since my crystal ball doesn't work so I can't know what the problem will be, but they'll probably just have to fix it. Or, when they look at actual client usage, they might have spotted 0 uses of XP during the previous decade, so they might decide to finally drop that for good.
(Meanwhile Chrome is sucking up 1.5GB!)