zenosmosis

This is interesting, I'd like something like that as well.

I'm doing some experimentation with something sort of along these lines via WebRTC.

I'm not sure if this was a serious comment, but that sounds like a massive amount of performance overhead.

A way to optimize that approach substantially, while keeping everything else mostly the same, would be to have a setter on the global object, and only re-render the root component when that setter has updated the state.

My suggestion is not a very optimal approach, but probably a lot better than the continuous state loop.

I prefer sticking w/ the basics and using EventEmitter.

https://speaker.app has a UI I've been prototyping w/ this approach.

I use Docker inside of Parallels running Linux and get far better performance than Docker Desktop.

Just make a PWA instead.

I am just stating obvious facts. You are trolling.

His companies were the first to land rockets and make the electric car popular. I am not saying he knows everything, but I am sure he can fix a website given a bit of time.

I find that Docusaurus docs usually are the easiest to follow when consuming them but I have no experience with creating them: https://docusaurus.io/

One interesting dynamic here. Literally everyone who tries to give him advice has less money than him.

This is a dupe and spparently they don't tweet.

I use a remote Mac and use the built-in screen sharing over VNC to help me set up NoMachine, which offers a much better experience.

I am not affiliated with them but have used them for years and have generally been very happy with it.

Plus you can share drives and USB devices over network.

Sometimes you may need to write code which runs in a browser as well as Node.js, and most test runners do not support this functionality out of the box, in order to run unit tests across all environments without duplicating the tests per environment.

So I made a little project with the number one goal of being a "ubiquitous" test runner, running tests against real browsers as well as Node.js w/o modifying tests to run between environments.

https://github.com/zenOSmosis/karma-jasmine-typescript-boile...

https://dev.to/jzombie/test-in-nodejs-and-in-browser-with-th...

Cloud gaming is an option as well.

True, and if they play online video games, they probably know as well.

I'm in Nicaragua and have a $10/mo. HBO Max subscription which includes Rick and Morty.

Thanks for clarifying this.

Great to hear Winamp is still being maintained.

One slight suggestion to this link is that it have SSL. It seems the benefits of SSL far outweigh the cons, especially when certs can be obtained for free via the likes of Let's Encrypt and the auto-renewing automatically maintained w/ something like: https://hub.docker.com/r/linuxserver/swag

I am curious why git modules couldn't be used here, and perhaps scripted to match particular workflows.

I live in Nicaragua and they are pretty expensive here. 14" Macbook Pro with M1 Pro, 16GB / 1TB set me back $3350 USD.

I somewhat agree with this sentiment (thought about it before as well), though I now tend to think of it as something like "fetching" the result of a given call, regardless of the operation type.

Looks like you've done some homework here.

Just a quick note: I followed through to the article on https://fatih-erikli.com/pattern-matching-in-typescript.html and noticed the useEffect call doesn't define a dependency array (not even an empty one), which I believe will make the addEventListener add new listeners on every render. Having a removeEventListener on the return of the useEffect would also ensure it gets cleaned up, if pointed to the same event name / handler.

I assume it was just for illustrative purposes, but felt like I should point it out, regardless.

+1 for "...Zuck decided to rename his shitty website from Facebook to 'Meta.'"

Yeah, good luck with that.

It's likely a CSS rule.

For example, look at word-break: https://developer.mozilla.org/en-US/docs/Web/CSS/word-break

Beautiful project.

Imba website looks great and the code examples explain it well. The React-like server-side rendering with the .html imports is phenomenal!

Lets wait a few years and see how this actually plays out.

Wonder if it makes any difference that the notice is buried 1/4 down the README instead of prominently displayed at the top.

Someone opened a GitHub issue calling it "pretentious" and asked to rename the project but it got closed w/ a "U Mad Bro" response: https://github.com/standard/standard/issues/1609

Maybe that makes it officially a standard after all.

https://speaker.app, an experiment that uses a web browser for an MCU / SFU.

https://github.com/zenOSmosis/speaker.app

Nice. I am a big fan of your swag repo for LetsEncrypt certs and have been exploring browser-based Linux desktops for several years and will give this a go.