@synalx Deep dives on design decisions, trade-offs for different considerations on how to implement new features, indeed what Ryan Carniato brings but then for Angular
@laforge_toma@angular signal forms, HMR per component when TS of component changes, a sort of react-scan in angular devtools, native angular-cli vitest support (+ browser)
@xocomil_1@angular@analogjs Not exactly. Our e2e testing pipeline didn't see any difference in duration for example. I would have expected to shave off at least a bit. You can see it struggling here: https://t.co/sMzT1VOe8W
@mbleigh Relational queries pleeeeeeeeeeease! Not sure about the performance cost but https://t.co/V121aOLNfA seems to say that it's possible with nosql as a base architecture
@stephenfluin@jamesuriah You can read similar concerns/delays about the upgrade for the latest firebase version here: https://t.co/cY6G2OgU1p
The same concerns have been repeateding/intensifying over the last 2 years IMO with every new release. Because of this we are planning to move away.
@BhosalePratim A step-by-step guide for automatically spinning up an instance locally per developer + in a CI and injecting those instances with start test data + run integration/e2e tests against it
@jeffbcross We run 8 playwright browser instances in parallel in our tests while it's not really having an effect on working. Rough guess is that the run goes 4-10 times faster than on a cloud instance (my estimates are 4 years out of date ;))
@jeffbcross Yeah indeed, I seem to remember I even researched which provider let us do that and I only found Azure DevOps at that time I think. Main reason was time of the run.