Fun game! I made it to 31 😄

Or maybe 90.deg? Idk which makes more sense

Considering embracing it and adding a .rad method to Number.prototype so you can do this kind of evil:

Math.cos(90.rad);

There are no text boxes in my case; it's all just code. I want ease-of-use while also being interoperable with other JS libraries (Three.js, D3.js, etc)

Fuck, that's a good argument

In the US Who Wants To Be A Millionaire? 2nd edition video game from Eidos & Jellyvision, entering your name as "Regis", "Millionaire", or one of the actual $10^6 winners on the show would result in the game changing your name to "Faker" or "Cheater". So I could not play the game as myself.

We'll crossy that road when we get there...

By "more accurate" do you mean in terms of being mathematically proper?

Degrees, much like fahrenheit, are less affected by floating-point errors than their more "compact" alternatives

Both arguments are valid: we need not concern ourselves with the level of optimization and compression needed in the 90s, yet many programmers (across all disciplines) neglect it entirely and risk being careless with memory/compute resources

That's the way that I like to work as well! It also makes debugging more intuitive (37.9271° is easier to visualize than 0.622 radians)

Incorrect values being values outside of -π to π for radian functions, for example?

This feels like The Way™

I'm considering creating my own trig functions that wrap JS's internals with a deg-to-rad conversion

In my case, all the built-in trig functions in JS's Math object use radians, but I'd like to use angles for my methods. I dislike the overhead of "what does this function expect?" but also don't wanna add a "Deg"/"Rad" suffix to my functions