But really, it's more of a 'well most of the time it's 2π' so maybe it makes sense to use the constant that represents that number, and since we're talking about small details, '2.0*PI' is also longer than 'TAU' to type.
Yes, there's always people doing things differently, with different targets, and amazing results. I don't think it matters when it comes to the 'for real' factor of the practice though.
I could say that I've been doing daily animations for the past 1580 days, and that's definitely real in my book. Your call.
2. If you were following my talk at GitHub universe yesterday where I was livecoding (archive will be up "soon"), the rebuilds are fast enough I don't really care (simple stuff are <3s for me, even my latest dailies where I have heaps of extra stuff are averaging <6s rebuild time). The compiler (via lsp) catches most bugs beforehand, so I would say it is not very much an issue at this point. Using a cargo cache will make things far easier as well.
3. Exactly why I started using nannou (coming from using processing via scala)!
As for the "why nannou?", and sorry for being nerdy, but nannou is the only framework I know of that does color right: you are working "naturally" in LinSrgb with float16 precision per channel (if that does not speak to you, just look for gamma correction and go down the rabbit hole). The blending of color is exceptional if you're into that sort of things (I am: see for example in HQ https://superrare.co/artwork-v2/road-to-nowhere-12621 )
Nannou is also focused towards the future: there's been a couple of major backend rewrites from opengl to vulkan then webgpu (without any issues for the end-user if you were using the core nannou api functions): you get to play with the latest toys and finally you get access to your whole GPU. No need to stay in a OpenGL-centric state based workflow (that does not make any sense since years)! I've been able to run crazy compute shaders passes while making my own render pipelines _on top of what nannou does_. It's crazy powerful.
Also I have to say the team behind nannou has been wonderful in dealing with my requests over the last two years, and they always provided help when I needed (to be honest, I chose nannou because the team was in Australia, and as I am in Japan, it made communication easy). Huge thanks to them. Have a look at the github issues to see how nice the team is.
And with cargo, I'm confident (not very confident, mind you, but optimistically confident) that I'll be able to get the thing building again in a few years.
So if your interest peaked a bit, please try it, if you have any questions, join the matrix chat and ask away!
But really, it's more of a 'well most of the time it's 2π' so maybe it makes sense to use the constant that represents that number, and since we're talking about small details, '2.0*PI' is also longer than 'TAU' to type.