The Venn Diagram of people who ride motorcycles purely for entertainment, and people who like to annoy others by being loud and obnoxious is just a circle.
First, that is wrong because Venn diagrams don't work the way you think they do.
Second, even if they did work they way they think they do it would still be wrong. :-)
Venn diagrams show all possible inclusion/exclusion relations between the sets they are showing. A Venn diagram of two sets is always two circles that partly overlap.
Even if the way they worked is that you could omit regions that are empty and redraw the remaining regions to be circular, it doesn't help because ending up with a single circle with both sets in it would mean you are asserting the the two sets are equal.
That is clearly false because pretty much everyone can name someone who likes to annoy people by being loud and obnoxious but does not ride a motorcycle.
I just made the discovery the other day that there are two Arduino IDEs, the old crusty one maintained by Arduino.org and the new hotness maintained by Arduino.cc.
I'd been using the Arduino.org version which had mostly driven me to use PlatformIO and ESPHome.
Unfortunately, but perhaps fortuitously, I needed to use a Library only compatible with Arduino 3.0.0 which is incompatible with PlatformIO. That lead me to discover the Arduino.cc IDE which, while not on par with VSCode, is dramatically better than the Arduino.org IDE.
> But I've only programmed Esp32s using the arduino dev environment.
Well you can use PlatformIO/VSCode and the ESP-IDF.
If you're ok with the Arduino 2 framework, then you can use PlatformIO as well. Unfortunately Arduino 3 support isn't there yet so a lot of libraries like HomeSpan won't work on PlatformIO at the moment.
> Currently, they seem to favor xml-rs which only implements a subset of XML.
What in particular do you find objectionable about this implementation? It's only claiming to be an XML parser, it isn't claiming to validate against a DTD or Schema.
The XML standard is very complex and broad, I would be surprised if anyone has implemented it in it's entirety beyond a company like Microsoft or Oracle. Even then I would question it.
At the end of the day, much of XML is hard if not impossible to use or maintain. A lot of it was defined without much thought given to practicality and for most developers they will never had to deal with a lot of it's eccentricities.
This is, to me, one of the absolute biggest selling points for ZigBee and Z-Wave.
I can get some random, vendor I've never heard of, ZigBee sensor, and I know it won't do anything rogue on the internet because it doesn't have any way of getting to the internet.
Also, ZigBee is extremely power efficient compared to WiFi. With ZigBee, I don't mind putting a sensor in the crawlspace or somewhere a pain to get to. It won't need the batteries changed for a year or two anyway.
I know Matter can work over more efficient means than WiFi, but most of the cheaper devices I find are WiFi. A cheap ZigBee device is still ZigBee.
As I said, my experience has been that the cheaper products run on WiFi. I also don't like that a product advertising "Matter" doesn't answer the question of whether it uses WiFi or not.
I much prefer that a $3 ZigBee temperature and humidity sensor definitely doesn't use WiFi rather than having to dig to see if a cheap a Matter sensor uses WiFi.
> Gen 2, however, had no excuses. They had every opportunity to add active cooling and they still decided to go with just air cooling.
The Lizard pack in the later Nissan Leafs has held up surprisingly well. I have a 2015 that still gets 75 miles of range. I'm sure they thought it wasn't necessary and they probably had the actuarial numbers to justify it.
reply