t00

"Every request spawns a fresh process" <- this is when I stopped reading to save some time for the latest news in AI. Apologies for an abrupt interrupt.

Is there a chance for a Linux version?

/FIFY A year ago this would have been considered impossible. The software is moving faster than anyone's hardware assumptions.

We do similar but sprints are somewhat flexible, more like versions. We chuck the features we want from the top of most needed, split into stories and estimate like you mentioned using brainstorming between devs and QA. Estimation happens by relatively comparing complexity of each new story compared to previously implemented stories, conservativy picking average one up if there is variance in estimates. QA is involved to determine how long it will take to test the feature or sometimes what uncertainty is there if this is even possible automatically.

In the end we have stable developer velocity metric and a really close estimate for each new version.

Closed, iOS only, invite only. Thanks.

Orwell was a licenced critic even if anti-imperialist at heart he sold his soul to fight communism putting imperialist issues aside.

As much as I agree with app deployment headaches, apps provide something a website cannot (except PWA) - ability to do stuff offline, log and register data which can be uploaded when connection is re-established. When talking about user experience - launching the app, selecting new -> quote -> entering details -> save -> locking the phone without worrying or waiting, knowing that it will eventually get uploaded, is much more convenient than walking with the phone around the property to get better reception to even load the new quote page.

UX matters, and user does not care if the native wrapper or 500kB of js is there or not, as long as the job is done conveniently and fast.

Am I missing something here? The mobile SPA app can be deployed using tools like capacitor to a device and the framework along with all static content is loaded into the app bundle. In such case it makes no (realistic) difference which framework is selected and it matters more how the background/slow transfers are handled with data-only API requests, possibly with hosted images. With the background workers PWA can be built as well, streamlining installation even more.

That is a really good advice, copying data everywhere makes only sense if the data will be mutated. I only wonder why, why C-style strings were invented with 0 termination instead of varint prefix, this would have saved so much copying and so many bugs knowing the string length upfront.

I have exactly opposite experience, Delphi was awful UI, verbose language experience, with hops and tricks and a ton of Win32 rendering to do simple controls like a ComboBox with checkboxes. Yet the community was brilliant, always helpful and SO questions answered the same day!

Agreed about your points, not so much about paper drink straws.

Both Apple and Android (stock) are candidates for anti-monopoly regulations regarding the limited, vendor locked backup API.

Enforcing choice of the backup solution would solve the problem of rogue countries like the UK meddling with privacy and security.

Like the browser choice, backup provider choice can end up being enforced, likely by the EU as they have a good history of breaking up vendor lock-ins.

Possibly an information/lobby campaign can be started and endorsed by some major online storage providers?

There are examples of cat and cp using io_uring. What are the chances of having io_uring utilised by standard commands to improve overall Linux performance? I presume GNU utils are not Linux specific hence such commands are programmed for a generic *nix.

Another one is I could not find a benchmark with io_uring - this would confirm the benefit of going from epoll.

One short key point to remember. Browser is a user-agent and regulatory issue is with browsers, not how users make use of them.

Sadly you're not alone