2,630 karma · joined October 31, 2018
Half of these are caused by C problems not present in Rust like: null pointer errors, buffer overflows, integer overflows.
The rest are logic errors (e.g., parsing errors) or crypto vulnerabilities (e.g., side channel attacks). There's nothing about Rust that magically prevents these errors. These vulnerabilities are discovered through testing and more importantly real world usage. Rustls has not been used nearly as much as or as long as openssl, so critical bugs could be in Rustls. You could encode some logic in the type system, but the types are still code that have to be tested. It's not a formal proof. It could still be wrong.
It depends on your threat model and your risk tolerance whether you want to depend on relatively unvetted code.
Think of all the interesting things you could do with a worldwide bluetooth mesh network, and they choose to use it for surveillance. Lol.
Ideally you want a formally verified SPARK or CompCert C implementation of TLS, but those are not open sores compilers so they won't fly.
If you're worried about the code changing, you can run e.g. ETH nodes yourself, download the DEX frontends, and run the DEX locally.
Their solar panels on the roof caught on fire. Presumably there was no actual disruption in service computing-wise.
> Google fire
2006, still a young company at that point. Also this was way before GCP where they were responsible for other people's services.
> AWS fire
Data center caught on fire while it was under construction. Drunk construction workers messed up, not AWS. Presumably no computers were even inside yet. This is completely different from OVH completely burning down while all their customers' data went up in flames.
If these are the best examples of Big Cloud messing up, this is quite the endorsement.
It's funny how the OVH CEO tells everyone to go activate their DRPs while the company didn't have enough foresight to install fire suppression systems.
Personally I'll continue to use these third world cloud providers. But I like to live on the edge.
Rust programmers tend to do all kinds of little hacks here and there to make the borrow checker happy. It can add up. The borrow checker is perfectly happy when you copy everything.
Rust is becoming one giant antipattern.
(I'm sure highly experienced Rust programmers can get it to work, but there are probably less than 1000 people on this planet that can write good Rust that outperforms C++ so does it really count.)
Meanwhile C and C++ can easily adopt any async system call style because it made no assumptions in the standards about how that would be done.
Rust also didn't solve the colored functions problem. Most people think that's an impossible problem to solve without a VM/runtime (like Java Loom), but people also thought garbage collection was impossible in a systems language until Rust solved it. It could have been a great opportunity for them.
Ten year old FUD. Most distros are on systemd now. Whatever you want to say about systemd, it's definitely not fragmentation. Also there's the freedesktop project and dbus which creates a standard API for desktop applications. All Linux distros use glibc and GNU coreutils. Where's the fragmentation?
Linux desktop applications are all very fragmented and broken (GNOME, KDE, 100 different tiling window managers, 100 different music players that all suck), but that's not Linux, that's userspace.
> Torvalds has a bad opinion on ZFS
Doesn't matter. ZFS on Linux still works. Also ZFS is not immune to criticism. BTRFS is getting better and is more than adequate for everyone who is not running a CDN. Also ZFS isn't exactly usable on all BSDs, just FreeBSD (nor did FreeBSD come up with ZFS in the first place (why not migrate everything to Solaris then?)).
> Linux is being heavily influenced by corporate interests
Good. Problem? The computer is a tool not a political bumper sticker. I'm happy to use something for free that developers are paid to improve and that I still have complete control over. Linux [Android] is the most widely deployed OS in the world. It's constantly improving and lots of eyes are on the code. There just aren't enough skilled volunteers to maintain a giant codebase as critical as an OS.
https://madaidans-insecurities.github.io/openbsd.html
When BSD is used by corporations, they fork it and make their improvements proprietary.
> Time to migrate everything to BSD
Then almost everything I do with my computer would be impossible except for dicking around in a web browser. How do I run containers, modern hardware, or CUDA? Hard mode: No Linux emulation.
At best you end up with a little hangout for you and a handful of people you already know, possibly people who were already on the mainstream for-profit social networks with you but you insisted they use this other one to contact you. At that point you have an overengineered group chat application.
Also if you believe just buying the S&P 500 is going to be most profitable, then why not buy deep ITM calls on SPY. You'd at least 2x your exposure at the same cost.
Now it's basically dead. Was it the deplatforming? Did the world just move on? Nobody knows.
If this scenario played out in another business, like a restaurant, then nobody could really stop them from operating. Even if the food supply companies stopped delivering, there is a decentralized network of small farmers and transportation companies that could pick up the slack. No such counterpart exists with internet companies. You're either part of the grid or you're out. Come to think of it, that could explain a lot.