Would be nice to NOT use Chromium for the client

[UnBeatWater]

I absolutely hate Google (and for good reason), so it could be nice maybe trying out Gecko instead, or something that isn't support by a big tech company (eg. Goggles, ApplePieces or FaceMetaBooks).

[rawWwRrr]

Chromium Embedded Framework is not even Google's. They provide a lot of resources to it which in turn may steer the ship more towards Google's roadmap, but it is not owned by Google. And Steam's been using it for several years now.

[Malfunctioning Robot]

rawWwRrr の投稿を引用：

Chromium Embedded Framework is not even Google's. They provide a lot of resources to it which in turn may steer the ship more towards Google's roadmap, but it is not owned by Google. And Steam's been using it for several years now.

If by several years we mean a decade+? lol

[Pscht]

OP's picture reminds me of the MacOS logo, just saying.

[rawWwRrr]

Malfunctioning Robot の投稿を引用：

rawWwRrr の投稿を引用：

Chromium Embedded Framework is not even Google's. They provide a lot of resources to it which in turn may steer the ship more towards Google's roadmap, but it is not owned by Google. And Steam's been using it for several years now.

If by several years we mean a decade+? lol

A decade is several, yes.

[UnBeatWater]

Pscht の投稿を引用：

OP's picture reminds me of the MacOS logo, just saying.

Old ♥♥♥♥ I haven't gotten around to replacing.

[UnBeatWater]

rawWwRrr の投稿を引用：

Chromium Embedded Framework is not even Google's. They provide a lot of resources to it which in turn may steer the ship more towards Google's roadmap, but it is not owned by Google. And Steam's been using it for several years now.

Mainly posting because now it's basically ALL just Chromium, which I'll say it, isn't completely attached to google. And plus it could be a cool experiment, to see if you can completely swap it out with something else and see how Steam runs. Fyi, I don't like to see that ♥♥♥♥♥♥♥ Chromium logo in my Volume Mixer.

[Mad Scientist]

I have been somewhat vocal about this in the past. Overall I would prefer custom code over chromium. "mainly developed and maintained by Google" is usually something indicative of not being the best out there or having the best interest even if open source.

The least they could do us some basic web code for mobile users so the size/scale setting change isn't necessary when not using the app.

[UnBeatWater]

Mad Scientist の投稿を引用：

I have been somewhat vocal about this in the past. Overall I would prefer custom code over chromium. "mainly developed and maintained by Google" is usually something indicative of not being the best out there or having the best interest even if open source.

The least they could do us some basic web code for mobile users so the size/scale setting change isn't necessary when not using the app.

You are right, infact I'm posting this reply from my phone and the app is just so awful.

[Mad Scientist]

unbeatwater の投稿を引用：

Mad Scientist の投稿を引用：

I have been somewhat vocal about this in the past. Overall I would prefer custom code over chromium. "mainly developed and maintained by Google" is usually something indicative of not being the best out there or having the best interest even if open source.

The least they could do us some basic web code for mobile users so the size/scale setting change isn't necessary when not using the app.

You are right, infact I'm posting this reply from my phone and the app is just so awful.

The old app was way better. This new 2 apps to do the same thing seems odd. That and its incredibly easy for the new app to switch pages on you due to how close it is to where you type. Can't tell you how many posts I've lost be ause of that, whereas the pc client you just hit back and what you wrote is still there.

I'm still fairly amazed they didn't switch to just hand coding, but I'm not too surprised when people use others framework because it's easier from a more lazy perspective.

[Start_Running]

And what happens when Gecko becomes a big company hmmm?

[Azure Fang]

Start_Running の投稿を引用：

And what happens when Gecko becomes a big company hmmm?

Depends. If they continue like the Linux project, nothing will happen. If they continue like Arduino, a ton of corporate bureaucracy will occur and they'll lose a ton of their consumerbase to other projects overnight. So far, the Mozilla Foundation and Gecko have stayed open, so the former is more likely. Can't pass judgement on "what ifs".

CES is a risk, considering Google's heavy control of its codebase, but it is ostensibly still an open project. Much like Xinput, its popularity as a framework comes from its ease of integration and robust featureset (sounds a lot like Steam's call to popularity). If a more attractive alternative were to appear with ease of migration, I'm more than certain Valve would jump at it to continue to advance the service.

What Valve could do is migrate from Chromium to Ungoogled-Chromium, but I'd hazard a guess that they make use of some of OG Chromium's embedded analytics.

[William Shakesman]

The issue is that browsers are so complex as to be almost little operating systems now. Unless Valves writes something that parses its own store in a unique manner, to make a proper browser that is secure is a lot of effort when you can just copy Chrome.

As you've learned, Chrome is ♥♥♥♥♥♥♥ trash. And Valve isn't any better at copying Chrome than they are building their own (No seriously they are the back button is just functioning precisely as Valve intends. Gamers love random chance right?!) but the issue is still a rock and a hard place and the real problem is the feature creep of the modern browser is awful.

That having been said, Amazon's app doesn't have these problems, so it's certainly not a carte blanche excuse.

[Start_Running]

Azure Fang の投稿を引用：

Start_Running の投稿を引用：

And what happens when Gecko becomes a big company hmmm?

Depends. If they continue like the Linux project, nothing will happen.

It wouldn't. See once you have to start hiring people and gain a certain size well things become inevitable.

Fishie の投稿を引用：

What Valve could do is migrate from Chromium to Ungoogled-Chromium, but I'd hazard a guess that they make use of some of OG Chromium's embedded analytics.

And then they'd have to build in the features and frameworks they want and basically spend a butload of cash and time just to get back to this point where you'll be making the same complaints.

[Satoru]

Mad Scientist の投稿を引用：

I have been somewhat vocal about this in the past. Overall I would prefer custom code over chromium. "mainly developed and maintained by Google" is usually something indicative of not being the best out there or having the best interest even if open source.

The least they could do us some basic web code for mobile users so the size/scale setting change isn't necessary when not using the app.

Microsoft, a company with more resources and money than most countries, gave up making their own browser engine. This is a company that burned BILLIONS of dollars every year on their Xbox division for a DECADE.

What makes you think any non Fortune 5 company can even maintain one now. It’s either Chrome, Apple WebKit, or Firefox. And Firefox is a dumpster fire.

Everyone uses Chromium for a reason

[RiO]

Satoru の投稿を引用：

What makes you think any non Fortune 5 company can even maintain one now. It’s either Chrome, Apple WebKit, or Firefox. And Firefox is a dumpster fire.

Everyone uses Chromium for a reason

Everyone uses Chromium because everyone uses Chromium.
The reason is literally cyclic reasoning. They reached critical market volume which causes a feedback loop where the entire industry itself is focusing first and foremost, or even only, on supporting Chromium along with all the (many times non-standard) features that Google forces into it.

This should sound familiar if you've lived through the digital '90s.
"Best viewed with Internet Explorer," remember?

Google built up that market share by being the fastest, snappiest, and modern browser there was. And by heavily, h-e-a-v-i-l-y pushing developer advocacy based on the promise of all the non-standard new-and-shinies they'd been adding to it, to get developers to grassroots for Chrome within their companies.

Simultaneously, they reduced funding to Mozilla as Chrome's star was rising - which squeezed Firefox and pretty much ensured that Firefox had to settle into a slower rhythm where it just couldn't keep up anymore.

Microsoft switching from EdgeHTML to Chromium/Blink as the underlying stack for Edge was done out of consideration for spending resources, but also because developing directly on Chromium next to Google as the second largest body invested in the Chromium project gave them more sway over the project than most other smaller development partners would. It's what allowed to exert some control over what Google is using Chromium for and where it wants to take it.

Safari meanwhile started cocooning and withdrew back to its own platforms.
Also- if we want to talk 'dumpster fire' then Safari has far more claim to that title than Firefox. The amount of missing; incomplete; and outright broken features that have festered in Safari for literally decades is painfully embarrassing.