ianjsikes

Barrier is almost perfect for my use, with one big flaw. It has no concept of individual displays. For most setups, it probably isn't a big deal. For me, I am back to a hardware KVM.

The cheaty way is `let copy = JSON.parse(JSON.stringify(val))`. Doesn't work for functions or cyclic structures though.

I'm in a similar situation and i'm going with a 5900x FWIW. The 5950 feels a little overkill, I don't expect to be fully taking advantage of the extra cores.

Wow, the bubbles feature is really interesting. They standardized Facebook Messenger's chat bubbles (the best part of Messenger imo). Pretty awesome to be able to have chats from many different apps accessible in the bubbles.

I am working on a little clone of One Night Ultimate Werewolf using Phoenix LiveView. It has been working out great for me so far.

That would be really interesting to me. I have been eyeing Kakoune for a while and love the idea but I'm too invested into VS Code to completely switch editors.

Are you... comparing psilocybin to heroin?

> Seems intuitive that if parseInt allows omitting the radix parameter, that it should default to whatever radix a standard integer primitive would default to.

But in this case, the radix is _not_ omitted. The map function passes the index of the current iteration as the second parameter to the function it is passed. It is kinda like this: ``` ['1','7','11'].map((item, index) => parseInt(item, index))

1. The "index.js" thing is due to how module resolution is handled with CommonJS and ES modules. If you have a file at "./lib/index.js", then you can omit the "index.js" and just write "require('./lib')" from another file.

2. Not exactly. In JS, every file with an "import" or "export" statement somewhere is its own module.

3. You can write code like this for the browser. Most browsers support ES modules now. However, you do need a bundler tool like Webpack if your code depends on other node modules.

Just wanted to mention that React Native + React Native Web _is_ a viable solution (at least for me it was). I was able to convert a mobile React Native project into a usable mobile website with Next.js and `react-native-web`.

I had to use a lot of platform-specific imports (eg: `index.ios.tsx`/`index.web.tsx`) to replace anything mobile-specific, and there are some cases where you need platform-specific UI components as well to make everything look nice on larger screens.

My only complaint is it gets a bit messy having all these different entry points and platform-specific modules and whatnot. Overall, it's probably the best you can hope for to write an app for mobile + web with ~80-90% _actual_ code sharing.

Better yet, scale the image proportionally down to the largest of the two target sides, then run the algorithm once in the direction that needs to shrink.