Which is worse?

• Entire driver written in a non memory safe language?
• The interface to the rest of the kernel is marked as unsafe and then the other X percent is safe from memory corruption?

Surely if X > 0 then this is still a net improvement?

This is inaccurate. OP , look it up for your airline. You’ll find all the information you need for your particular circumstances in a handy guide on their website, because they very much want you to know.

In general though:

Devices containing batteries with less than 100Wh capacity can go in checked luggage as long as they are completely turned off and can’t be accidentally turned on. There are limits to how many, for example a suitcase full of laptops will be frowned upon. Vapes and other similar devices (that is, things designed to get hot) need to go in carry-on.

Spare batteries (for eg power tools) need to go in carry-on and again, there are limits to how many.

Anything > 100Wh, like scooters or biiiiig powerbanks need special permission or are banned outright.

The cable between the two boards would be a maximum of 50cm. 3 of the signals are addresses for a multiplexer that would change at a maximum speed of 2ms per change. One of the other signals is a 20khz pwm signal. The final signal is a zc detector for mains so max Freq of 100/120hz.

None of this will be a problem over 50cm of cat5. If you were talking about millivolt or MHz signalling then you’d have to be a bit more careful.

Regarding wifi and power draw, you could always do batch uploading of data to another server at something like a 1:10 ratio, or upload only when there’s a change of more than 1 degree or similar.

There are some low power deep sleep esp32 boards out there that can do like 3-6 months on a couple of AA batteries. A lot of power draw comes from hanging around on wifi doing dhcp, so having fixed addresses can cut down power usage considerably.

Even without using the wifi side of things the esp32 boards come with lots of IO , plenty of drivers for various devices, and a reasonable in-house (i.e. not Arduino) development environment so I’d be leaning in that direction.

You could also look at Sharp’s memory LCD as opposed to normal LCD, as that’s extremely low power without the fiddlyness of e-ink screens.

If you read the phrasing carefully it’s quite clear that it will be doing things to the codebase, just “with oversight”.

How much oversight? Not sure, just some assurances that there will be oversight.

Vibe coding is essentially just a different phrase for that.

each driving for one hour per day with a computer consuming 840 watts

This entirely depends on what energy source we end up using in 2050.

IF , you assume that by 2050 home solar and batteries are a common item, and consumer electric vehicles are predominantly charged at home via those sources , then claims of emissions becoming a concern are moot. Seeing that home solar/batteries are becoming more common now, with 25 years to go, this is not a huge stretch of the imagination.

Each individual vehicle has daily energy requirements that can be sourced relatively easily by local renewables, unlike datacentres which have huge energy requirements requiring energy to be piped in from sources elsewhere.

Apart from that , the 0.8kWh/day usage of the computer hardware is entirely dwarfed by the (handwave guess) ~20kWh/day usage of the actual electric drive system, where trivial improvements in efficiency can compensate for the 0.8kWh/day usage of the computers. Hell, improvements in efficiency because of the adoption of autonomous driving instead of leadfoot humans at the wheel might end up making all this a net positive.

So, after sifting through all the other breathless articles from their website it seems that they’re going to :

• Use a LLM to attempt to sort out their documentation.
• Have a chatbot trained on the docs so you can ask it questions and possibly get coherent answers.
• Some sort of vague thing where the LLM provides guidance and suggestions on improvements to the codebase.

Lots of reassurance that they’re not going to let it do vibe coding but to be honest, they doth protest a little too much methinks.

I just got GPU temp monitoring working on my old dell laptop. “Heat management” for the GPU is pretty much just an extra chunk of steel tacked onto the heat pipe halfway between the CPU and its radiator, so GPU temps are always in the red.

I might as well just turn off monitoring and remain ignorant 🤷

It’s a 1/4 wave antenna with a groundplane. Physics dictates the size.

Compared to the PCB antenna in your average USB dongle, this would have at least two to three times the range, and likely more than that, because you can put it somewhere more optimal than just poking out the back of your device.

promises improved support for Wayland users by raising the minimum supported Wayland version to 1.20…

What a nice fluff piece for NVIDIA. How does ditching users below 1.20 and fixing an issue in their own UI improve support for Wayland exactly?

I do wonder if ditching < 1.20 support just so happens to fix the drop down issue they were having in their UI…

Some of the biggest jumps in house prices were when interest rates were less than 2 percent and you could get a million bucks from the bank just by asking to see the manager and giving them a firm handshake.

I don’t see that at all. Perhaps you are just projecting your own issues onto Lemmy at large. I think you need to have a good hard look at yourself and your internal biases and then come back and apologise to all of us.

they’re presented in the time and place you’re more likely to interact with them.

Normally about 4 to 6 days late so you’re “forced” to urgently like or comment after " missing out" on something in their life.

As is tradition.

I’m not a fan of people expressing views, even when awful, having machinations of the state used against them.

Welcome to the paradox of tolerance, enjoy your stay.

Search engines should have an off button for ai,

Techbros won’t let that happen, because they’re all terrified that consumers will just shut off all the AI being crammed into everything and all their money will evaporate.

If you’re just simulating the temperature there’s pretty much just three options:

• The thermostat will simply command the HVAC system to maximum cooling, just like with any temperature well above the setpoint.
• The thermostat will treat that value as a faulty sensor, report “error faulty sensor”, and not do much in particular.
• The thermostat will crash due to an overflow of some sort as its software was never tested with inputs like that.

Personally, I’d go with, “error faulty sensor” as the most likely outcome.

(Edit: you can stimulate the temperature by setting your house on fire. Better to just simulate it)

Lots of options here.

You can use a few strands of clean copper wire to clear the hole. Heat the solder with your soldering iron and poke the wire through.

Alternatively , you can heat the solder and then quickly apply a strong puff of air via a straw or ballpoint pen casing to the hole. That will blow the solder out the other side.

You can ALSO just place the new switch on the hole and heat the solder and push the pins through, as long as there are one or two clear holes to get the alignment right.

Somewhere, a grizzled old sub-editor’s eye is twitching over that title.

The gains compound a bit too, 20 percent less weight equals proportionally less battery capacity required to shift the now-lighter vehicle from point A to point B.

So then you can cut the size of the battery while maintaining the same range, and that’s where you start to get significant overall weight and cost savings.