lonjil

11 ms·

121.
by lonjil 3y ago
Chrome and Chromium are the same dev team. Open source doesn't mean that they'll accept any pull request. It was implemented in Chromium, as an experimental feature, and then removed.
122.
by lonjil 3y ago
I don't see any comments from any Chrome developer since the Safari news, so the headline here on HN doesn't make a whole lot of sense.
123.
by lonjil 3y ago
> Why not just buy a Linux laptop and have everything work out of the box? Why are Linux enthusiasts putting so much effort into supporting hardware from companies that - at best - ignore Linux? Almost all laptops sold with Linux pre-ins
124.
by lonjil 3y ago
> They're suited for delivery because they're based on video codecs (WebP on VP8, AVIF on AV1) for which consumer hardware typically has hardware decoding support, But no one is doing HW decode for web images. (other than maybe
125.
by lonjil 3y ago
> Actually, Google employs 2 of the 3 main authors of the JPEG XL spec, and the main contributors to libjxl. > There people in this thread arguing they have no idea what they are doing and have no expertise, while they simultaneously
126.
by lonjil 3y ago
No it wasn't. WASM implementations are simply slower than native support. No browser uses HW accelerated decode for AVIF images or JXL. I think Safari might use HW for JPEG, but that's it across all browsers.
127.
by lonjil 3y ago
The work wasn't done by anyone on the Chrome team. Someone at Google Research Zurich (I don't recall who) wrote the patches and submitted them. Actually, I think that they've even kept the patches up to date with newer Chrome
128.
by lonjil 3y ago
I think they want better compression. JXL has excellent lossless compression.
129.
by lonjil 3y ago
> Their justification was more that adding it would be committing a lot of hardware Which is completely nonsensical. Hardware support is meaningless for web images.
130.
by lonjil 4y ago
The regular stable Alpine releases sound like exactly what you're asking for? Packages in the main repo get 2 years of support.
131.
by lonjil 4y ago
Hm, I don't see any fetishes in this blog post.
132.
by lonjil 4y ago
> But also nobody will read your articles if the site looks like this. But wait, Xe's articles frequently make it to the HN frontpage. Surely someone must be reading them?
133.
by lonjil 4y ago
It's actually rather simple. You read one bit of text, and then you read the next. It's a dialogue, if you've ever read a book the format should be familiar.
134.
by lonjil 4y ago
SQLite is what they switched to , and still use.
135.
by lonjil 4y ago
> So, when AV1 becomes more popular and starts really showing up in silicon (which Google is putting huge pressure on silicon vendors for), almost everyone will have a hardware AVIF decoder for free, should they choose to use it. If that
136.
by lonjil 4y ago
> In the article I linked, the creator of ANS asserts that Microsoft's patent covers the variant used in JXL. Microsoft is a member of ISO. They're obligated to notify ISO if they have any relevant patents to new standards. The
137.
by lonjil 4y ago
That patent is completely irrelevant to JXL. JXL doesn't do anything described in the patent. And in any case, I think the person you responded to is referring to non-web actors like Abode, who seem to like JXL.
138.
by lonjil 4y ago
Hah, they definitely didn't apply this criteria when they enabled AVIF by default in Chrome before the AVIF spec was even complete.
139.
by lonjil 4y ago
> Was there any momentum getting JPEG XL approved in browsers (not behind a flag) before Google decided not to support it? Not sure if it counts as momentum, but engineers representing Facebook, Intel/VESA, Shopify, Adobe, and more
140.
by lonjil 4y ago
He kicked out 100% of people who actually contribute code, so I'm not sure what the heck you're talking about. To the contrary, the sole person left in the project is the one who was all political about it.
141.
by lonjil 4y ago
All good, apologies for not being clear.
142.
by lonjil 4y ago
Yes, and the person I replied to explained how to prevent that, but seemed unsure about auto-update capabilities of the launcher itself, so I provided that information.
143.
by lonjil 4y ago
Should be noted that autoupdate was only ever available on macOS.
144.
by lonjil 4y ago
No, the person who owns the GitHub organization kicked out all other developers with zero notice and started talking about how he's purging the "leftoids" from the project and that all other contributors were "promoting
145.
by lonjil 4y ago
> SQLite cannot accept random contributions. It's on A350 flight systems, where failure is not an option. The maintainers are able to uphold this quality, but random contributors are not. Do you think Airbus updates their copy of SQ
146.
by lonjil 4y ago
> but arguably a lot of stuff in pico-playground or pico-extras is not finished Arguably? They straight up say that the things in those repos are unfinished or otherwise not good enough for the SDK.
147.
by lonjil 4y ago
> but I have a feeling this $7 cost is the usual fantasy they advertise, then sell them for twice the price everywhere. The current pico is sold at the stated price + taxes here in Sweden, so I don't see why the W wouldn't also
148.
by lonjil 4y ago
> All the issues with availability have turned me off on them. The Pico in particular has never had availability issues. Actually, it seems to have much better availability than most competing products.
149.
by lonjil 5y ago
> Yet, it appears the median and mean Lisp programmer is producing Yet Another (TM) test framework, anaphoric macro library, utility library, syntactic quirk, or half-baked binding library to scratch an itch. Our Lisp programming environ
150.
by lonjil 5y ago
Page size is not set when you compile. At runtime, you can ask the kernel what the page size is, and use that value where appropriate. Some poorly written software hardcodes the page size on a per target basis.

More ›