51–60 of 177 posts
Hey - I am nothingismagick aka Denjell, one of the founders of Tauri, and will do my best to answer your questions about the project, rust, wasm, etc. https://github.com/tauri-apps/tauri
I don't care about your YouTube videos, I don't care about your governance, I don't care about your book, tell me what it is in non-marketing speak and show me a screenshot on the front page and shut up about everything else. Tell me what it is, show me what it looks like, provide a "Hello, World!" API example for opening a window on the front page. Stop contributing to landing pages that jerk the consumer around.
They've got a point. Time to cut through the hype, get straight to the point and show some screenshots to catch their eyes.
If you can't manage that, the tab gets closed with in 5 seconds. Even if it has the Rust buzzword. (Because that trick always works on HN)
I don't care about your YouTube videos, I don't care about your governance, I don't care about your book, tell me what it is in non-marketing speak and show me a screenshot on the front page and shut up about everything else. Tell me what it is, show me what it looks like, provide a "Hello, World!" API example for opening a window on the front page. Stop contributing to landing pages that jerk the consumer around.
I don't care about your YouTube videos, I don't care about your governance, I don't care about your book, tell me what it is in non-marketing speak and show me a screenshot on the front page and shut up about everything else. Tell me what it is, show me what it looks like, provide a "Hello, World!" API example for opening a window on the front page. Stop contributing to landing pages that jerk the consumer around.
Earlier quoted context omitted.
Normally I'm on the defensive side for the JS ecosystem on Hacker News, but not today. While it's still the best option for web app development productivity right now, there are woefully bad issues with the Node ecosystem, from poor or lack of documentation for complex build tools to zero contracts between dependencies. Rust has the advantage of being able to break if things seem to not fit together. It's a popular l…
> zero contracts between dependencies. Isn't typescript contract? This is not really about JS, if I want to replace JS I'll pick a language with similar characteristics that make it successful. Similar to how you replace C++ with rust, another language that gives you control of memory. For app developments they are simplicity and a focus on domain modelling with a good type system (this is typescript teritory), NOT m…
> the focus isn't domain modelling, like C++ and golang's type systems
Could you please explain what you mean by this? I've honestly not heard this argument before so I'd be interested what domain modeling Rust doesn't encourage/support that, e.g. Go does.
Earlier quoted context omitted.
Maybe you should spend like 5 minutes looking into the thing you're critiquing before critiquing it? Just a suggestion, given that Tauri literally uses typescript for front-end.
did spend 5 mins, saw absolutely no code so I made some assumption. Maybe they should make better docs that don't require 5 mins+ to figure that out.
You don't need to offer a perspective on everything, and I prefer the critiques I read to be well-founded.
Earlier quoted context omitted.
That seems to eliminate one of main advantages of electron, the consistent runtime environment. If your html/css/is has to work correctly in EdgeHTML, Safari Webview, and Blink, you are limited to the lowest common denominator features. Electron with Chromium has the largest feature set out of all of those.
I can’t speak for other developers but my app runs on electron and the web (because why not?), so I need to make sure my app works with those browsers as well. A lot of the big electron apps I’m aware of are the same (slack, notion, discord, etc).
I don't care about your YouTube videos, I don't care about your governance, I don't care about your book, tell me what it is in non-marketing speak and show me a screenshot on the front page and shut up about everything else. Tell me what it is, show me what it looks like, provide a "Hello, World!" API example for opening a window on the front page. Stop contributing to landing pages that jerk the consumer around.
Like I wrote in another response, we are due for a landing page revamp, and we'll be sure to make a "nothing but the facts" hero for people like yourself who are concerned that their time is being wasted.
It's not for "people like me," it's for everyone. In terms of volume of traffic you're going to get, no one else cares about this stuff.
Here's an example of one of my projects where I do just that: https://www.planimeter.org/grid-sdk/ Literally! I tell people what my team has built. I show them a screenshot. I then provide API examples. Mine could be better if I provided screenshots per API example, too. Everyone can improve.
Your audience is technical, they don't want a non-technical pitch. Tell me it's faster than Electron, show me RAM usage comparisons, etc.
I don't care about your YouTube videos, I don't care about your governance, I don't care about your book, tell me what it is in non-marketing speak and show me a screenshot on the front page and shut up about everything else. Tell me what it is, show me what it looks like, provide a "Hello, World!" API example for opening a window on the front page. Stop contributing to landing pages that jerk the consumer around.
Also, I liked the way they presented their roadmap.
Earlier quoted context omitted.
They use whatever is the system WebView on the platform you run the code on. On Windows that's the Edge engine, on MacOS it's Safari's engine, etc. Those are all some combination of C and C++. See https://github.com/tauri-apps/wry Edit: s/IE or Edge/Edge
That seems to eliminate one of main advantages of electron, the consistent runtime environment. If your html/css/is has to work correctly in EdgeHTML, Safari Webview, and Blink, you are limited to the lowest common denominator features. Electron with Chromium has the largest feature set out of all of those.
AFAIK, if you're writing a greenfield Electron app, it's best to do as little as possible in the renderer side, and as much as possible in the Node.js side, because the Node.js side has things like native threads and mmap(2), and everything running within the Node.js process can share that state, but things on the renderer side have to use it through RPC.
I would assume that this project is similar, but with arbitrary Rust code in place of Node.js (is that right?)
In that case, it doesn't matter how featureful the renderer is, as you're just using it as a GUI framework with a declarative view-model format. Just like a XAML or QML, but it's HTML+CSS.
As such, idiomatically, you won't be using fancy browser APIs like threads or WebRTC within the renderer; instead, you'll be using native code on the "app side" and then passing the renderer data. The features of Tauri itself are "whatever native libraries you want to bring into your Rust binary." (Plus whatever conveniences it already builds in, of course.)