Hah, yeah a hexagon is a weird case. In my experience, devs talking about “math in a custom view” has always meant simply “I want to render some arbitrary stuff in its own coordinate system.” Sorry my assumption was too far. 😉

You should probably use matrices rather than trig for view transformations. (If your platform supports it and has a decent set of matrix helper functions.) It’ll be easier to code and more performant in most cases.

I feel ya, but consoles are a different beast.

Reasonable people can debate how the pricing should be structured, especially when it comes to online functionality that doesn’t even take a penny of Nintendo’s server budget…

But I don’t think it’s reasonable to expect zero cost at all, when:

• Console manufacturers have an unavoidable incentive to sell hardware at a loss (even without factoring in the platforming costs+risks) and make up for it in software sales and add-on services
• …and they suffer the reputation hit if any of their offerings are not up to par, in a way that e.g. Windows does not, so they have an unavoidable interest in monitoring and triaging issues with games
• …and networked components tend to be the most sensitive and most traceable part of any software system
• …and scaling issues tend to be a cross-cutting concern that a third-party vendor who isn’t intimately familiar with the client codebase can affordably help with

It’s just part of the deal you make when you sign up for a walled garden. You get certain guarantees, but only if you pay for the relevant package. You can’t have it both ways – getting the benefit of first-party backing while enjoying the freedom of a purely third-party environment. It’s like a cruise ship that doesn’t let you bring your own alcohol.

Why do you refuse to pay for NSO?

Oh neat: https://github.com/AsahiLinux/docs/wiki/Apple-Platform-Security-Crash-Course#apples-unspoken-agreement

It is apparent however that the platform security model was engineered to allow third party operating systems to coexist with macOS in a way that does not compromise any of Apple’s security guarantees for macOS itself. Rumours circulating that Apple are actively hostile towards efforts such as Asahi, or that their security must be bypassed or jailbroken to run untrusted code are unfounded and false. In fact, Apple have expended effort and time on improving their security tooling in ways that only improve the execution of non-macOS binaries.

So if Apple complies with this new ruling in a similar way, we could expect to (eventually) have the same level of security on a third-party OS!

So are we gonna get an alternative OS for iPhones? I wonder how that would even work, with the hardware-level security that I assume requires a signature that Apple won’t wanna make publicly available.

And what about the SDKs? Would you be able to reuse the Apple-maintained ones, or would we need FOSS reimplementations – or would that even be possible without violating IP?

Cuz some of the ways that Apple achieves privacy while enabling functionality (I’m thinking things like ARKit shared sessions) could be considered trade secrets, and I wouldn’t be comfortable using an alternative that doesn’t provide the same level of privacy…

In a statement, Apple told Bloomberg “We remain very concerned about the privacy and data security risks the DMA poses for our users.”

Usually, the “We’re gonna fight this!” response the corpos publish when we do antitrust action is like “Yeah sure buddy, whatever you gotta tell yourself”. But this one does actually ring kinda true for me.

macOS all the way.

All the comfort of a UNIX FOSS env, all the premium features of a corpo env.

So many reasons. JS has a small standard library, a history of competing standards for things like asynchrony and modules, there are tons of different implementations against tons of different specs, running in tons of different environments (whose constraints and opportunities are also changing all the time), it tends to be the first language to receive an SDK for many services, packages tend to be almost-excessively granular because optimizing for size can be so important on certain platforms (tree-shaking and minification works, but takes time), there are many add-on languages like JSX and TS, there are tons of bundlers and transpilers which each have their own quirks… and also due to its unique position as the lingua franca of client-side web, it tends to be the primary battleground for researchers, tech firms, VC, FOSS, malicious users, and everything else.

To stay alive in an ecosystem like that, any project must become a “ship of theseus” kind of deal.

You may be interested in yarn’s “zero-installs” option: https://yarnpkg.com/features/zero-installs