HNHacker News
TopNewBestAskShowJobs

lonjil

675 karma · joined May 2, 2017

submissionscomments
lonjil··on Chrome still hasn't changed its opinion about dropping JPEG XL support
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.
lonjil··on Chrome still hasn't changed its opinion about dropping JPEG XL support
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.
lonjil··on OpenGL 3.1 on Asahi Linux
> 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-installed or with support advertized only work well with Linux due to volunteer work similar to what is being done with Apple's stuff right now. Almost everything is proprietary with close to zero upstream support, you just don't notice it because the work has already been done.

lonjil··on macOS 14 will support JPEG XL
> 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 Apple with JPEG? I've seen conflicting reports). AVIF images that aren't actually videos are always software decoded.

lonjil··on macOS 14 will support JPEG XL
> 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 employ the spec authors to work on it and are one of the two primary contributors to the reference library.

Google is not a monolith. The JXL people are at Google Research Zurich, while the people who decided to not include JXL in Chrome are members of the Chrome team. The Chrome team obviously does not employ the people over in Zurich, nor do they presumably control what they work on.

lonjil··on macOS 14 will support JPEG XL
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.
lonjil··on macOS 14 will support JPEG XL
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 releases so in theory it would be easy to re-introduce JXL into Chrome if there is a will to do it...
lonjil··on macOS 14 will support JPEG XL
I think they want better compression. JXL has excellent lossless compression.
lonjil··on macOS 14 will support JPEG XL
> 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.

lonjil··on In Praise of Alpine and APK
The regular stable Alpine releases sound like exactly what you're asking for? Packages in the main repo get 2 years of support.
lonjil··on 🥺: the best sudo replacement
Hm, I don't see any fetishes in this blog post.
lonjil··on 🥺: the best sudo replacement
> 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?

lonjil··on 🥺: the best sudo replacement
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.
lonjil··on Tailnet Lock
SQLite is what they switched to, and still use.
lonjil··on JPEG XL support has officially been removed from Chromium
> 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 happens, any decoding speed advantages that JXL has could be blown apart very quickly.

No one has any plans to decode AVIF still images in hardware. There are two problems. The subset of AV1 supported by hardware is much narrower than what is in practice used in AVIF images. Such images cannot be decoded by hardware. Second is that it actually doesn't get you any speed. Each image would need to be shuffled to the GPU, decoded, then sent back because browsers aren't really set up right for doing everything on the GPU. And any non-stateless HW decoder would be problematic, since every single image would need to reconfigure the decoder state, which is slow.

lonjil··on JPEG XL support has officially been removed from Chromium
> 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 subcommittee that JPEG is part of is even chaired by a Microsoft employee, so it's not like they'd be unaware.

Duda seems to think that Microsoft's patent simply covers rANS in general, but this seems dubious. Not only would it cover a lot more than JXL, it would have shitloads of prior art. The patent seems to describe an improvement of rANS, which isn't used in JXL.

Further still, Microsoft has straight up said that the patent is free to use for any open codec.

> That is completely irrelevant to Chrome, why would Google change their mind on that basis?

WebP adoption was slowed, and is to some extent widely hated, because it for many years had zero support outside the web. Not only is JXL seeing faster than adoption outside the web than WebP, it's seeing faster adoption than AVIF. That seems relevant to me. And of course, web companies literally can't adopt it until at least one browser starts supporting it. Shopify already serves JXL when you enable the flag. Facebook wants to use it. Yet Chrome's devs claim that there is basically no ecosystem interest. It's pretty ridiculous.

lonjil··on JPEG XL support has officially been removed from Chromium
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.

lonjil··on Chrome Responds "No" to JPEG XL
Hah, they definitely didn't apply this criteria when they enabled AVIF by default in Chrome before the AVIF spec was even complete.
lonjil··on The case for JPEG XL
> 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 have been asking for JXL to be enabled in Chrome without a flag for quite a while now.

lonjil··on PolyMC compromised by rogue developer having unabomber manifesto in steam bio
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.
lonjil··on PolyMC compromised by rogue developer having unabomber manifesto in steam bio
All good, apologies for not being clear.
lonjil··on PolyMC compromised by rogue developer having unabomber manifesto in steam bio
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.
lonjil··on PolyMC compromised by rogue developer having unabomber manifesto in steam bio
Should be noted that autoupdate was only ever available on macOS.
lonjil··on PolyMC compromised by rogue developer having unabomber manifesto in steam bio
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 radicalist leftist queer ideology".
lonjil··on LibSQL is an open source, open contribution fork of SQLite
> 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 SQLite to the newest version constantly? Bugs make it into SQLite every release, and no released version of SQLite is known to be DO-178B compliant. Seems a lot more likely that it is as Dr Hipp said a few years ago [1], that some customers have qualified specific versions of SQLite in specific configurations for use in applications that require DO-178B compliance. He says that he thinks that those companies certified it to D or C level, which is non-critical stuff, like failure leading to passenger discomfort, e.g. they may be using SQLite in the in flight infotainment system.

lonjil··on Raspberry Pi Pico W: your $6 IoT platform
> 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.

lonjil··on Raspberry Pi Pico W: your $6 IoT platform
> 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 be. And it seems unlike that Sweden would be special in that regard.

lonjil··on Raspberry Pi Pico W: your $6 IoT platform
> 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.

lonjil··on Why we need Lisp machines
> 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 environments are less than what they were in the 80s because everybody feels the current situation with SLIME and Emacs is good enough.

I don't think this is true. Not anywhere close. Most such examples are small, and probably only took a small number of hours to produce. While "superlative" stuff takes very many man hours to create. So just by seeing that there are many throwaway testing frameworks or whatever, you cannot tell where most of the work hours actually go. A half baked binding library takes 20 minutes to make, while a proper high quality rendering engine takes hundreds if not thousands of hours.

The Lisp population is thin on people making cool shit because the Lisp population in general is thin.

lonjil··on Asahi Linux alpha release
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.
← PreviousPage 5 of 7Next →