No that doesn’t keep windows from changing anything.

Just learn how to repair your bootloader how your distribution wants it done and you’ll be fine.

They are not irrelevant points and hopefully I can show why.

So I went fishing through the kernel rust directory and didn’t find any drivers. It’s late and I definitely missed a lot (I didn’t even go through the drivers branch, but should rust code be there? I thought it all lived in /rust…), but the r4l page lists the nvme driver, an implementation of existing functionality in rust that is in the words of its description page “not suitable for general use”. The r4l page also has the null block driver, which is not a strictly speaking useful thing for actually doing stuff with the computer but is a great way to do a bunch of goofy crap and its page on the r4l website explains why it’s being rewritten in rust.

I just want to pause here in the comment and say that the null block driver is actually a phenomenal thing to be rewriting in rust for so many reasons.

Then there’s the android binder driver which is not something I understand enough to comment on, but is a rewrite in rust. I also saw a puzzlefs driver on the r4l page. Puzzlefs is an experimental file system written in rust to begin with so it’s no surprise the Linux driver is rust.

Last the r4l page offers two gpu drivers, the apple one that asahi uses and the nvidia nova one which seems to be in the early stages of development.

As I said, I probably missed some drivers and other rust code that needs to use —since it’s our topic of discussion— the c dma bindings through a wrapper.

But if all six of those used the dma c bindings wrapper then that’s still far short of my agreement with you that the right way would be to write a bunch of good rust shit that uses the wrapper then say “hey, if we move this wrapper into dma directly it’ll save 10k lines of code because it’s a hundred lines and used in a hundred things”.

Instead it’s used by three rewrites (the point of r4l!), an experimental file system, a in development gpu driver and the asahi mac driver.

For a third time, I’m absolutely 100% sure there’s more rust drivers than that, but enough to make the argument that you’re taking a hundred lines out of a hundred places?

When I was younger I was involved in local government. I was idealistic and thought that having been accepted at the table, the correctness of my ideas would be evident and they would be accepted and implemented quickly. Of course I was very wrong and was surrounded by competing interests vying for limited resources so the force of my argumentation had almost no effect.

What was effective was constructing scenarios that made it almost impossible for people to act in ways other than what I wanted.

I chose a narrative analogous to the common rust person complaint of “political reasons” here on purpose because ultimately instead of appealing to an authority to settle the chicken or egg problem for them (which is somehow not political, despite the authority existing within some governing structure but whatever!) rust devs should be saying “who the fuck cares, I’m headed to market with a cartload of chickens and eggs, you gonna give me a stall to sell out of or am I gonna be clogging up the thouroughfares?”

You’re posting in the internet right now. I suggested that you tell people you are trying to get away from computers

I’m not at a computer with the source on it, so if you get to it before me, how many rust drivers are there? How many that would use the rust dma wrapper?

I ask because last year there were relatively few.

People writing in c don’t have to use a wrapper because there’s no need to wrap c code for use by other c code.

More broadly there are times when duplicated c code has been condensed into a library or something and added to the kernel.

Okay but you’re not lifting the bike by its chainstay and swinging it around like a claymore or something, you lift at the center of mass, which in an e-bike is at the battery or damn close to it. It’s why they’re all in the triangle or under the rear rack and in the latter case manufacturers get away with it because you put the bike over your shoulder and use your hand on the bars to stabilize it thereby reducing the impact the battery weight makes on the bikes portageability through the use of the same lever whose fulcrum is your shoulder.

A lot of what you’re saying seems to me to be dancing around the point of “I want an incredibly light, fast e-bike, not a 50lb grocery getter”, and I truly understand that desire. But the reality of the e-bike buying public is that people want those 50lb grocery getters.

It’s the same as the car market. I want a manual everything, decently high displacement inline four with a manual transmission, manual 4wd, crawler gear and enough ground clearance that dirt roads aren’t an issue. Everyone else wants maximum fuel economy and lots of features so all the cars accommodate that set of desires instead of mine.

How much does torque come into play when you’re carrying your bike upstairs?

So you carry the groceries upstairs at the same time as your bike?

Wait so would you leave your groceries outside while you carried in your bike?

I have. It sucks but it’s possible and because I live in a mountainous area I avoid that problem by using less assist so everything lasts longer.

The broader point I was trying to make is that If you’re trying to allocate the limited raw materials to the types of transport that benefit people the most then pushing e-bikes to lead acid makes a lot of sense. Yeah, the bikes could benefit from a more power dense battery, but they have backup pedals and ultimately their rider is the majority of the loaded bikes weight.

Electric cars and trucks weigh at least ten times what a person does and are generally used for longer distances than e-bikes so it makes more sense to use very energy dense batteries in them.

Again, I’m speaking from a position that recognizes the proliferation of electric vehicles in China and recognizes that the raw materials used to make lithium batteries are finite and in high demand, not from the position of trying to optimize the e-bike.

I meant the ~300 mile ranges common in electric cars. That’s a long trip. Plus if the car rolls to a stop by the side of the road you just gotta have it towed or charge it up in the field somehow, electric bikes have pedals.

It sucks to pedal a heavy ass ebike but you can do it in a pinch to get where you need to go.

If you’re in america almost sixty percent of phones are ios.

If you’re choosing an encrypted chat and sixty percent of people are already using it then that’s the one you choose. The hardest thing is compliance and you’re almost two thirds of the way there if you just pay a hundred bucks (or scrounge up an old mac) and run the bridge app. Then you use signal for everything else.

I think we’re looking at this from fundamentally different perspectives. I’m not worried about a universal solution because I know I’m not getting to 100% compliance with any solution so I suggested the one that immediately fixes the majority of the problem. Having had to convince people to exchange pgp keys twenty five years ago, I’d pay a hundred bucks to not have to deal with that for two thirds of the people I know.

Think about it this way: if you were starting from scratch would you rather have to convince all your contacts to move their chats with you to signal or matrix or whatever or would you rather have to convince four out of ten to do that?

Obviously you’d pick the easier thing because no matter how committed you may be to not using proprietary software or big corporate apps or fragmented ecosystems you actually have to accomplish the goal of chatting with people using encryption and all the process compliance and wheedling and convincing and tech support for family members is time you could be spending talking about gardening, sharing baby pictures, plotting to overthrow the government or whatever you would normally be doing.

People will dislike this:

The most basic one with little barrier to entry is imessage. Theres a good chance your friends and family already have it and with a few setting changes (no sms fallback, set icloud recovery key, probably some stuff I forgot) you’re damn near at parity with signal.

All without dad having to download a new app onto his phone and make a new identity!

Of course you’ll need signal or something for people who don’t use it.

I use that combination and it’s excellent. If you can be on imessage with someone you’re good and everything works, if not you do signal.

There will be people you gotta use sms with. They just won’t be able or willing to do something new. Sometimes there’s an equipment problem, their super old provider version of android can’t get an app you both agree on. Sometimes they’re using a Nokia.

Interacting with sms often may help keep you on your toes about it. I know I’m more careful over text now.

That combination, imessage and signal, also has a benefit of reducing the chances that you’ll broadcast an awareness of and desire for privacy and security to the whole world all the time.

In the us, there’s a 50% chance you just look like a normal person and that’s nothing to sneeze at.

Make sure it meets your needs of course