> And, the fact it supports KOSync is just amazing.
I was excited by this and went through the effort to set up syncing, get the same books and KOSync support on my Kindle and phone as well, and... I don't ever use it because I just read on the X4 Pro all the time and haven't touched my Kindle in months.
I wonder how accurate the locations are in this LiDAR dataset and/or the Queens Giant Wikipedia article. The Alley Pond Park candidate looks suspiciously close to the the Queens Giant, so I wonder if it's actually picking the same tree?
The (typically government) agencies that pay for these scans create specifications for the data to meet. This is not hard to find. IIRC the accuracy is generally less than 0.1m (though the precision is usually 0.01 meters or feet).
I wonder if they are actually going to start enforcing this. I’ve been receiving emails that my account is at ~200% capacity for a little over 13 years (just went through my email to double check). I’ve logged into my account a handful of times over the years, but certainly not every 12 months.
I’m not sure if you were getting at this by mentioning the ABI specifically, but for Go the “faster size class computation” isn’t purely about the computation itself.
There are lots of cases in the allocator that are conditional on size class (tiny allocations have a bunch of special cases, as do large allocations). Pointer/no-pointer allocations also have lots of special cases.
In the specialized functions, these conditionals become constant and lots of code falls away. We don’t pay the cost for those comparisons anymore, plus since code size is smaller it is now more reasonable to inline callees a bit more aggressively.
Michael also put a lot of time into finding the right balance of code size. At first you want to specialize everything, but that is going to increase code size a lot and thus hurt icache performance. If I recall correctly, our initial version had a code size increase ~4x higher than what we ended up with in 1.27. The final version specializes far fewer size classes yet actually had better performance than the original version.
Regarding the ABI, we definitely see an improvement with static calls vs computing the size class in the runtime. If I recall correctly, it’s the indirect call to the specialized function through a lookup table that stalls the dynamic case.
> I’m not sure if you were getting at this by mentioning the ABI specifically
Fil-C dynamically links its runtime, and it's a goal to support having different runtime versions link against code compiled by different versions of the compiler, within the same ABI epoch.
Hence, the current thing where the compiler computes the allocator bucket means that the shape of allocator buckets in the thread object is part of the ABI.
> In the specialized functions, these conditionals become constant and lots of code falls away
I see. That's a key difference from Fil-C.
Fil-C's GC only specializes on size in the sense that you end up in a different allocator bucket.
> we definitely see an improvement with static calls vs computing the size class in the runtime
> “That moment when you realize that a tool simply fixes all the UI issues that you had and that you have been developing for the last 20 years was not exactly great." He had two options: despair or learn from the competition. He chose to learn from it.
"He discussed the workflow for splitting a Git commit, which involves seven separate commands with Git's current UI. Most users do not know how to do this, he said. The goal is to add several ""opinionated subcommands"" that make more modern styles of working with merge requests, such as stacked branches, much easier."
I was excited by this and went through the effort to set up syncing, get the same books and KOSync support on my Kindle and phone as well, and... I don't ever use it because I just read on the X4 Pro all the time and haven't touched my Kindle in months.
reply