I'm not sure. The last time I tried using it, I had a similar experience.
Nobody was ever able to coalesce a coherent UX/UI around ssb, the core contributors at the time weren't interested in scaling the network without outside funding.
I was working on implementing lighting fast discovery for ssb using a distributed BitTorrent-like tracker. Getting onto the ssb network took way too long. Still, there were not many users on the network, and nobody seemed interested in growing.
I've spent approximately 13 months with WebGPU + WASM + CSS + JavaScript, building high-performance gaming solutions that run in browser. It's possible to run graphics at Nintendo64 level quality on a potato. JavaScript as an orchestration layer for WASM is exceptionally performant.
I think what the people at thanks.dev and Front End Masters are doing is great, and I appreciate what they are doing. I made it on this list and got $5 for something. Great.
I've spoken with armini about Thanks.dev numerous times—a great person to talk with and knowledgeable about open-source economics.
The brass tax here is that the peak of open-source software written by humans has already passed us. The following steps we'll be seeing are things like LLMs, which are trained on the entire NPM registry and can solve any known domain problem through curated APIs.
The next few years of open-source will be unglorified janitorial positions with minimal pay. Most of the intelligent maintainers have already offloaded their projects to others.
Anecdotally, I have found that open-source projects with overly abundant funding have perverse incentives for their user base and ultimately harm society.
Ok human. You can read the Hans Moravec paper on CTC and time loop logic to understand Novikov self-consistency principle is formalized, yes you must run the computation for as long as it would have already taken or result will never arrive.
I say through "through use of quantum entanglement" as glossy term for reader. Crystalline quantum circuits are not really existing yet so is all scifi.
I won't be able to repsond to further posts in this thread. Cheers.
Time loop logic is a hypothetical system of computation that exploits the Novikov self-consistency principle. In this system the computer is able to send the result of a computation backwards through time and rely upon the self-consistency principle to force the sent result to be correct.
I've written about this before. Instantaneous data transfer with zero lag is theoretically possible through use of quantum entanglement. You can use this same technique to build a doomsday clock similar to the film "Tomorrowland".
We think it's deplorable that a concerted effort was made to dilute the Markov chain ranking of James Halliday ( aka the actual Substack ) for not wanting to play games with you. James has the quantum entanglement crystal and there is nothing you can do about it.
First off, thank you for bsnes. Have used it a lot in the past.
It's a tough call, but it's somewhat understandable what Google is doing. Arbitrary binary downloads from arbitrary websites are for the most part a problem for the majority of users.
There is nothing stopping a savvy user from still finding and downloading your binaries. You should probably figure out a better distribution channel.
Remember that all the hoops you have to jump through to get a signed binary are also required for anyone who would want to pirate your software and re-release it with a virus ( which I have seen done in the emulator community before ).
I would think this is a common approach. I use the same approach. Scales up to hundreds of developers.
I do generally try to enforce the goal that on any working day there should be at least one commit from the developer. If I notice a developer is consistently missing this metric it usually indicates trouble in the project they are working on or that the developer is just not delivering enough.
NPM still has bugs from v5 which haven't been addressed and are ignored by it's maintainers. Problems with `npm link` were never fixed. There is a discussion on the NPM tracker where the maintainers tell Substack that his ( very correct ) assessment of an issue was wrong and lock the thread.
It's always the same usual suspects at NPM never accepting responsibility or blame for multiple incidents and ongoing quality issues.
NPM is currently on it's last legs before acquisition or buyout.