<d1b2>
<fjullien> @dragonmux what sort of trouble did you get with LiteX ?
<d1b2>
<dragonmux> general readability, understanding what was on which domain, constructs being expressed very confusingly making it hard to model in our head, and the lack of type information to get VSCode to help make sense of the mess
<d1b2>
<dragonmux> thing is.. diagrams.. great.. but Amaranth entirely solves all of our gripes without needing to resort to diagrams that can get out of sync with the logic
ChanServ has quit [shutting down]
ChanServ has joined #amaranth-lang
<cr1901>
I wish LiteX used the omigen compat layer in amaranth, but Florent didn't want to risk breaking compat (which yes I understand, but still...).
<cr1901>
s/compat/breaking existing designs/
<whitequark>
yeah
<cr1901>
Anyways, Idk the future of "what lang will LiteX be written in?". LiteX is more a "SoC manager" nowadays. Amaranth-soc may one day be a viable alternative.
<whitequark>
I think I'll deprecate amaranth.compat
<whitequark>
it hasn't seen more than incidental update, I think
<cr1901>
I have one design that uses it, but it was explicitly to test the compat layer. It's _really_ not a big deal to rewrite it.
<_whitenotifier-9>
[amaranth-lang/amaranth-lang.github.io] whitequark 0be8f1e - Deploying to main from @ amaranth-lang/amaranth@427c82fcbc9e40caa8b22543cb728ff720e64887 🚀