truss VS autocomplete

Nice! We copied StyleX's "type-safe extensions" in Truss [1] so things like `` are allowed (setting margin is fine) while disallowing `` (anything "not margin") that would mess up the components internal impl details with a compile error.

That said, we don't actually use the feature that much, vs. higher-level logical props like ``.

I know we're supposed to use build-time CSS-in-JS these days, but afaiu they don't support the rare-but-handy "just spread together ~4-5 different object literals from ~random different conditionals + props", i.e. intermixing styles some inside the component + outside the component, which emotion handles really well.

Basically this [2]. StyleX says it does "cross-file styles"...but can it support that? I kinda assume not, but I'm not sure.

[1]: https://github.com/homebound-team/truss#xstyles--xss-extensi...

[2]: https://github.com/homebound-team/beam/blob/main/src/compone...

Fwiw to the avoid 80%-in-TW / 20%-in-SCSS-or-something-else dichotomy/complexity, we built Truss which brings TW (Tachyons) style abbreviations to the existing "something else" tool chain (Emotion in our case).

So then everything goes through a single system.

https://github.com/homebound-team/truss

> tailwind's and SCSS's VS code integration is pretty amazing

We get that too, by being just vanilla TypeScript, no editor-specific integration necessary. :-D

(I've linked to Truss in another response, so will stop now. :-))

Don't want to take away from Tailwind, it's great.

That said, self-promotion disclaimer but if you like inline/utility CSS, and also like TypeScript/React/Emotion, we've got a "Tailwinds-ish" CSS-in-JS library that we've enjoyed so far:

https://github.com/homebound-team/truss

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