Chromium: Improve support for Nintendo Switch gamepads
chromium-review.googlesource.com
chromium-review.googlesource.com
* Windows
* Mac
* ChromeOS
* Linux
* Mobile
...overnight. Pretty compelling way to draw in new users given millions of people already own a Switch controller and could start without needing to buy Google's one.
Also, I don't know if it's commonplace anymore, but I remember in the past a lot of people that worked on Chrome had @chromium.org addresses, too.
Some relevant links are https://opensource.google.com/docs/releasing/ for the personal-project-with-Google-copyright flow and https://opensource.google.com/docs/iarc/ for the personal-copyright flow.
A number of companies, both startups and established game companies, have tried this. It's not taken off because you can't beat latency.
Of course, it's technically involved to make a local client for every video game they want to support. With local echo or even YouTube the scope of the problem is smaller.
I'm still not convinced it can be commercially successful though: not that many people have a good enough connection, and most people who care about games at all will already have a better way to play them.
https://chromium-review.googlesource.com/c/chromium/src/+/15...
e.g: switch_pro_4, dualshock_ps4_, ...
It does not happen for all variables, what is this convention? :o
https://google.github.io/styleguide/cppguide.html#Variable_N...
Seeing 'this' unambiguously implies instance variable. Otherwise you have to spot the underscore and be aware of the conventions in the codebase. A good IDE should highlight class variables vs locals, though.
On the other hand code can get really messy with boilerplate like this everywhere, and I personally agree with you. Although I believe Google also promotes human-readable variables over less typing.
int area(int width) {
return width * height;
}
What is "height". Is it a global variable? variable in some outer scope? A member/property of the current object? Absolutely no idea.> scope where both this->foo and foo are valid and it's unclear which is which
Ideally you'd turn on the compiler option to warn about scope hiding.
Eg void set_foo(int foo) {this->foo = foo;}
The controllers have both been plagued by the issue of dust entering the analog sticks, making it drift. You can't calibrate this away (tried it). Nor did it for us help with a spray can of air to blow it away, but perhaps I was holding it wrong (snark). Had to send it away for repair and they changed both analog sticks.
A new set of controllers (ie two sticks) also cost almost twice what an official PS4 dualshock controller costs. A single costs about as much as a PS4DS. Also, the PS4 one feels so much more robust.
For a controller that is meant to be used on the go, I find the poor dust-resistance and high cost of replacement very off-putting. I get the feeling that they, or something else on the switch, is gonna break again soon.
Puh, sorry for the rant.
Dragging my Switch everywhere haven’t had a single problem ever with my joy cons not with the pro Controller. Friends had problems, got their joy cons replaced - all good now.
If the latter, it's just a question of time before one has to do the same ordeal again. I'd prefer the problem not to arise in the first place. But good thing Nintendo are generous with replacements.
* you know, like saying "oh this issue is really bothing me but no I won't change them because it would just happen again anyway I'm sure of it even though most of others aren't affected". This is a definite case of "the user is not looking for a solution, but for a chance to rant", we've all seen it one time or another
Completely agree re: costs though. 80$ for the pro controller is 30$ too much. Joycons too.
I still loved donkey kong and zelda and mario. I accepted, at that point, that nintendo just sucks in developing hardware.
The usb c port is btw. on the bottom. you can't play and load your switch without having something which keeps that cable away if you like to use the little stand feature of your switch. Smart right?
The only problem is that A/B and X/Y is different between Xbox and Nintendo controller and you need to press B when the game tells you to press A. But it's a minor issue.
Do you know which one you had?
It's also different with Xbox and PS4 controllers. It's something I got used to a while ago after using DS3 controllers in Windows games.
Lots of PC games nowadays detect PS4 controllers and properly adjust UI (or even work with the lightbar), but I doubt Project Stream / browser controller APIs get that level of info.
- Switch doesn't even have a browser (it does technically, but it's internally used and you need to hack the switch to be able to use the browser)
- Nintendo could easily change this if they wanted, of course, but considering their history of tight control over the platform, I don't think they'd be willing.
None of my friends know c++
But all of them know Go or Rust.
I'm in a bubble too. I couldn't name a single friend or colleague who uses Rust or Go.
Just for example, scanning the jobs in my city the most in demand are c#, java and c++ in that order.