hsheth2

4 ms·

1.
Python concurrency: gevent had it right(harshal.sheth.io)
2 points by hsheth2 11mo ago|1 comments
2.
Python async: a step in the wrong direction(harshal.sheth.io)
5 points by hsheth2 1y ago|0 comments
3.
DataHub MCP Server(github.com)
3 points by hsheth2 2y ago|0 comments
4.
GitHub Actions Won CI(harshal.sheth.io)
2 points by hsheth2 2y ago|1 comments
5.
by hsheth2 5y ago
Yes you’re right - I somewhat conflated two different things. More clearly: once Wasm interactions with the browser are fast, a new framework + Wasm could replace React + JS.
6.
by hsheth2 5y ago
If we get to a point where interacting with browser DOM is comparably fast with Wasm, either through JS or with native APIs, then we could see Wasm replace React. That said, you're right that we probably won't see anything of that
7.
by hsheth2 5y ago
From a technology perspective, I think you're totally right that Wasm and WebGPU support is super exciting for game engines like Unreal/Unity. The ease of distribution could be a game-changer. That said, I'm not super familia
8.
by hsheth2 5y ago
Agree with sibling comment - the JS ecosystem has a huge momentum behind it and probably isn't going away anytime soon. On the web, Wasm has currently found the most success with compute-intensive applications, since the JS <-> W
9.
by hsheth2 5y ago
Hey Syrus, that's great to hear - I'm excited to see what WAPM has in store!
10.
by hsheth2 5y ago
Thanks for the correction - I'll update my post shortly.
11.
Pay attention to WebAssembly(harshal.sheth.io)
344 points by hsheth2 5y ago|244 comments