Both perspectives need to be tested against each other, carefully.
732 karma · joined August 5, 2024
Both perspectives need to be tested against each other, carefully.
I think just having less in the kernel and moving bits out (like Mach) into isolated domains is probably better than reinventing the universe for some purity argument.
Edit: I don't even know Rust but I wrote a prototype:
fn main() {
const LOL: *mut u64 = 1 as *mut u64;
unsafe {
std::ptr::write(LOL, 0);
}
}
Edit 2: fuck that's ugly.Edit: just in case anyone took this too seriously, it was facetious.
That's how this ends.
And I'm fine with that. May the best solution win.
I avoid office type packages now when I can.
Numerous minor updates have screwed up things for me, particularly with some applications I rely on. I will usually lag 2-3 patches behind and wait for other people to suffer first and confirm what I use is stable. I am still on Sonoma / 14.5 at the moment.
Incidentally I actually have a Mac Pro here which is running Monterey which hasn't been patched for about 9 months. The universe has not and will not be imploding any time soon.
Everyone forgets the "availability" bit of security.
Moved to Apple Silicon in 2021 after my Dell Precision cooked itself (and my lunch!) to death in my bag on a train. No issues since.
It’s usually less interesting on the EE side where you’ll get something that looks like an expensive opamp but turns out to be an LM358. It might even partially work in circuit!
I'll add that my cousin was stabbed 6 times by a coke head flat mate who had a psychotic episode.
And I haven't started on the slavery side of the production side of the supply chain.
So we have extortion, illegal drug dealing and illegal guns in one fine evening.
ChatControl is not the solution however. Reporting it to the police didn't do a damn thing either though so I don't know!
flights |>
filter(
carrier == "UA",
dest %in% c("IAH", "HOU"),
sched_dep_time > 0900,
sched_arr_time < 2000
) |>
group_by(flight) |>
summarize(
delay = mean(arr_delay, na.rm = TRUE),
cancelled = sum(is.na(arr_delay)),
n = n()
) |>
filter(n > 10)
If you haven't used R, it has some serious data manipulation legs built into it.This is a real problem because any zealot of this level serves only to discredit the product by association.
I have no opinion on Rust other than I don't have the time to learn it at the moment and it doesn't look like it solves any problems in the domain of things I care about at the moment. I have no opinion past that. I am interested in technical discussion on it in case it overlaps a problem domain I am interested in, which is why I am on this thread :)
In fact I did this a couple of years back on a project I was working on maintaining in win32. It had a complicated memory management scheme for a GUI process that kept screwing up. Turned out it couldn't ever use more than 2MB of RAM so I just allocated 10MB up front at the start of the process and wrote a simple incrementing pointing counter in that allocated block and free'd it at the end like a short life pool. Solved all the issues. Machines it's running on all have at least 16GB of RAM so it's not exactly breaking the bank!
What I need is people who can write very complex rule and constraint engines, mathematicians and statisticians to deliver some business value, not crud monkeys.
Rust is not the answer for most problems. If you like it or not!