3 ms·
Looks really interesting! Huge shame there isn't any native client, but at this point, I wouldn't even know what stack can still produce a native client without
by lionkor 3y ago
Looks really interesting! Huge shame there isn't any native client, but at this point, I wouldn't even know what stack can still produce a native client without being shunned by HN ;)
- meiraleal 3y agowhat would be a native client? They need the nodejs server in the client so Electron and React Native are the platforms needed to support their architecture.
- lionkor 3y agoA native client would usually, for the most part, be written in a language native to that OS, and usually compiled. The discerning factor is that native apps, or any apps which use (actually) native GUI frameworks (as opposed to gpu rendering their own), integrate much better with the OS
- meiraleal 3y agoThis is the goal of React Native Desktop, not sure how good it is.
- holmesworcester 3y ago(Quiet founder here) LOLOL. Ask HN: "How to produce a native client without being shunned by HN?"
- lionkor 3y agoI mean really - the obvious, most featureful and well known one would be C++ with Qt or something, but thats way too unsafe (says the crowd using Chrome which is mostly C++). Rust doesnt have any mature GUI frameworks, and Lisp is probably the best choice here (for some reason).