80 karma · joined January 13, 2014
if I was in your shoes, I would assume that once the feature is merged, the maintainers have final say and can modify or remove your code as they wish. An RFC for a breaking change would surely be nice but I wouldn’t expect any kind of notification if the change was some kind of minor update or enhancement.
If you’re looking for something you can configure every little bit of for a very large team (like Jira) it may not meet your needs, but otherwise I highly recommend.
I don’t see what the nuance is you’re getting at with the mixin vs object method argument though. They both have the same issues around testability and violation of SRP.
Canon is still making cameras, and Sony is having more success than ever with the mirrorless transition. Changing the label doesn’t mean that photography is dying.
I don’t disagree with the overall point you’re making, I’m just pointing out that it’s very common
For a basic CRUD app, especially for a solo dev, the monitoring story on Vercel is sufficient and it’s hard to say that their single repo push to deploy setup is more complex than the traditional alternatives.
How do they test things on production? If there’s a bug how do they revert to the previous version? There are way more issues without source control than with.
Affinity Photo is also on the same level as PS, I don’t know about “surpassed” but Adobe is no longer the clear leader.
Alternatively, it’s pretty common to only run prettier on changed files using lint-staged or pretty-quick.