News for hackers. Stuff that matters.
Re:The case for an iceberg-native database by adzm on Wednesday October 08, 2025 @04:48AM (#45513721)
While not related to the topic exactly, the blur under the translucent header was so distracting I had trouble reading the article. Usually I can overlook stuff like this; I can't explain why it bothered me so much.
Re:The case for an iceberg-native database by bryanrasmussen on Wednesday October 08, 2025 @08:06AM (#45515226)
the problem really is that if you scroll you have enough variation between images and text it makes the translucent header function as a sort of blink effect, calling your attention away from what you're trying to read which is probably right up by where the header is blinking.
Re:The case for an iceberg-native database by mihau on Wednesday October 08, 2025 @05:24AM (#45513994)
Kinda off-topic but I love the quality of images used in this article. Even memes are HD. Quite rare as people tend to use whatever meme creator provides - super-pixelated, low-quality source image with text slapped on top.
Re:The case for an iceberg-native database by whobre on Wednesday October 08, 2025 @09:41AM (#45516090)
The main selling point of the open table formats is to decouple the data from query engines.
Re:The case for an iceberg-native database by rubenvanwyk on Thursday October 09, 2025 @07:44AM (#45526297)
Isn't that almost what we got with DuckDB + DuckLake?