With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js. Learn more →
Jxl.js Alternatives
Similar projects and alternatives to jxl.js
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
libwebp
Mirror only. Please do not send pull requests. See https://chromium.googlesource.com/webm/libwebp/+/HEAD/CONTRIBUTING.md.
-
node-unblocker
Web proxy for evading internet censorship, and general-purpose Node.js library for proxying and rewriting remote webpages
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
jxl.js reviews and mentions
-
JPEG XL and the Pareto Front
> It's so frustrating how the chromium team is ending up as a gatekeeper of the Internet by pick and choosing what gets developed or not.
https://github.com/niutech/jxl.js is based on Chromium tech (Squoosh from GoogleChromeLabs) and provides an opportunity to use JXL with no practical way for Chromium folks to intervene.
Even if that's a suboptimal solution, JXL's benefits supposedly should outweight the cost of integrating that, and yet I haven't seen actual JXL users running to that in droves.
So JXL might not be a good support for your theory: where people could do they still don't. Maybe the format isn't actually that important, it's just a popular meme to rehash.
-
Still no love for JPEG XL: Browser maker love-in snubs next-gen image format
https://github.com/niutech/jxl.js a javascript polyfill taken from the main page https://jpegxl.info/
There are other decoders [0] written in a "safe language" (rust) listed as well. So no there are many "safe" implementations
[0] https://github.com/tirr-c/jxl-oxide
- CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
-
Apple Safari 17 beta release notes: JPEG XL support added
> If you care about JXL, and only want to support JXL, and you put a JXL in your picture tag, then the browser still won't render it, even if you use a picture tag.
Is this true if you provide a polyfill? Have you tried it and it failed? (Serious question.)
https://github.com/niutech/jxl.js
-
FSF Slams Google over Dropping JPEG-XL in Chrome
All of the people here who are so passionate about JPEG-XL will be happy to learn that there's nothing preventing them from using it on their sites right now:
https://github.com/niutech/jxl.js
If you want Chrome to ship with JPEG-XL support, use it. At some point, browser makers will decide it's worth the cost to them and all users to add it.
-
Nvenc vs. QSV: Who Has the Best Hardware AV1 Encoder?
> Please be aware that some images may not load on this page unless your browser supports JPEG-XL
The site could provide a WebAssembly decoder to make the JPEG-XL images work for everyone.
For example, here's a WebAssembly decoder: https://github.com/niutech/jxl.js
Demo: https://niutech.github.io/jxl.js/
-
Question: Is there a list anywhere of which browsers support JPG-XL by default?
at this point, I'd consider just using a polyfill library to decode jpegxl data client-side, like JXL https://github.com/niutech/jxl.js
-
Efficient and performance-portable vector software
:) There are some wasm vs native benchmarks in the context of JPEG XL (for example https://github.com/niutech/jxl.js#benchmark)
-
Adding JPEG XL & QOI Support to my Website OS
For adding JPEG XL support I went with jxl.js which I modified for my use case. After looking through the main file, which is also called jxl.js, I decided I only needed 2 relevant code blocks. The one to decode the image and the one to turn the ImageData into something I could display in my existing codebase (which I already partially had implemented for another use case).
-
JXL.js decoder now features multithreading and SIMD
It's easy - you'll get ReferenceError: SharedArrayBuffer is not defined when the COOP and COEP headers are not set. Multithreading is enabled by default if you use the scripts from multithread folder. If only SIMD is supported, it is being used. Oh, and progressive decoding is also enabled by default.
-
A note from our sponsor - SurveyJS
surveyjs.io | 23 Apr 2024
Stats
niutech/jxl.js is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of jxl.js is JavaScript.
Sponsored