What I really don't like about thread/matter is that it is becoming the de-facto standard that thread border routers are connected to the internet.
This will in time result in IoT devices that actually mandate this connection (it was already stipulated in a recent version of the protocol). The end result will be that a new protocol was created, but rather than devices being able to run on their own, we end up with beds in heating mode, ie. the garbage we were trying to avoid in the first place.
A lot of zigbee infrastructure also expect an internet connection.
These border routers also double as admins, and people want their smart home stuff to be available while they are outside their home network.
Thread devices can mandate internet connectivity the same way Wifi devices can.
Matter defines profiles and does certification that says your light bulbs cannot require an internet connection. The admin your water leak detector connects into can (and arguably should) alert you even when you are away from home, but the leak detector _itself_ cannot do that and be certified.
> A lot of zigbee infrastructure also expect an internet connection.
Like what. I have several hundred zigbee devices of almost all category you can think of, and I have never come across such a requirement. I don't understand how that would even work.
Any reason you prefer Matter rather than Zigbee? Zigbee has been a thing far longer than Matter, so I don't think the "one more standard" criticism is valid here.
It is supposedly an open source standard that do not requires internet connection to work, and can use regular wifi (2,4ghz) networks as a means to connect devices so you do not need to buy a hub for them. You can create your own hub with a mini pc for instance with a regular wifi card. No need for specific hardware
I think that "hate" comes from the "write once" language fact. Perl is quite cryptic to read... even if it is your own script. That's why raku appeared
Windows beta testing has worked this way for 30 years, if not longer. I was a 'public' Windows 98SE beta tester. I downloaded new 98SE ISOs over 56k once per week and wiped that machine clean once per week.
The only compensation I ever got was from beta testing DirectX 5?, I think, and I received a MS Force Feedback Pro joystick for filing the most bugs.
You are actually testing for both, as an insider your feedback is asked every now and then, also you report issues you encounter willingly (Get Help metro app) or unwillingly (System Service/App stopped responding, collecting data and sending it to MS)
"Insiders" get (got?) to use Windows without license/activation as long as they stay on the latest version. That can be seen as "payment". The rest of the users get to offer QA services for free, after the repeated layoffs in the MS's QA departments.
I basically stopped using "stack overflow" web to help me find code issues. Now I just ask the model. It's usually faster and much more concise. Also many of my google search has been discontinued and just use a model to ask what I want. The only problem is about being updated. Models have a set of trained data so new content is not there. So for very recent or new things old "googling" still there...
-To learn try something easy and well structured as Pascal or Ada. Those languages will teach you organization and well structure code. C family of languages are extremely loose and vague, avoid them if possible.
-After learning the basics go for python if you like data science or machine learning.
-Go for javascript if you plan to do frontend with react or just web development.
-Go for rust/ada for system programming.
-kotlin or dart/flutter for android. Swift for Apple systems.
reply