Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
it use's HTML, JavaScript and CSS
so it's just a web browser, given a fancy name
it accepts the same lines of code as chrome/firefox/etc for displaying webpages/web app's
so if we could disasemble the new version of steam, you could launch chrome in developer mode, or use firefox developer edition, insert the code into it, and have all the new features and access to your library inside of a web browser
twitch use's it, discord uses it, itch.io uses it just to name a few
can download there programs or just visit sites via web browser, doesn't seem like it would be hard for valve to do since they already have the framework in place
Believe me, Electron is extremely cheap solution, used for non demanding markets (eg. like kids, teenagers), but believe me again, everything is better then 2 decades ancient code based on Chromium like Steam client today. The current Steam client is only suitable for blowing away (in its entirety). The best part is that as of 2019, this programming monstrosity hasn't changed even a step. It's still the same junk. But how many revisions and versions there were during that time. What a development! What a joke.
No. It's just the UI which is in Chromium. That UI interfaces with a native code, written in C++, backend in the client which does stuff like game downloads and lots of other stuff. If you try to load the UI in another web browser, like Chrome, the native code backend is missing so the UI doesn't work at all.
Often enough. YouTube 1080p and 4K content comes to mind.
And it goes just as fast as it goes through Steam, which is also just HTTP(S) traffic.
For very obvious reasons*, browsers don't get arbitrary file system access.
The web platform does give them access to a sandboxed file system using the File and Directory Entries API. But files written within that sandbox are flagged non-executable. Again: for the same very obvious reasons*.
For these particular use cases though; you would best use a native headless service installed on the local system. And said service could connect to the client's UI running in a web browser, through a custom protocol handler. (Steam actually already has one.)
*) reducing malware attack surface
In-page overlays, just like Steam implements many of them today.
Or failing that, just opened as new tabs.
Why couldn't I have one browser tab with my library; and two or three with various community threads? Seems perfect really.