bfrog

Care about security in what way? The radio and protocols are all written in C still with the endless CVEs that bring about aren’t they?

Is TrustZone really all that useful? I haven't had a need for anything like it myself!

esp-c6 module parts are like $2-3 and already have an fcc cert, low power, and support all the same protocols I believe. Are nrf54 modules really that cheap? Can I program them natively with Rust yet?

I kind of wonder why Nordic bothered sticking with arm cores at all. The competition isnt

C doing C things

They don’t return anything, what are you talking about?

Subscribers are never happy, it’s very expensive and fails to cover many things. But what choice is there? Don’t get coverage and hope you don’t get sick? Often times you don’t even get a choice… the company decides what plan and such you can get. So no, there’s no incentive to do the right thing other than the potential loss of corporate customers (which don’t have the same incentive as individuals) or potential lawsuits.

LLMs are overrated trash feeding themselves garbage and producing garbage in return. AI is in a bubble, when reality comes back the scales will of course rebalance and LLMs will be a tool to improve human productivity but not replace them as some people might think. Then again I could be wrong, most people don't actually know how to create products for other humans and that's the real goal... not simply coding to code. Let me know when LLMs can produce products.

Insurance is a terrible name for what we have, its not insurance, its blackmail.

You dying and zero being paid out by the insurance company is the best profit margin they can ask for, that's the entire goal of an insurance company at this point.

Exactly this, hard to grok why people think somehow the fab is the boat anchor around Intel's neck. No, it was the golden goose that kept Intel ahead until it didn't.

BK failed to understand the moat Intel had was the Fab. The moat is now gone and so is the value.

I’m interested to see how things progress! rustc itself is still reliant on llvm and ld, but there’s some intriguing alternatives coming in cranelift and wild both written in rust themselves, and I think done in a way that would allow incremental compilation and linking to be done in a way that better suits rust.

Sounds like a dystopian hell to me. Best of luck contacting the robo help support for the robo taxi trying to explain your unique human scenario that it’s never seen I guess.

You bled all over the car because you were shot and then crawled out looking for help because the AI had no clue wtf to do? Ok good luck sir, you owe us 10 days of metered fairs. No there’s no human to get help from.

Yeah the robotaxi is a pipe dream grift. Humans are gross and nasty, I think some of these people need to do a ride along in a cab sometime in the winter in a busy poorly marked city on a Friday or Saturday night. Pray tell how the robot kicks passengers out or navigates the inevitable unexpected weather/human activity.

I don’t think the intent was directly to embarrass anyone, but the standoffs and loosely stacked pcbs really did seem unfortunate. It was dropped, Mark repaired it and it was quite likely just as good as new minus the enclosure damage.

Audio equipment definitely has this issue of extreme pricing for questionable things. In all likelihood the amp on a chip is the best designed amp for the money. Sure discrete stuff might have a better noise floor and reduced noise. I’d argue few people could tell the difference.

I watched this episode, hilariously terrible construction of what I’m sure was a thoughtfully designed amp.

The thing had pcbs stacked using plastic m2.5-like standoffs that had snapped. Apparently the product designer claimed Mark couldn’t fix it. Mend it Mark can fix anything that is fixable, truly a master repairman.

Which is why Pat was on the right track imho with foundry. It’s too bad he won’t have the tenure needed to see the outcome of 18a, good or bad.

Even Arm is tenuous at best with risc-v right on its heels.

They can’t compete with byd. Doubtful any auto company reasonably can.

Isn’t io_uring eating away at these bypasses like spdk and dpdk ?

It wasn’t like this as little as 10 years ago

C++ is somehow aesthetically dis pleasing, thus mixin idea doesn’t change the needle for me.

McAfee like investing

Copilot feels like I’m getting a personal health examination I didn’t ask for, need, or want.

Don’t need to be remote to do a whole lot of nothing. Being a bench warmer in the office is absolutely possible

Aren’t we all skeptical? What’s the real value exactly.

Long term I wonder how healthy x86 is as a whole. It seems like only a matter of time before someone puts out risc-v aws/gcp/azure instances that compete, or puts out a laptop part on a chromebook that kills it.

The only thing holding back the wave is windows... and microsoft themselves seem somewhat open to the idea of not using x86 anymore.

If only, somehow any failures will still be placed on a different plate. This is the winner of a dying/dead empire.

Google sure seems to think it’s solved and prevented many exploits. Do you have similar credentials to back your statement suggesting Rust doesn’t solve a category of security issues? The same kind this hardware extension is looking to solve?

The entire premise seems to be that if you are stuck using not Rust in some way then CHERI helps. How is my comment not correct then? This is a bandaid to help poorly written code handle memory faults with hardware exceptions. MMU and MPUs do this as well without the cost of fat pointers which is non negligible. Rust does this with the compiler before the firmware even runs.

Is it neat? Sure. Is it practical and useful? I’m skeptical.

This seems to be a common theme with many c++ developers honestly.

Or… you could use a memory safe language and not have to try and patch up things in hardware for buggy software.

If we didn’t have Rust this would be super cool. With Rust this seems like slapping flexseal on the leaky boat.

Bikes can last a lifetime, this is a case in point. Imagine how little cost in carbon and energy has gone into this item after its life of use.

Now imagine the same with an automobile. It was a terrible mistake to build a car centric world where we sit in metal boxes to go to massive parking lots with enormous stores to fill our cars with useless crap that lasts a moment in time.

This is generics.

Calling x.some_func() in rust means there is either a type specific function or an impl trait. If more than one option is there rust requires more explicitly calling the types function with x as a parameter.

E.g.

Something::some_func(x)

I’ve never read rust code where I’m entirely guessing which overloaded function is being called. C++ has an entire set of overload resolution rules around this! https://en.cppreference.com/w/cpp/language/overload_resoluti...