Well yeah!

That’s the CD part :)

We’re rolling the same thing, except with all our cloud infrastructure, our code, and various integrations.

Automatic deployments are so great, as long as you trust your integration process and test suites.

There’s a reason we value the local development environment.

You can run everything locally, the only use for the cloud environment is for CD.

Yep, just like electron or Tauri. A web view wrapped in a native application.

These are very common these days, it’s the same use case and value proposition. Mainly because it’s just easier to develop UIs with web technologies that look the same everywhere, never without the app.

You do know that a pwa can be packaged up in an app container and you won’t even be able to tell the difference?

It doesn’t actually have to operate like a pwa, and require native pwa sport.

There are tons of apps that you use that are just well packaged PWAs, packaged as an app store app, and you don’t even know about it.

PWAs only suck on when they suck, just like everything else.

Oh, you get the benefit of explicit scanning?

We get the beauty of every file that’s modified being scanned before the write “completes”. It’s an absolute joy starting a build and watching ~80% of the available compute be consumed by antivirus software.

Or, you know, normal filesystem caching as part of your tool’s workflow.

Or dependency installing and unpacking…

Or anything actually that touches a lot of files.

No, no they are not.

Bad ones? Yeah, just like that.

I got the feeling that these replies are written by ChatGPT?

I mean, that could be extreme, or really not that bad.

Refactors have a way of generating a lot of changes. Half our job is code review, kind of have to get over it and go read some code.

If someone put the effort in to write it, it’s your responsibility to put the effort in to read it and review it.

If the style is difficult to read and non-standard for your repository or not. Conventional then your repository and your engineering team should be following set standards to ensure consistency.

If you’re doing this then most PRS shouldn’t be that difficult to review.

I say this, spending a decent part of my week reviewing something like 40+ PRs.

Kagi literally documents how this works in their blog post about it: https://blog.kagi.com/kagi-privacy-pass

Perhaps you should start reading before writing?