wordpress-playground
libjxl
wordpress-playground | libjxl | |
---|---|---|
22 | 85 | |
1,527 | 2,236 | |
1.4% | 29.1% | |
9.7 | 9.8 | |
2 days ago | 2 days ago | |
JavaScript | C++ | |
GNU General Public License v3.0 only | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wordpress-playground
-
Things you forgot because of React
Sorry friend, WordPress already beat you to it: https://github.com/WordPress/wordpress-playground
- WordPress Playground: A WordPress that runs entirely in the browser
-
WordPress Playground: A WordPress that runs in the browser
> Is there a reason why using OPFS directly from SQLite doesn't work?
I'm guessing this means using SQLite WASM's built-in OPFS integration as described in these articles:
- sqlite3 WebAssembly documentation - Persistent Storage Options: OPFS - https://sqlite.org/wasm/doc/trunk/persistence.md#opfs
- SQLite Wasm in the browser backed by the Origin Private File System - https://developer.chrome.com/blog/sqlite-wasm-in-the-browser...
Within the Playground, SQLite interacts with the database file in MEMFS only, and the Playground coordinates the syncing from MEMFS to OPFS.
https://github.com/WordPress/wordpress-playground/tree/trunk...
The reason for this, I believe, is that the primary use case is/was to have the entire file system in memory, including SQLite's database file. This was the original implementation, and is still the default behavior. Persistence was later added as an optional feature.
The good news is that browser support for OPFS seems to be getting better. From the SQLite docs:
As of March 2023 the following browsers are known to have the necessary APIs:
-
WordPress Playground
One of the most exciting things at WordCamp Europe 2023 for me was discovering how far along the WordPress Playground project is. If you haven’t heard of the playground before, it’s a full version of WordPress, running directly in your browser!
-
WCGI: WebAssembly and CGI
WordPress has an official WebAssembly build for the browser and Node.js: https://developer.wordpress.org/playground https://github.com/WordPress/wordpress-playground
(Disclosure: I'm the creator)
-
WordPress testing official SQLite Support
I love the work going on there at WasmLabs, especially enjoying the articles with in-depth technical explorations.
After the article about running WordPress in the browser was published, there's a new project called WordPress Playground which is gradually preparing NPM or Composer packages to make it easier for people to run it.
https://github.com/WordPress/wordpress-playground/
They've been doing very detailed work, like making some patches to PHP and SQLite for improved compatibility with Emscripten, etc. It seems there's a lot of overlap with what WasmLabs has achieved and probably have continued to develop further. Perhaps there's an opportunity for collaboration.
- WordPress WASM
-
Hacker News top posts: Sep 25, 2022
WordPress WASM\ (28 comments)
libjxl
-
JPEG XL and Google's War Against It
> Regarding JPEG XL's mobile support, it makes sense it would see limited development if the company that manages one of the biggest mobile players has been the greatest restriction on their success. The lack of support also disincentivises manufacturers to prioritise support.
There was literally no involvement from any hardware vendor in the standardization of JPEG XL. It went from a Call for Proposals in Sept 2018 to Committee Draft in Aug 2019 with very little time for industry feedback. Contrast this with AV1 which had involvement from hardware vendors Intel, NVIDIA, Arm, AMD, Broadcom, Amlogic from the beginning as well as companies who ship media on hardware at scale such as Cisco, Netflix, Samsung and yes Google. These companies reviewed and provided significant feedback on the format that made it suitable for hardware implementation.
https://news.ycombinator.com/threads?id=JyrkiAlakuijala is a lead on the project and a Google employee, and active in JPEG XL development https://github.com/libjxl/libjxl/commits?author=jyrkialakuij...
- JPEG XL Reference Implementation
-
JPEG XL and the Pareto Front
https://github.com/libjxl/libjxl/blob/main/doc/format_overvi... is a pretty detailed but good overview. The highlights are variable size DCT (up to 128x128), ANS entropy prediction, and chroma from luminance prediction. https://github.com/libjxl/libjxl/blob/main/doc/encode_effort... also gives a good breakdown of features by effort level.
-
Compressing Text into Images
For JPEG XL, refer to its format overview [1]. In short its lossless mode uses a combination of multiple techniques: the rANS coding with an alias table, LZ77, reversible color transforms, a general vector quantization that subsumes palettes, a modified Haar transform and a learnable meta-adaptive decision tree for context modelling.
One good thing about JPEG XL is that its lossy mode also largely uses the same tool, with a major addition of specialized quantization and context modelling for low- and high-frequenty components.
[1] https://github.com/libjxl/libjxl/blob/main/doc/format_overvi...
- JPEG XL v0.9.0 Released
-
Stripping Metadata
The cjxl source is here. If you spot any reason why -x strip=exif may not work, tell me.
-
Www Which WASM Works
The problem is that the instructions for actually running the WASM file are not that clear... the docs the author mentions shows how to compile to WASM, which is easy enough, but then here's the instructions to make that actually work in the browser:
https://github.com/libjxl/libjxl/blob/main/tools/wasm_demo/R...
Yeah, you need some mysterious Python script, a JS service worker at runtime, choose whether you want the WASM or WASM_SIMD target, use a browser that supports Threads and SIMD if you chose that, make sure to serve everything with the appropriate custom HTTP headers... just reading that, I can see that to get this stuff working on non-browser WASM targets would likely require expertise in WASM, which is the point of the OP. WASM's UX is just not there yet.
-
First automatic JPEG-XL cloud service
https://github.com/libjxl/libjxl#usage
> Specifically for JPEG files, the default cjxl behavior is to apply lossless recompression and the default djxl behavior is to reconstruct the original JPEG file (when the extension of the output file is .jpg).
-
Why "sudo make install"?
I mean compiling a bleeding edge kicad, inkscape or jpeg-xl is easy. But will probably trash your system if you already have an older version installed.
-
XYB JPEG: Perceptual Color Encoding Tested
But you look at your image viewer that could have the lossless indicator? (and there is an issue open to add this indicator to the jxl files)
https://github.com/libjxl/libjxl/issues/432
What are some alternatives?
marmot - A distributed SQLite replicator built on top of NATS
qoi - The “Quite OK Image Format” for fast, lossless image compression
dod - DOS on dope. The last MVC Web framework you'll ever need
Android-Image-Filter - some android image filters
webrcade - Feed-driven gaming
DirectXMath - DirectXMath is an all inline SIMD C++ linear algebra library for use in games and graphics apps
wapm-cli - 📦 WebAssembly Package Manager (CLI)
libavif - libavif - Library for encoding and decoding .avif files
wp-sqlite-db - A single file drop-in for using a SQLite database with WordPress. Based on the original SQLite Integration plugin.
jxl-migrate - A simple Python script to migrate images to the JPEG XL (JXL) format
Platform - Qbix Platform for powering Social Apps (http://qbix.com/platform)
squoosh - Make images smaller using best-in-class codecs, right in the browser.