Apologies! I think I might have a found an eager redirect on the server. I haven't been able to reproduce, but you're not the first to report it. I hope it's fixed now.
I'm glad you're taking my feedback in stride. To be honest I regretted the harsh tone as soon as I hit submit. Can I blame it on oxygen deprivation? :)
Easily one of the worst UI's I've seen since 2020.
Timing the initial in/exhales is tricky, because the circle contracts, not to its center, but to a nearly invisible (on my screen at least) smaller circle in the middle. No visible counters.
After a while, it just says "Hold". No indication that we're done. And I sit there, almost dying for 2 minutes before realizing, that it's done some kind of quiet-quitting routine on me.
Really great work, I liked the video, even had a good laugh. But I was surprised to learn that it would cost 1000$ to make something which is still... very clearly artificial.
My experience is the opposite, I've only met incredibly friendly and helpful people within the functional world.
Your description of a person who has to put down everyone else in other to raise himself up, is just person with such low self-esteem that it's become toxic. You'll find these people everywhere, it's not exclusive to FP.
I'm personally fairly rigid about implementing business logic as functionally as possible, but I also enjoy game development which is inherently stateful and never without some imperative parts. I do think FP has some advantages over Imperative programming in many instances, but the opposite is also true, and I'd never pretend to be smarter or better than someone like John Carmack, who's made his career almost exclusively in Imperative languages.
> Typed languages are essential on teams with mixed experience levels
Essential, meaning 'cannot exist without', it's not. I've seen this work a number of places.
> Blind devotion to functional is dumb.
Managing/limiting state is always a worthwhile pursuit. I'd think he would agree since he seems to value simplicity
> People who stress over code style, linting rules, or other minutia remain insane weirdos to me. Focus on more important things.
That's like saying don't check if your cars tires still have any pattern left, the engine is more important. Until it isn't. Streamlining the smaller details allows the brain to focus on more important stuff, but the details matter and their value increases exponentially with the size of the project.
I wonder who he keeps running into. Not only do I use Linux on a daily basis, I run about 20 virtual *nixs from that Linux desktop and everything runs really great, but when I run into problems, the Arch community (ie. colleagues, forums, mailing lists) have been nothing but extremely helpful and friendly. Without exception.