It could be the three.js shader on the page that they use which renders in the background. I think you may be able to disable shaders to test but not sure. Been awhile.
Want to point out, it does run pretty quick on my iPhone surprisingly (and faster than my other dev laptop :-P). Almost forget how much power phones have...
I’m a bit alarmed by the many issues here. I’ve heard a lot from the maintainers but much from the foundation.
- continued lack of communication
- for so many issues to occur to multiple parties paints a picture of it being routine
- that no immediate reversals have happened with utmost immediacy
- the ethos of the maturity model
- the policies apparently being enforced - even now…
- for calls to solve things privately
It’s culturally indicative of the foundation’s values whether they know it or not.
A healthy community is one where discussions happen in the open, good and bad.
This is not good, and I’d recommend the community coming together and maybe finding or forming an alternative - which is difficult I know.
Yeah, the (continued) lack of communication is not great. But the timing is admittedly pretty poor for the .NET Foundation as well. They just brought on new board members this week. So delays are kinda' expected... but I would have communicated differently.
For sometime now GitLab could be made aware of Kubernetes deployments. That is you added the integration of through your build. This allowed you to see your build through to the “deploy” phase.
All this new Serverless functionality does is now provide a window to see the Serverless workload rather than just your traditional pods.
If the laws still do not deter then increase the penalty until they’re adhered to. Such that it will leave no such question as to whose responsibility it is.
