LibertyBeta

And if they don't, then the firmware is open and the community for retro games loves allowing the people to play their "backups".

Honestly as a whole the retro gaming hardware community is amazing. I'm part of one that's focuses on gameboys, and one member reverse engineered the firmware for a cartridge flasher because the main one from the manufacturer is so bad. now we have a new flasher and less buggy firmware.

I can't wait to see what we do to the Pocket.

I think the parent is typing to say that the data is stored in a map which is read to a proto, etc. Kinda like what GPRC does over HTTP. Which kinda makese sense. The schema gives you a great idea of what "should be", and the typing/errors/etc are understood by the host language.

Cory, first and foremost, sticks to his guns and writes what he believes. Glad to see this getting some press.

He makes me want to ditch my kindle for a kobo, but the book buying experience is just not as good/workable for me along with rebuying my catalogue. Not to mention cost of hardware.

For example, most Schools are in massive violation of OSHA because their air filters aren't up to the job because they can't afford to retrofit buildings to support a clean air system.

The unions are trying to keep their members ALIVE not out of spite, but because some one has to take the hit.

and you have my axe. Or pledge.

I find this interesting. One of the things I like about languages like Go, Dart, and Rust is their robust tooling.

If it's built as well as my Ergo from them. I look forward too it. They make some very refined and well thought out implementations of otherwise obvious keyboards. And they're open source firmware support is amazing.

So, why buy this v. s. building a pwnagatchi? Am I just missing the use case. difference?

This plays nicely into the idea that human consciousness is really just our brain meats way of resolving the internal understanding of the world with the outside understanding of the world.

Mental health, and any issues you have with it, are a hitch in that system. But to assume that you can fix is by only affecting one part(the internal understanding of the world) seems flawed for me. Same can be said, like in the article, of only fixing the outside understanding of the world (chemical changes).

So let me add my voice to your message, don't lose hope! We are a ball of walnuty textured jelly that tracks changes between the inside view of the world with the outside input of the world using lightning and chemicals. Its complex, hard, and the fault surface is huge.

Keep going, try new solutions, find someone one who helps you build the solution for you. But please, _try_.

Hopefully this will lead to an improved PineTab as well!

Another great crib sheet for JS folks to think about Rust. What I like about this, rather than say the Rust book, is you've given examples that map closely to other language paradigms without ignoring the fact that rust handles them differently.

So, to me, this just looks to wrap the import map functionality with a nicer cli.

For the same number of times as in days I'm torn on wether this is good.

On one hand, it's a bridge for node people and adds some nice comfort tooling.

On the other, it means you don't get to really understand how packages and bundling are supposed to work.

I may just end up writing a post on this tonight.

I like how "HOT" deno is becoming. A successor to node would be a great thing in my opinion.

That said, the fact that the author failed to bundle shows us one of the hurdles that Deno has to overcome. When the tooling is "batteries included" people need to remember to pull the little plastic tab out(bundling).

I can second this recommendation. JS is an odd bugbeast in that it took some design shortcuts early in it's life that aren't really visible without this kind of "here are your primitives" review. It also works like any other language primer in that it doesn't go into needlessly specific domain bound examples. That kind of stuff should be in a stdlib-eqsue doc.

A good read for even for some one like me, who slings JS almost daily.

I can only see this as good. MATRIX is awesome, but people don't get the connection between riot and matrix. I think of it a bit like IRC and mIRC. It lowers the bar of entry(a 9 year old could have setup mIRC when it was commonly popular) and lowers the bar of protocol discovery.

So, this looks interesting. Rather than a real new linter, Github is proposing a tool that runs against a number of common linting standards with a single shared standard library.

Perhaps it would have been better pitched a Lint-runner for CI jobs rather than a real linter.

Doesn't help if they close down your account for saying the wrong thing....

Took a quick look around at the offering, seems like an interestingly focused product for email. And I'll be honest, the kind of dedicated "Works well works here" focus of Basecamp is something I've come to love for general project management.

We live/work in a world were small projects get too easily overlooked. Not every one has to be a FANNG. This should apply to email as well.

Now this looks fun! I might spend some time poking around in your API and whip up a quick flutter app.

This would be similar to people who run Syncthing meshes for their file system backups, correct?

Digging a little into the posts about HOW they setup the communication channel does seem like it could be used to inform a system for that. So Kinda?

I would stay with Vue. While the react world is bugger it's mostly made up of competing solutions instead of distinct tasks.

That said, this healthy Vue/Angular/React competition has been great for us devs.

Does any one know if this means react native is moving as well?

Cause I might consider a move now.

Good points, but I think we can work around them.

1) As others have said xinput is pervasive as this point. If the Xbox 360 controller becomes hard to source then I'm sure a replacement xinput derived device will still be around. If not, it's a well documented standard and new devices can be made.

2) This leans on my first response. Xinput is the winner here, not the Xbox controller. If after testing they can't harden it then we have a lot of other options, up to and including a bespoke controller.

I guess what I'm saying is that video game controls are so much fun for a reason. They 'just work'. And while there is a little bit of dystopian sheen to seeing video games become the source for defacto tooling for war machines I'm always for a simplification of man/machine interactions.