Asmod4n

Depends how you use it, just last week I’ve hit 40 nanoseconds unpacking a 8 megabyte msgpack array and accessing one of its values in a hash.

As long as you only use ruby as glue code for c(++) extensions it’s pretty fast.

I’ve tried to write something similar for mruby, saw the 90% performance hit compared to just using callbacks and never released it as a mgem.

I’m getting different results for it with every reload, is that normal? Ranges form 56-96%

Nissan hat the e-POWER system where a petrol engine is just used to recharge the battery of your electric car and nothing else. In theory they could run that petrol engine at the sweet spot where it produces the least amount of carbon emissions.

i believe there is also a chinese company which is making such a car, their cars have nearly 1000 miles range.

Are you saying it’s impossible to misuse disabling the accept syscall but it’s prone to misconfiguration with disabling io_uring_enter?

There should be no issue with disabling it altogether by banning its setup and usage syscalls.

I'm about to start something like this targetting epoll, poll, dispatch_io and maybe kqueue this weekend.

An average human being can produce around 650MB of text during a while work lifetime when doing nothing but write text 4 hours per weekday without any interruptions.

Saying multi gigabyte databases for single user usage is the norm feels insane to me.

The System you keep your wallet on must be secured like a bank. Because the app can do nearly everything a bank can do (except refunds)

Great, their new devices actually work in thread mode with HA, but their older ones only when you got an Apple hub device. I’ve got 6-7 of their devices before matter was a thing and 0 work with HA. Even those that got firmware updates.

They work without issues Ine HomeKit mode. With thread/matter only Apple got the keys or whoever paid them to get them.

Also: the Apple home app can’t change their mode to matter, you have to do that in home assistant.

Buy a device from the manufacturer “Eve” try to add it to homeassistant after upgrading its firmware to use matter/thread: no can do, they don’t give you their key to talk to their devices.

You can’t talk to other devices unless you got the private key of them.

i had hopes to find a elegant solution to this issue in modern async io libs. Those I have found just simply ignore the error and forward it to the user.

getservbyname Is also one of those functions, it returns NULL on error or for signaling it couldn’t find what you looked for.

You can share them via airdrop

no GUI lib for cosmopolitan libc yet, afaik.

CD Text is a thing, sadly no major label is using it anymore to embed metadata into their records so such a thing like MusicBrainz wouldn't be needed.

Sony was a big supporter of it ~25 years ago.

It’s one reason i don’t like WSL2. When you compile something which needs 30 GB RAM the only thing you can do is terminate the wsl2 vm to get that ram back.

They even removed most mentions of it where they talk about firmware, that’s a shame.

Correct, this makes it possible for one chip to speak both protocols at the same time with one antenna.

The usb stick sold by nabu casa does that.

IMHO, thread and matter will probably be as mature as homeassistant and zigbe2mqtt in the 2030ies. At the moment, Zigbee devices can work without any hub as long as you stick to one vendor.

Aka buy lightbulbs and switches from ikea and you can right out start using them, I believe you only need a hub to create groups of devices which then can get controled with one switch. You then could unplug the hub and still use them, only needing a hub for ethernet bridging and automations.

But here comes the tricky bit, when you buy either Zigbee or matter devices each vendor will add its own extensions.

In the Zigbee ecosystem vendors out right refuse to communicate with devices from other vendors even though Zigbee is an interoperable standard.

That lead to the birth of zigbee2mqtt, literally hundreds of years of development time went into it to have full feature support for every Zigbee device that exists.

For thread and matter devices each vendor would have to do the same. And that won’t happen, leading to a fragmented ecosystem.

Thread and Zigbee implement the same IEEE standard.

Matter would be correctly the application layer protocol of thread and could be spoken over any transport. Like HTTP

Thread is using the same protocol as Zigbee, which requires specialized hardware to talk to it. You can’t get around a centralized hub when wanting to use them on your WiFi network.

Thread just adds an IP layer above Zigbee. Zigbee is on the same protocol layer as Ethernet or WiFi.

Oh and, Zigbee has automatic range extension as part of its standard. Every device with a plug expands your network.

Thread is a WiFi replacement, the devices talk IP over thread.

And it has an encrypted pairing process to your vendor controlled hub. Said vendor can allow or disallow it which other vendors may speak with said hub.

Here is the landscape we have: HomeKit: fully closed, requires certification from Apple. Very expensive and limited functionality.

Zigbee: fully open, anyone can make Zigbee devices and sell them without any restriction. Operates on the same frequency all over the world. Devices are super cheap. You can expand the protocol however you like as a vendor.

Z-wave: fully closed, several incompatible frequencies, requires certification to sell devices.

Thread and matter: semi closed, same ieee standard as Zigbee for data transfer. Vendors can allow it to talk to devices of other vendors. Requires certification. Same price tag as HomeKit, aka 3-4 more expensive than Zigbee.

All of them require hubs. And only with Zigbee you are guaranteed to have interop between all vendors and all devices sold across the globe. Thanks to Home Assistant. With thread the vendor can simply disallow you to use your devices with HomeAssistant, which is unacceptable by me.

thread and matter will, in my opinion, never matter for consumers. Why? It’s basically a walled garden.

Think HomeKit but a tiny bit more open, the open bit is, that a vendor can allow it to communicate with devices of other vendors. But they don’t have to.

Thread also needs more expensive SOCs, with Zigbee you only need a tiny micro controller with a few MHz of clock speed and a few KB of RAM. Thread and matter on the other hand can require megabytes of RAM.

Vendors which nowadays sell HomeKit devices can reuse their SOCs for thread matter, keeping their 3-4 times higher prices compared to devices with the same functionality from Zigbee vendors.

Can this be mitigated by putting the cables under ground? Just curious, since it’s a huge debate here at times because of the massive cost of doing so.

Germany needs a connection from the coast into the south and most of it as of now will be build under ground.

The case maker HYTE calculates 25% as net margin for brick and mortar stores for MSRP and says stores are tough and won’t allow any % less margin.

Update: oh and they also said stores won’t lower it because of the tariffs, making the stores more money.