IronOS VS tauri

So apparently the Pinecil is a BLE-enabled soldering iron with a 108 MHz RISC-V processor running a custom real-time operating system [0]. The author wanted to access the UART logs, so they repurposed a Raspberry Pi Pico (a dual-core microcontroller system running a real-time OS) for the task.

That's a staggering amount of hardware, sortware and computing power devoted to decoding one of the simplest and oldest serial protocols from a device whose sole purpose is to essentially melt tin. Maybe I'm out of touch, but I think I'll stick to my thermostat-controlled Weller soldering station and FTDI UART converters. I apologize if this post comes across as snarky, my point is that these are solved problems and have been for half a century.

[0] https://github.com/Ralim/IronOS

I got a TS101 and wanted to switch to IronOS straight away as it seems like an improvement to stock firmware. On the website it says that TS101s are supported, but there is no file for it. I figured it must be the TS100 .hex file, but flashing it just gives me an error (a .NOT file). Is the TS101 really supported and how do I flash the firmware in that case?

but the pinecil can also use IronOS https://github.com/Ralim/IronOS

Look at this ticket in Ralim's IronOS, all 4 people same issue and all they had to do was clean their Cartridges with IPA 90-99% Alcohol. https://github.com/Ralim/IronOS/issues/1601

I'm very happy with the Pinecil. The $25 price is very reasonable for a reliable soldering iron that is open source hardware[1] and runs on free and open source firmware.[2]

[1] Schematics: https://wiki.pine64.org/wiki/Pinecil:_How_to_Repair#Schemati...

[2] IronOS: https://github.com/Ralim/IronOS

Also, I'm not sure what exactly is happening with the OS on the irons, because I thought the pinecils shipped with IronOS but it may be an old or cut down version because when I loaded the latest https://github.com/Ralim/IronOS on my pinecils I just ordered two weeks ago, I definitely got a ton of options I didn't have before.

Hi, dear Tauri! Long time no see. I published my first post, Developing a Desktop Application via Rust and NextJS. The Tauri Way almost a year ago. Since then, Tauri has become stronger. I'm happy about that! And now, I am very pleased to make a useful contribution to the Tauri community. As a full-stack developer, I frequently face situations where I need to start a DB-based UI project as fast as possible. It's stressful if I need to start the project from 100% scratch. I prefer to keep some boilerplates on hand, which will save me time and nerves and will be the subject of this article.

Hey Thanks!

Just electron & vite. I might actually migrate off electron, Tauri (https://tauri.app/) seems to be getting more stable and it's gotten great reviews.

I think this is the boilerplate I used though https://github.com/cawa-93/vite-electron-builder.

Well the great thing about WebAssembly is that you can port QT or anything else to be at a layer below -- thanks to WebAssembly Interface Types[0] and the Component Model specification that works underneath that.

To over-simplify, the Component Model manages language interop, and WIT constrains the boundaries with interfaces.

IMO the problem here is defining a 90% solution for most window, tab, button, etc management, then building embeddings in QT, Flutter/Skia, and other lower level engines. Getting a good cross-platform way of doing data passing, triggering re-renders, serializing window state is probably the meat of the interesting work.

On top of that, you really need great UX. This is normally where projects fall short -- why should I use this solution instead of something like Tauri[2] which is excellent or Electron?

[0]: https://github.com/WebAssembly/component-model/blob/main/des...

[1]: https://github.com/WebAssembly/component-model/blob/main/des...

[2]: https://tauri.app/

Welcome to the 2nd episode of our series “Building with Tauri”, where we chat with developers who build amazing projects and products using Tauri.

Tauri seemed like the "thing" I should switch to because everybody loves Rust (heh), and because it ships significantly smaller apps.

First of all, I will be using npm as my package manager but feel free to use whatever you prefer. Find more info here.

Today I'm talking about Tauri! Do you know all the various tools that allow you to develop native applications starting from web languages? They often need an intermediate compilation, in the middle of which you end up encountering various problems not always transparent and directly solvable with a language mostly detached from native development. On the other hand, there's still the ease of developing attractive and easily usable interfaces, which are more difficult to develop with low level languages.