dromtrund

In the case of NotebookLM, the AI generated podcasts aren't competing with existing podcasts, they're competing with other ways of consuming the source material. Would I rather listen to a real podcast? Yes. But no one's making a real podcast about the Bluetooth L2CAP specification.

I've found some still have a weird tendency to defend bad UX on apple products, even if it's obviously bothering them. I've heard similar sentiments as in the article too, especially about the app store, but it's not something people go around announcing to everyone anymore, like they used to.

If you buy a product that's more expensive, you'd be a fool if it's not superior to other products, so it's hard not to get personally invested in the idea that they are.

This is true, but this was never really a problem for the adoption. Spec delays, no firmware upgrade support, and most importantly no proper backing by phone or gateway vendors. Thread and matter seem to have fumbled their opportunity though, so it might not be too late.

Isn't named registers an advanced enough feature that it shouldn't be optimized for new users?

In the US, wages, vacation, healthcare, pension plans and care for the elderly are private arrangements set up by everyone individually (technically). The Nordic model is a collective arrangement, where safety nets are provided by the government, benefits are governed by law and compensation is governed by collective agreements between unions and employers.

Most families would provide for their own if it was required, but it's not a scenario most people ever need to consider, even as a backup, as bad luck alone can't put you in that situation, you'd need to actively seek it out.

> Contrast that to the last time I worked with Nordic in a professional manner, I had to sign NDAs to get the full documentation and toolchain

That has to be at least 5 years ago, but even back then, 99% of their software was out in the open. Now, their SDK is open source, their official toolchain is based on the Linux Foundation's Zephyr toolchain and their docs are open and buildable. Their support is done on an open forum and complete data sheets are available both as PDFs and (with the exception of the nRF51) as web pages. They aren't allowed to publish their LTE stack because of operator licensing, their Bluetooth link layer is still distributed as a library and some upcoming SoCs aren't publicly available yet, but aside from this, they're as open as they can possibly be.

> Think of yourself as the person you want to be, not the person you are.

I have always done this subconsciously, and although I can attribute a lot of my personal growth to this trait, it's also the source of a lot of self-loathing. If you can't accept the parts of you that differs from who you want to be, you'll spend a lot of energy focusing on perceived mistakes that others didn't even notice.

Odd not to see Zephyr mentioned at all, it's got way more activity than most (all?) of the projects listed, and many of the sponsors are actively involved.

Yes, actually. I have to charge for 30-40 minutes every 5 hours or so. That fits well with my meal schedule, and most charging stations are at or close to restaurants or shops. Charging at these stations is almost as expensive as gasoline though.

I wouldn't normally drive more than 1000km in one trip though, and that's at most once per year.

A VW Golf starts at 35800€, and a VW ID.3 starts at 32800€, taxes included. Overall, electric cars are a bit cheaper than their counterparts, but not a lot. However, today, petrol is 2.15€/l and electricity is 0.013€/kWh. That's 11.20€/100km versus 0.185€/100km for the ID.3, literally two orders of magnitude cheaper. Everyone charges at home, and there's also a 40% discount in toll roads, which saves me about 8€ per day I'm commuting.

With the 3k€ lower price, a range of 430km, and fast charging stations every 30km along the major highways, there's just no reason to pick the Golf.

We still have a PHEV in addition to our electric car, but there's no reason to. If we're going on a 500km road trip, we'll take the electric BMW i4, no question.

It's not obvious if you come from emacs, but the keyboard centric navigation is very different from traditional IDEs, that usually come with a wide array of buttons with weird icons at the top.

A few other aspects: - dark mode by default - web tech UI, not terminal - decent looking widgets and decorations

I don't think these are the main selling points for vscode, but they do all of this better than their competitors.

> studies will point that radiation are not harmful until they are.

Smartphones might genuinely be a thing future generations will look at asking "what were you thinking?", but this argument is completely moot, as it could be used against literally anything.

Studies will suggest that electricity is not harmful until it is. Studies will suggest that freedom of speech is not harmful until it is. Studies will suggest that touching grass is not harmful until it is.

This is true, but the connection request only comes on one channel. The sniffer can be set up to follow an advertiser though, which makes it jump to the next channel in the sequence as soon as the time window for sending a connection request after the advertisment is gone. It picks up connection requests virtually every time in this mode.

Both this and encrypted communication interpretation works a lot better than the commenter above you claims. They've either not tried this sniffer, and are only making claims based on assumptions, or they haven't learned how to use it properly.

It's definitely not as good as commercial sniffer hardware, but it's perfectly fine 90% of the time, and the price is two to three orders of magnitude lower.

I wrote some of the firmware for this sniffer. As others mention, Bluetooth Low Energy works on multiple channels, with connections jumping from channel to channel in a predefined pattern. Bluetooth stacks are implemented to act as one of the two parts of a connection, and there are no apis that would let you change this, as it's normally not relevant.

This sniffer is set up to follow the channel jumping, but instead of participating in the packet exchange, it just listens for both parts. As the channel jumps are predetermined, the sniffer can sleep between these events, then start the radio up to listen on the right channel at the right time.

The hardware does not support listening to multiple channels at the same time, so to follow a connection, the sniffer needs to listen to the connection establishment exchange to learn the timing and channel pattern for the connection.

Device discovery and connection establishment runs on three channels, but all beacon packets (advertisements) are sent on all three channels, so the sniffer only needs to listen to one of them.

The connection requests are sent as immediate responses to an advertisement. If we want to be sure we catch all connection requests for a specific device, we can choose to "follow" its advertisements, which are sent on each of the three channels in sequence.

The sniffer is implemented by interacting directly with the radio hardware peripheral, which acts just like a state machine with states RX, TX, idle, and a few warmup states.

3) isn't really practical without some storage mechanism though. Sure, you can make a change that sits in ram until the next power cycle, but you could do that with firmware too if you plan for it. Whether you store the raw data in executable flash or in some external eeprom doesn't really change the workflow much.