Alpha 27 of 0 A.D. has a notable performance regression for a subset of users, compared to earlier versions. Users not affected by this regression should see improved performance, thanks to improvements like the added Vulkan support.

The regression in performance seems to be caused by a change in Spidermonkey. For details check out https://gitea.wildfiregames.com/0ad/0ad/issues/7714

That said, even without this performance regression, 0 A.D. is prone to run slow in late game when lots of units are on the map. There are several reasons for that, but maybe the most intuitive one is that 0 A.D. is still largely single-threaded and therefore doesn't make use of the multi-core capabilities of modern CPUs. As you can imagine changing that is no easy feat and takes a lot of effort. As the number of volunteers to 0 A.D. is limited, nobody has picked up that topic yet.

If you enjoy 0 A.D. and want to improve it: it's Open Source and contributions are always welcome!

The Framework Laptop 12 is new, you probably switched to a Framework Laptop 13.

As it's visible from existing material the bezels on the Framework Laptop 12 will be huge and as it's a touchscreen, its readability will be worse.

From all what I've heard over the years, they have a problem staffing the service teams. I imagine with the AI craze that just got worse, as they certainly shifted resources to work on that.

If they really have staffing problems, it'd make sense in the short-term to shut down services which don't bring in much revenue. In the long-term that might fire back if AWS customers loose trust in the services they're using still being there in the future.

The obvious solution to a possible staffing problem would of course be not fire a certain percentage of your employees every year.

> "When we want to innovate. When we want to really, really innovate on interesting products, I have not seen an ability for us to do that when we're not in person," Garman said.

I have the suspicion that this is not caused by remote versus in person, but rather by not giving engineers enough space for innovation. All you hear is that teams are understaffed at AWS.

Also a high turnover rate caused by regularly firing a certain percentage of your employees certainly isn't beneficial either to solve understaffing and foster an environment where people innovate.