Hacker News Reader

Interesting that people voluntarily pay. Write-up of bloggers doing the "buy me a coffee" button suggested to me that nobody pays like that.

I guess software is a bit more tangible than a blog post even if both have value.

One difference I can see is the "buy me a coffee" button isn't a "these are the people who bought me a coffee" list. I imagine most of these sponsors (from their perspective) are paying for advertising.

Ah good point

Sounds like good advertising! If these companies are trying to sell hardware corresponding to this software, then having a callout right in the software's README is a great way to attract people who are discovering the project through GitHub. This wouldn't work as well if the product was oriented toward non-technical people (not discovering it through GitHub) or if the software wasn't directly related to the hardware (most OSS projects are probably run on general-purpose hardware).

This actually made me happy, considering all the bad news lately:

> I even got a Chinese company, notorious for selling "clone" of OSHW projects, to support the SW development as well via GitHub sponsor.

I suppose that's RetroScaler?

What controllers you would recommend for retro games with a great d-pad and buttons? I can't find anything that's even remotely close to native controllers especially for Super NES.

Nintendo Switch SNES controller?

Otherwise personally my daily driver is PS5 DualSense

I've never managed to find a Wii-connector-to-USB adapter that wouldn't inexplicably die within six months, but the 1st-party SNES Classic controllers are basically perfect clones of the original. Ditto the NES versions they have. Wii Pro Controllers are also great and have a similar feel & quality, but with modern ergonomics (no rumble, though, so not great for e.g. Playstation games, and IIRC the triggers aren't analog, which is limiting)

You can connect Wiimotes to PCs over Bluetooth and use any of those Wii-connector controllers through them, which would make them wireless and solve the finding-a-reliable-adapter problem, but I've never managed to make that kind of set-up sufficiently stable. Always having to screw with re-pairing and such.

In the end, my go-to for BT emulation controllers is usually a PS3/4/5 controller. I haven't tried the XBone but I found the d-pad on the XB and XB360 controllers unusably inaccurate, and the face buttons weirdly slow when trying to play old-school Nintendo-hard games. Playstation controller d-pads are much better, and the face buttons feel quicker to switch between, for whatever reason.

For d-pads on Xbox controllers, you can cut a cross out of an old plastic folder and wedge it between the plastic and the membrane for better feel. It makes the pad crispy. 10/10 all my old controllers have it, too bad no one to play halo3 with. :(

https://www.8bitdo.com/pro2/ The ps2 and the SNES had a baby and it is a marvelous baby. (They sell them at Best Buy as well)

It has: Turbo key function for SNES games, Vibration, Macros, Pressure-sensitive triggers, Multi-system support (there is a switch on the bottom that changes the signal from windows to Mac to Linux mode and so on), And it just werks.

I like RetroBit's Sega Genesis bluetooth controllers. They feel substantially similar enough to the originals.

Something to look out for with retro gaming is a lot of modern controllers have increased latency, which can be frustrating on games that require precision. Unfortunately, the Nintendo Switch Online SNES controller isn't great in this regard. You can use this tool[0] to check latency.

Personally, I use an original Super NES controller + a Timville triple controller adapter[1], but a more modern controller that I like is the 8bitdo SN30 Pro+. I primarily play on a PVM via a MiSTer, so your use case may be quite different.

[0] https://rpubs.com/misteraddons/inputlatency [1] https://www.tindie.com/products/timville/triple-controller-c...

I recommend the PS5 controller! They're very available (unlike the console), come in a few colours, and are regularly on sale -- about $90AUD in my currency.

They're rugged, reliable, pair easily via bluetooth without any custom software required (just hold the PS button and menu button together), and have excellent button feel. I grew up on the super Nintendo so I'm picky at times.

Battery life is excellent, reported over Bluetooth (so linux and macos can see it), and the controller central pad acts as a mouse which makes navigating menus great without needing to put the controller down. They go to sleep automatically if you close the lid on a laptop they're paired to, and you can change the LED colour and brightness on the controller.

I've had and used one for quite a while now, and in that time two of my friends have purchased one to replace various alternatives (8bitdo, & another one I can't remember) for either reliability, pairing issues, or both.

To top off this review: I've never owned a PlayStation!

If it's Apache 2.0 how are you getting royalty payments from it?

People are nice? But most likely they want a good relationship with me in case they get problems. Also they benefits from being able to tell their customer they support the project.

Ahh, I see. So you are receiving donations. Royalties to me mean payments that are required not voluntary.

I consider donation what random user give me on patreon/gh sponsor/itch.io

I talked with the makers or manufacturer and we reached an agreement. So to me (and them) it's royalties.

What you consider and your manufacturer considers doesn't matter. The definition of royalties is what matters, it doesn't fit in this case as far as I can see. They aren't paying you money so they can use your software, they are donating money because they are nice, they could stop paying at any time and continue to use your software.

Ad.

?

They get ad placement for the money paid ie a commercial transaction not donation.

Pretty sure the license means you do not have to pay royalties, not that you are disallowed from paying royalties

Royalties are typically a contractual payment, though. Calling a voluntary payment a royalty is kind of an odd use of the word, if not plainly incorrect.

You're right, these are donations. But they are donations that are determined based on the number of units sold. I believe that's why the parent is using the term royalty.

It's not a contract, as the term "royalty" implies, but it is a royalty in the sense that it's determined per unit sold.

>> If it's Apache 2.0 how are you getting royalty payments from it?

It sounds like acknowledging the sponsors is "the right thing", good Karma, or simply advertising for them. Not everyone wants to just rip off open source and not give back, they're willing to share the wealth if you make it easy and let people know they're doing it?

I need to set up github sponsors myself. We get the occasional request "how can I contribute money to you guys" and we always say stuff like "just spread the word". I keep telling myself I don't want to feel obligated by money, but I also know that I'd love to make enough to work on open source full time.

You’re not obligated by money when the money is coming from donations. That’s what donations mean. The people giving them to you are not your customers.

Also I can recommend OpenCollective; I’m sure there are other similar solutions as well. It’s nice to be able to “expense” stuff and I’m sure donors appreciate transparency.

I think it's really important to make it clear that the contribution is for what is currently there. I get often ask "Will $$$ make you work on that issues" and I always answer no.

What will help fix that issue is my wife going shopping with the kids long enough for me to figure what is wrong. ;)

So the obvious answer is to take the $$$, give it to your wife, and ask her to take the kids shopping with her :-)

Creative workarounds like this is why I love hacker news. :)

does this work with steamlink? I have bought all these different supposed "PS3" controllers but BT doesn't connect!

sponsoring is not licensing and royalty income

great that you got this result, btw