kesh VS tauri

I have something similar in kesh, where : is the assignment operator and the type/signature may be "assigned" before the value:

I'm not OP, in case you thought that :) kesh lives here. I tried incorporating some of the ideas discussed here, but posponed it to a later language, which I'm still thinking about.

This is a great idea that I've adopted for my PL. I took it a step further and also allow extensions of the core language to be specified, including profiles.

My (non-existing) language kesh, designed to compile to TypeScript, has expression blocks. That was one of my first decisions.

Still no work on a compiler, but more work on the documentation of kesh.

I'm working on kesh, but it's only at the design stage. I have tried to make it simple yet powerful, so I thought I'd mention it even though you can't use it.

I tried to distill down the most essential features of TS/JS (functional, prototypal) and then come up with new syntax and semantics that was minimal, orthogonal and hopefully easy to learn and use. The result is kesh and na.

I like the way you think. I had the same goal with kesh. A minimal syntax is easier on the eye and lets you focus on the actual code.

I'm only at the drawing board stage of kesh, a simple little PL that one day might possibly transpile to TypeScript. Not a single line of compiler code has been written so far, it's still all about syntax design and exploring ideas. kesh is mostly a pastime activity and something I can ponder over when I'm bored or can't sleep (which may be the reason I can't sleep).

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.

I think Tauri is the most established framework using that approach

https://tauri.app