Re: [fxtf-drafts] [geometry-2] Proposal: Geometry Utility Methods (#602)

If we're proposing expanding the web platform, it should be to meet common needs when creating things which will run on it. It's important that we resist the urge to get too specialised, and that we take a step back to consider whether we're assuming our own very specific requirements are more widely applicable than they really are?

The original proposal includes providing methods such as "contains", which are obviously useful, and seem applicable in a lot of general cases, so adding them makes a lot of sense; whereas some of the other suggestions feel decidedly niche to me, as someone with admittedly only limited experience using geometry libraries, but who therefore probably represents the more general potential consumer of these proposed additions.

If we continuing down the path of packing everything into the web platform, we'd end up with things like full games engines (which I'll be honest, I'd expected Google to implement years ago, and am surprised we've still not seen) or libraries for handling things like financial information. There are plenty of games out there, and many apps that manipulate financial data which are delivered as web apps, but I don't think many people would argue that this functionality belongs in the web platform itself.

-- 
GitHub Notification of comment by ciw1973
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/602#issuecomment-3044215914 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 7 July 2025 09:44:50 UTC