oweiler

Or use tests and/or a debugger. Which gives you all the listed benefits w/o an additional dependency.

So like Testcontainers Cloud?

That game felt like a graphics demo though. Almost unplayable.

His first "what" example actually explains "why" clear is called two times. The code perfectly captures the "what".

It just gets rid of the boilerplate. Never had a problem with ctor injection in Spring.

Use the builtin Result class and runCatching/fold and be done with it. Yes, it has shortcomings but works well enough in practice.

This is honestly the main reason I prefer Playwright to Cypress. Playwright leans heavily into using POs, while for some reason Cypress doesn't.

So in almost every project the Cypress tests are a procedural mess, while the Playwright tests are mostly well structured.

I know that Cypress has other patterns for dealing with this but they never seem to get applied.

I use Starship without any customizations and its good enough for my every day use.

Reminds me of a game I've played on C64 AS a kid.

Bash has no standard library. It has builtins, and commands. And commands are just external tools.

I have read almost the same thing 5yrs ago. And 5yrs before that. And so on.