frak.js is getting a revamp this week. Check out the GitHub repo for a preview of which issues I'm addressing.
> npx @frakjs/frak init
https://t.co/a9v5pLSPpe
>hey opus please go remove <thing>
opus: <thing> is now removed. I added 4000 lines of tests asserting that <thing> no longer exists so that it can't come back without us knowing.
I always like to keep an old computer around.
Because everything runs like a dream on that brand new M5 Macbook, but will your behemoth of a JavaScript app run smoothly on your users hardware if they're running old specs? Probably not.
@Gaus450 Because most people don't want to make so many decisions when it comes to customizing. They actually get decision fatigue or freeze and don't know where to start.
@pmitu You can compress many parameters/vectors/tokens per qubit. But there's trade-offs. I'm still researching, but I think as the labs experiment with this crossection of tech it will be really interesting.
@PovilasKorop Oof. Running unit tests on every commit...would love to, but our repo's tests take 40min on a dedicated GitLab runner. That's an issue in and of itself. Maybe pre-push, if that's a thing?