It looks like configuration management for devops. If I have an app and want it run in 3 different environments that each have rapidly changing configs, I might use this. But I won't b/c Facebook.
"But I won't b/c Facebook."
Do I understand correctly that you also personally boycott React?
Are you insinuating that it’s unimaginable that someone would boycott React because Facebook?
I did (and do).
>"But I won't b/c Facebook." Do I understand correctly that you also personally boycott React?
I do. Is that surprising, though? Given the variety of tools/frameworks to build interactive web stuff, there isn't a single thing React offers that cannot be found elsewhere.
I do not boycott React because of Facebook. It's because its inferiority.
Inferiority to what? I hate Facebook as much as the next self respecting Netizen, but I still use React at work because it's just the best tool for the job. I'd be happy to hear some arguments to the contrary.
React is kind of the best one right now. I wonder if Apple’s new React-ish thing will prove to be an improvement and be ported to JS.
I work on the backend so I have a de facto boycott. On the front end I'd probably be forced to use it until something better came along.
Your profile has an Instagram account, are you aware that Instagram is actually Facebook?
Oh no. Well, as long as I have my WhatsApp I should be fine...
All, too, well aware. After Facebook bought Instagram was the last time I saw Kevin and Mikey (IG's co-founders). You're right to point this out, but I'm very ambivalent: a tool that I value from a company that does reprehensible things.
Devops scripts are definitely a good use case, but so is machine learning research, which requires a lot of flexibility.
The origins of the framework is in ML, not devops.