io_eric

6 ms·

1.
by io_eric 7mo ago
Honestly, the biggest difference is how they treat the web. Flutter brings its own entire rendering engine to the browser to draw pixels on a canvas, while Coi is designed to use the browser's native HTML and CSS. If you’ve used Vue or
2.
by io_eric 7mo ago
Technically, it’s not just about the download pipe. A 2MB+ WASM blob or JS bundle imposes a heavy CPU parse/compile tax. On mid-tier mobile devices, this results in main-thread jank and a 'Time to Interactive' (TTI) that kill
3.
Show HN: Can we have Flutter-like portability without the bloated web binaries?
1 points by io_eric 7mo ago|4 comments
4.
Show HN: Designing package namespacing for a new language (Coi)
1 points by io_eric 7mo ago|0 comments
5.
by io_eric 8mo ago
Thanks for the feedback! You're absolutely right to question this. Just to clarify, my benchmark was using Canvas2D, not WebGL, that's why the numbers are much lower than your WebGL2 example. Based on your comment I actually remov
6.
by io_eric 8mo ago
Hard disagree. Canvas 2D is fully GPU-accelerated in modern browsers and can easily handle thousands of draw calls at 60fps,more than enough for most practical applications. For data visualization, interactive tools, drawing apps, and UI re
7.
by io_eric 8mo ago
I suspect Svelte’s heavy lift with compile-time reactivity came largely from trying to infer "reactive intent" from standard JavaScript code. Since JS is so dynamic, the compiler had to rely on heuristics or strict assignment rule
8.
by io_eric 8mo ago
Possible in theory, but a Vue→Coi transpiler would be complex given the different reactivity models and syntax. Most practical approach: AI-assisted conversion. Feed an LLM the Coi docs + your Vue code and let it transform components. For m
9.
by io_eric 8mo ago
Fixed! The issue was specific to FreeBSD's clang setup. When compiling with --target=wasm32 and -nostdlib, clang on Linux/macOS still finds minimal freestanding headers for the wasm32 target, but FreeBSD's clang doesn't
10.
by io_eric 8mo ago
Reactive DOM updates – When you change state, the compiler tracks dependencies and generates efficient update code. In WebCC C++, you manually manage every DOM operation and call flush(). JSX-like view syntax – Embedding HTML with expressio
11.
by io_eric 8mo ago
You're right about the market positioning - WebCC isn't trying to be Emscripten. It's for when you want to build for the web, not just on the web. I'm actually using it myself to port my game engine, currently in the pro
12.
by io_eric 8mo ago
I started with WebCC to get the best possible performance and small binaries, which works well for things like games. However, writing UI code that way is very tedious. I built Coi to make the development process more enjoyable (better DX)
13.
by io_eric 8mo ago
Pretty fast. It doesn't drag in the C++ standard library, so builds stay lean. My demo page takes about ~1s to compile for me (after the first time)
14.
by io_eric 8mo ago
Good question! Pure JS would likely be comparable or slightly faster for this specific test since there's zero interop overhead. The 10k rectangles benchmark is specifically testing the interop architecture (Emscripten's glue vs
15.
by io_eric 8mo ago
A C++ library could wrap DOM APIs (WebCC already does this), but achieving a fine-grained reactive model purely in library code involves major trade-offs A dedicated compiler allows us to trace dependencies between state variables and DOM n
16.
Show HN: Coi – A language that compiles to WASM, beats React/Vue
225 points by io_eric 8mo ago|69 comments
17.
Show HN: Coi – A compiled-reactive language for high-performance WASM apps
3 points by io_eric 8mo ago|0 comments