I had the exact opposite and it was hilarious. Every time my manager (a great guy and really good at what he did) was away for a week the sprint would go very smoothly.
I have been on the 'receiving' end of such persons actions. We had one guy who worked probably 50% of his time on using
not F#, but another "nice" thing. It never worked well and he spent an incredible amount of time patching it and fixing issues with it. I threw it out the day after and replaced it with some older boring technology, and the problems just went away.
Meh... after not more than my first month into D this syntax grew on me and now I just use `1.writeln` everywhere. More than a few years later, I can't think of a single issue this has ever caused me.
UFCS as a concept is fantastic but the one hangup is that D's language server implementation by the community and
its IDE integration can't handle it because of the complexity.
It's possible to implement, because Nim's language server handles UFCS, but atm D's doesn't do it (it's written pretty much by one people)
So personally I avoid UFCS except for very simple/common function like "to!" because it breaks the intellisense for that call.
Though if I knew the language inside and out probably I wouldn't care.
It's still my "favorite" language.
-----
SIDE NOTE: This single person wrote the D lang server, and has maintained it, written and maintained the VS Code extension, and other fundamental tooling + libs for years.
If you use D and feel like sponsoring someone, consider sponsoring them, or Rainers (VisualD), or the maintainers or LDC or GDC, also single individuals for the most part.
The language server doesn't do it because it's only a parser whereas making UFCS work properly would presumably require a full semantic analyser. By no means impossible to do, just no one has taken the plunge yet.
My guess is it's a Microsoft shop where the most used technology was ASP.NET Webforms and then later Angular. They saw that Telerik (a favorite of enterprisey MS shops) had a cross-platform app framework based on Angular, and they decided to stick with what they knew. I've worked at a couple of these places.
You don't even need to do that! 6 years ago, I was exploring cross-platform mobile options (RN wasn't available for Android yet, also it was brand new and not to be trusted. It turned out OK in the end though.) and Native Script was one of the options I looked at. A couple things instantly made me reject it.
1) The official demo apps were slow and janky. (hmm, reminds me of Flutter. I don't think these guys will be much happier with Flutter, honestly)
2) It was made by Telerik, the company known for bloated and slow ASP.NET controls. Also, surprise surprise, poor documentation.
Eventually, I decided to make 2 separate iOS and Android apps.
> The official demo apps were slow and janky. (hmm, reminds me of Flutter. I don't think these guys will be much happier with Flutter, honestly
The Flutter web demos are slow and janky on some devices and browsers due to depending on WASM, which isn't universally suppported yet. Mobile Flutter apps are sometimes slow ( e.g. the new Google Pay), but they have no obvious excuse to be ( UI in Flutter is really fast, 60fps all that).
That was probably the right call on your part. Though if someone was insisting on a single code base to save money, I'd probably go with Xamarin because if the framework doesn't supply what you want, you can always drop down and code against the native toolkit.
I still do this on Spotify. Scroll through the new releases and if a cover looks interesting, I give it a listen. Having grown up in record stores, I love that I can listen to anything instantly. It's pretty insane actually.
Let me just say, it's nice to see a sane comment every once in a while. The world seems to have gone completely off the deep end and is throwing itself at the mercy of petty authoritarian bureaucrats.