QED VS impulse

Not exactly "experimental", considering the Unix heritage, but -- line editors.

"I've seen [visual] editors like that, but I don't feel a need for them. I don't want to see the state of the file when I'm editing." -- Ken Thompson, on the superiority of ed to visual editors. Summarized by Peter Salus in A Quarter Century of UNIX (Addison-Wesley, 1994).

Definitely a blast from the past, but I do think line editors may force one to write simpler programs -- or to think in smaller chunks, as opposed to (doom)scrolling or moving about incrementally on a large screen.

Rob Pike's sam editor has an interesting command language. You're not limited to thinking in "lines" as in ed or sed; rather, the whole file is a giant string that you manipulate using regular expressions, external pipes, etc: http://doc.cat-v.org/bell_labs/sam_lang_tutorial/sam_tut.pdf

Its predecessor, qed, is also interesting, extremely powerful, but it seems to have a much steeper learning curve. I have used sam quite a bit, but not qed. https://github.com/phonologus/QED/raw/master/doc/qed-tutoria...

I you use Tailwind and React, you might like Impulse[1] (disclaimer: I made it and use it almost daily)

Not only does it provide means for visual editing (for Tailwind only), but it also saves all changes to your code.

Free and open source.

[1] https://impulse.dev/

I've been working exclusively on this project for half a year and... I don't really know where it's going. One of the primary goals from the beginning was to make a product I could use for most of my UI work. And oh my God, have I achieved that. Having used Impulse regularly for months (including designing Impulse itself and impulse.dev), I can't imagine going back.

You can look at a few demo videos on the website https://impulse.dev/

Trying to design some elements intuitively, just by setting classes and seeing how it looks; also prototyping. With Impulse, I can just cycle through all possible font-sizes / margins / paddings / shades of a color / you name it. I've designed the whole impulse.dev website with that approach and I don't wanna go back, it's just so much faster and fun even compared to writing code on two monitors with 10 years of experience. :D