Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mort96
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
39 ms
·
811.
▲
by
mort96
9mo ago
From the man page: --ultra: unlocks high compression levels 20+ (maximum 22), using a lot more memory. Regardless, this reproduces with random other files and with '-9' as the compression level. I made a mastodon post abo
812.
▲
by
mort96
9mo ago
It seems like zstd is somehow compressing really badly when many zstd processes are run in parallel, but works as expected when run sequentially: https://news.ycombinator.com/item?id=46723158 Regardless, this does not make
813.
▲
by
mort96
9mo ago
Okay now this is weird. I can reproduce it just fine ... but only when compressing all PDFs simultaneously. To utilize all cores, I ran: $ for x in *.pdf; do zstd <"$x" >"$x.zst" --ultra -22 & done; wait
814.
▲
by
mort96
9mo ago
No, it can't. No LLM can purchase the equipment and chemicals and machinery you need to reproduce experiments, nor should you want it.
815.
▲
by
mort96
9mo ago
I just did some interactive shell loops and globs to compress everything and output CSV which I processed into an ASCII table, so I don't exactly have a pipeline I can modify and re-run the tests with compression speeds added ... but I
816.
▲
by
mort96
9mo ago
I'm not sold on the idea of adding compression to PDF at all, I'm not convinced that the space savings are worth breaking compatibility with older readers. Especially when you consider that you can just compress it in transit with
817.
▲
by
mort96
9mo ago
Isn't zstd primarily designed to provide decent compression ratios at amazing speeds? The reason it's exciting is mainly that you can add compression to places where it didn't necessarily make sense before because it's a
818.
▲
by
mort96
9mo ago
EDIT: Something weird is going on here. When compressing zstd in parallel it produces the garbage results seen here, but when compressing on a single core, it produces result competitive with Brotli (37M). See: https://news.ycomb
819.
▲
by
mort96
9mo ago
I can't give you a precise number, but it's somewhere above $0 and below $∞
820.
▲
by
mort96
9mo ago
EDIT: Something weird is going on here. When compressing zstd in parallel it produces the garbage results seen here, but when compressing on a single core, it produces result competitive with Brotli (37M). See: https://news.ycomb
821.
▲
by
mort96
9mo ago
Neither $X nor $Y are going to be hard dollar values. If I semi-arbitrarily pick some $X and some $Y, put in $X+$Y as my max bid, and lost the item due to $0.01, I would be annoyed not due to some irrationality but because $X and $Y were
822.
▲
by
mort96
9mo ago
No, I am willing to pay $0.01 more but not infinity more, there's a difference
823.
▲
by
mort96
9mo ago
Before I have made that initial decision, and before I have invested resources into evaluating what I think the value of a product is, I do not have a price in mind. Deciding on a price I think is fair for a product takes effort. The more
824.
▲
by
mort96
9mo ago
> are you > - agreeing there must be some threshold such that if the price is $X then you will buy(/bid on) the item, but if the price is $X + $0.01 then you won't; No, I'm not. If I will buy an item for price $X, I wil
825.
▲
by
mort96
9mo ago
> But if you set a max price at $5000 and would be happy to get the item at $5000.02 (for some reason other than satisfaction from sniping), then you set your max price wrong, or at least differently from how economists expect you to set
826.
▲
by
mort96
9mo ago
Regarding the last part: it's simple, $1.01 is less than $100 This process doesn't work endlessly. You can't just add $.01 a billion times and I'd still pay it. But it works once or twice. Shops set prices like $499.99 d
827.
▲
by
mort96
9mo ago
The gap between total indifference and wanting something bad enough to bid on it is always going to be more than $.01.
828.
▲
by
mort96
9mo ago
It can be extended forever in theory, and sure, that is an interesting philosophical discussion, but it isn't in practice. We're discussing sniping. That means you make the choice once : do I send in a last-second bid that's
829.
▲
by
mort96
9mo ago
The logic of "you shouldn't ever need to snipe, just bid your max price" only works if we assume that the max price is a red line though. If I "value something" at $5000 (as in I want to buy it at $5000), and I bi
830.
▲
by
mort96
9mo ago
I don't see why I would buy something if I'm indifferent to whether I buy the thing.
831.
▲
by
mort96
10mo ago
I don't understand this line of reasoning. I don't do auctions, but if I did, it would be because I want that item. When I want something, I never have an absolute hard price ceiling; if I'm willing to pay $10000, I'm wi
832.
▲
by
mort96
10mo ago
HDR support is an anti-feature. Nobody want a part of a website to suddenly be 10x as bright as pure white.
833.
▲
by
mort96
10mo ago
What if I have a string and not a byte string?
834.
▲
by
mort96
10mo ago
It's so annoying how so many languages lack a basic "ASCII lowercase" and "ASCII uppercase" function. All the Unicode logic is not only unnecessary, but actively unwanted, when you e.g want to change the case of a h
835.
▲
by
mort96
10mo ago
Can you describe some of the errors you have found this way?
836.
▲
by
mort96
10mo ago
I work on games sometimes, where the goal is: "run as fast as possible on everyone's computer, whether it's a 15 year old netbook with an Intel Atom or a freshly built beast of a gaming desktop". As a result, the best ap
837.
▲
by
mort96
10mo ago
This is cool! Makes me want to implement peephole optimizations in some of my own bytecode interpreters. Though I'm wondering about the const_binary optimization: > This optimisation refers to a binary instruction > and
838.
▲
by
mort96
10mo ago
Regarding (b), I would never rely on auto vectorization because I have no insight into it. The only way to check if my code is written such that auto-vectorization can do its thing is to compile my program with every combination of compiler
839.
▲
by
mort96
10mo ago
It goes through the "reject all tracking" flow. Other solutions automate clicking "accept all tracking" (since that's usually simpler), or just hide the pop-ups.
840.
▲
by
mort96
10mo ago
Yeah, as I said it's a solvable problem. It just needs solutions to be implemented
More ›