BlueRetro VS jsynchronous

SNES: FX Pak Pro, Internal BlueRetro mod (BT controllers), Voultar's RGB bypass, Recap. N64: Everdrive x7, Tim's RGB mod, Noctua fan, Recap. GC: PicoBoot, LaserBear's internal BlueRetro mod (BT controllers). PS1: xStation, Internal BlueRetro mod (BT controllers), Pico PSU + Noctua fan, Recap. PS2: Ultraslim mod with SD card reader in top Fat PS3: This is actually a sleeper PC with a GTX 1060 and a Ryzen 5 2600 for emulation purposes.

Read this

I do plan to do an internal BlueRetro mod at some point (so I'll be able to connect controllers without dongles) but I'm waiting til this issue is hopefully fixed.

best i could figure out is that he did this. https://github.com/darthcloud/BlueRetro/wiki/BlueRetro-DIY-Build-Instructions maybe there is something better?

https://github.com/darthcloud/BlueRetro This is the GitHub page with tons of different links to different sellers. I would try my chances there.

It’s already available and fairly easy to build yourself: https://github.com/darthcloud/BlueRetro

This issue is documented on the BlueRetro github, where it is the 5th-oldest reported bug, as well as by far the most commented. This issue has been known for at least a year and a half. Will's Console Modifications used to have this bug listed on the UnoRetro page, but they removed it - even though the bug still hasn't been fixed - which means you have to use the Internet Wayback Machine to verify on an old version of their website that they knew about it.

The official BlueRetro docs have great instruction on how to install the code and pair controllers, but for internal installs I'd recommend nostalgic-influences wiring diagram.png) if you're like me and have trouble reading electrical schematics.

A data-synchronization library for Node.js

https://github.com/siriusastrebe/jsynchronous

Ever get tired of sending API requests and JSON payloads? Wouldn't it be cool if data just synced between server and client?

Jsynchronous lets you share deeply nested object/arrays between node.js and connected browsers – and any changes made to that variable.

For the very reasons listed in the article, I built:

https://github.com/siriusastrebe/jsynchronous

a library for keeping a javascript variables synchronized between Node.js servers and clients.

Websockets work great for message passing but it struggles with data structures more complicated than what JSON can represent. Jsynchronous syncs any javascript object or array with arbitrarily deep nesting and full support for circular data structures.

If a computer goes to sleep, or disconnects, websocket connections (and their underlying TCP connections) get reset so you lose any data sent while a computer is unavailable. Jsynchronous will re-send any data clients are missing.

There's also a history mode that lets you rewind to past states.

I recently built https://github.com/siriusastrebe/jsynchronous which uses event sourcing to synchronize javascript variables on the server with connected browsers.

You can also replay states using a special “rewind” mode, a core advantage of event sourcing.

Not for rust - for javascript: Take a look at this library: https://github.com/siriusastrebe/jsynchronous

Fullstack web developer, data visualization and real-time app specialist

I recently built and open sourced https://github.com/siriusastrebe/jsynchronous a real-time data sync library for javascript.

Location: Seattle, full time roles