autocomplete VS druid

Having contributed to the Fig autocomplete specs, I find this sad. The Amazon product Fig was built into basically works as replacement, which is good. Still, the core value of this product are the open-source autocomplete specs: https://github.com/withfig/autocomplete. What's going to happen to that? It looks like they are still using it in the Amazon product. It should definitely be possible for an open-source re-implementation of the Fig UI to use those specs. There is a lot of knowledge encoded in there!

8. Fig

Fig is awesome but with signups blocked[1] for 2+mo already it's also as good as dead ¯\_(ツ)_/¯

* [1]: https://github.com/withfig/autocomplete/issues/2068

https://github.com/withfig/autocomplete is it this?

How is this different than https://fig.io/?

AWS CloudWatch Evidently The worst. No comment. AWS seems to perpetually lack a good DX for developers. It appears that they don't recognize or continually undervalue the importance of roles other than engineers, such as Product Managers or Designers. Very disappointing. However, AWS has recently acquired Fig, so looks like they're now pursuing an acquisition strategy instead. Let's see how it turns it out, and let's hope they don't ruin Fig, since it's such an useful tool.

slightly tangential, but where do people get awesome landing pages like linear(https://fig.io/. has similar landing page) etc. Do they build them in-house or buy templates somewhere? Many of the recently launched YC companies have awesome landing pages. eg. https://automorphic.ai/,

I love this product, have contributed several times to it, and I'm a little torn. One thing I am thinking about now, is that the completion specs are MIT-licensed, and it should be possible to use them to re-implement a basic open-source version of the autocompletion product... https://github.com/withfig/autocomplete

For GUI applications, the story is mixed. There are several GUI frameworks in active development, but nothing as polished and battle-tested as Electron for TypeScript. There are bindings to GTK, but they're cumbersome to work with, and I wouldn't recommend it to a Rust newbie. There's also Tauri, which is a bit like Electron and lets you write the GUI in HTML/CSS/JS and the business logic in Rust.

Concerning GUI frameworks, the most common ones are druid, egui and iced. All three of them run native and on the Web.

Going to give a shoutout to druid. I've recently tried it with the Lapce editor and it's just so smooth, fast and works so well for a pre-alpha app.

As iced and egui were difficult for me, i started with druid.

There is Iced which is used by system76 in Pop!_OS, Druid [DISCONTINUED], GTK-rs, Relm, Azul and Tauri. Personally I would use Tauri for its speed using the OS's native web render, documentation of use with things such as Sveltekit and the ability to make UI's using JS, CSS and HTML. Tauri similarly to Electron whilst being far faster. But its up to personal preference really. There aren't any solid "go to" options at the moment.

Druid should be good for most cases, it has a lot of built-in widget for the UI, you can even make a custom widget with a canvas-alike painting API.

Druid, which is a Rust-native UI toolkit for building desktop applications targeting Windows/macOS/Linux/OpenBSD/FreeBSD, has a new version out - v0.8.

There's a memoize View node in the previous iteration of the Xilem prototype, but it hasn't made it in to the current branch yet. That sounds like what you're asking, but it's possible I'm missing something.

You can use GTK from Rust. But the Rust native ones aren't really there yet. [Iced](https://github.com/iced-rs/iced) which has been picked up by System76 and [Druid](https://github.com/linebender/druid) (and it's next gen version [Xilem](https://github.com/linebender/xilem)) are the ones to watch, along with Dioxus which is the main post here.

I'd expect there to be something useable by the end of 2023.