I'm sure this is just a troll post but wouldn't anyone your property management "caught" using this device simply say they used off the premises and that would be the end of it?
Not a troll just frustrated that potheads are contaminating the air in my state. I can’t walk a mile with my kid without smelling pot in the air. The smell and the effect of irritating my eyes is worse than a cigs smoker standing next to me. To answer your question they could but their apartment will smell like a pot factory once the property management goes into check.
> which means runtime errors in the object tree usually causes the entire app to crash with very abstract error messages.
This is absolutely untrue. Xaml errors can be caught like any other error, and most errors get swallowed rather than crash the application (which can cause some debugging headaches when things aren't rendering as you expect).
> I used to think XAML could be better if architected well, but the missing ecosystem and usage around it made it so, that HTML was and still is massively more productive.
I don't think html is massively more productive. I'm not even saying that WPF is so much better, but start debugging any reasonably large react application and you're just as likely to get into an unproductive quagmire.
Your comment reads that you're angry at Github for not taking a more open source approach. That's a fine opinion to have, but it doesn't make sense to demonize them for being a for-profit company. They are not robbing anyone of anything.
Starving the competition with loss-leader tactics is not an unbeatable strategy. If, however, you don't have anything to offer other than a run of the mill payment processing platform, then yea, you're going to have a tough time beating someone who can cut costs. They have a feature you don't, you should lose.
$20 is less than a drop in the bucket, but $20 dollars for essentially a donation is another matter. For the companies that already contribute monetarily to open source, I don't think much changes. The unfortunate reality is that for companies who don't, not much changes.
jetbrains is doing a very good job of creating good error messages, but just like any other jvm language, you can run into huge, messy, jvm stacktraces. In my experience, Java/jvm proficiency is useful
lambda's are much more limited in flexibility when compared with linq. Because of the way java lambda's work, I imagine there are some scenarios where they are more performant, but it probably comes down to the specific problem/usage.