“For the GCC and Clang compilers, our evaluation shows that BOLT speeds up their binaries by up to 20.4% on top of FDO and LTO, and up to 52.1% if the binaries are built without FDO and LTO.”
“Up to” though is always hard to evaluate.
1,267 karma · joined May 11, 2014
“For the GCC and Clang compilers, our evaluation shows that BOLT speeds up their binaries by up to 20.4% on top of FDO and LTO, and up to 52.1% if the binaries are built without FDO and LTO.”
“Up to” though is always hard to evaluate.
From the Bolt paper: “For the GCC and Clang compilers, our evaluation shows that BOLT speeds up their binaries by up to 20.4% on top of FDO and LTO, and up to 52.1% if the binaries are built without FDO and LTO.”
Not as nice as having an updated version in apt, but it’s a trivial amount of work for something I personally get so much value out of.
As someone who also consumes US news, this does not describe what I’ve seen.
If anything, Russia and Hamas are each less likely to spark each conflict (in the specific sense of invading Ukraine and 7 October, not the preconditions) knowing that the US is more likely to provide arms to Ukraine and Israel.
There are plenty of valid criticisms, but I felt the author’s post missed sufficient nuance.
The tweet has 10M installs, where each one makes a $1. 5M installs where each one produces $2 in revenue results in a smaller cut by Apple. 20M installs at $0.50 results in a larger cut.
Pixel 8: released in 2023, updates through 2030 Pixel 5: released in 2020, stopped getting updates in October 2023.
They were posted in a previous thread, and the way they were written made it unclear what was actually covered. Is Apple allegedly infringing on the idea of putting a blood oxygen sensor in a watch, a technical innovation in how to do so effectively, or something else entirely?
However, it’s implemented poorly, with frequent false positives. Furthermore, there’s a race condition between scanning the item, the machine saying “place it in the bag”, and the actual weight check. If I move too fast, the item is in my bag before the check starts, and I have to wait for assistance.
Maybe folks are frustrated that their theft is being caught, but high frustration seems to be the base case here.
"BUT YOU JUST WANT TO SELL YOUR COURSE!!! Ahahaha, you caught me! It’s true. I do have something to sell you. I run a community for small-time entrepreneurs who are satisfied with reliably attainable mediocre success. The YC folks feel sorry for our joy with mediocrity while they’re out there changing the world. And we reciprocate the emotion.
So yes, I am promoting something that goes against everything YC stands for. But if you think YC is not also selling you something, I have a bridge to sell you. But maybe I’m being a bit too harsh. Because what is it that YC is selling you exactly?
Me, I charge you a one-time payment of $245, and you get access to my community, which includes live workshops, recorded classes, a group chat, and a few other things. It’s very clear what I’m doing. I ask for some money in exchange for access, and those who give me the money get access. Even my 6 year old kid understands it."
Once again, a much broader issue than just YC! The author could have written the exact same article, just with VC instead of YC.
That said, not switching over to a memory safe language, in my opinion, is letting perfect be the enemy of the good. Folks will still be able to write footguns, but better language choices will prevent bugs in the all the non-crazy optimized parts.
None of those are suitable options for an image decoding library on the range of WebP supported platforms.
Android 12 was the first version to support Rust code, and came out in 2021 [0, link talks about the first year of integration].
On the iOS side (which also was affected by this), Swift 1.0 came out in ~2014.
As far as I can tell, Chrome doesn't yet support a memory safe language, but do have a bunch of other safety things built in (see MiraclePtr, sandboxing, etc). Since both WebP and Chrome are from Google, this would stop a possible transition.
WebP was announced in 2010, and had its first stable release in 2018 [1].
[0]: https://security.googleblog.com/2022/12/memory-safe-language...
The author mentions that many other systems need to patch as well. However, wow many of those billion Python docker pulls are rendering untrusted WebP images? Same for Node, etc. These should also be promptly patched, but they're not in the same ballpark here as iOS/Android/Chrome.
He’s certainly aware of memory safe programming.