Because tailwind_compiler is written in @ziglang.bsky.social I can build an in-browser compiler pretty easily by targeting Wasm. Here is a demo
Try for yourself: beaconcms.github.io/tailwind_com...
The full @tailwindcss.com v4 tailwind_compiler is a 122kb Wasm asset
Heat pumps are increasingly becoming required by regulations and thus suppliers are intentionally over pricing them to make more money. Meanwhile, "get 'er done" installers are forced to install them in low ventilation locations where they are completely ineffective and provide worse outcomes.
I've completed the Zig 0.16 update for Zap. Now just waiting on the linux builds to complete then I can push.
Decided to look into what the 0.15.2 -> 0.16.0 upgrade for Zap's Zig fork would require.
Two hours later and I'm nearly ready to push it all up. Async will still wait for now but Zap should get some nice additional optimizations especially from the newer LLVM.
With Zig 0.16 now out I'm going to continue to work with Zig 0.15 for now for Zap. I may update Zap's Zig fork once 0.16.1 comes out but the big feature I was hoping for is Io.Evented but that's still marked as experimental.
I'm OK with that though, I have a ton of work on my plate to solve with single process work right now in Zap that I want to harden and prove out before introducing a concurrency model
oh wow, I wasn't expecitng this until later in the year
"I want you to add value for users and remove entropy. No mistakes."
No, mostly architecture changes. Cache all the things but the biggest culprit was we were compiling a module per page at runtime. Also, putting into place a mature cache invalidation strategy. But claude is useful for reading logs
I'm declaring victory on the Beacon CMS memory issues
Wrote tailwind_compiler in Zig with an Elixir NIF wrapper that has an order of magnitude faster Tailwind v4 compilation compared to Tailwind CLI v4.
This is for Beacon, API is being adjusted for Beacon. Feel free to use but I won't be accepting PRs.
github.com/beaconcms/ta...
I’m bringing it back
New eager loading feature, which is configurable per site in Beacon.
if cache is cold on first hit it kicks off the cache warming job then will show this temp page until the site is available. Stampeding herds are properly managed as well.
She ducked off for a bit. There were more important things to address. It is our absolute pleasure to welcome Quinn Wilton back.
Last I handed her a mic she threw DIY dental care to people. I think this one is about Elixir...
www.goatmire.com/talk/a-hundr...
#elixirlang #goatmire
I don't know why people keep insisting that AI is good at writing
@elixir-lang.org
btw, I'm glad she lost. Good riddance.
It is one of systemic issues that has lead to the larger macro issues you're alluding to. When candidates are just opportunistic like her and seen to use an elected position for fame and national recognition rather than actual representation, yes it's an important issue.
I've got for-comprehension working in Zap
High-level programing languages are just prompts for machine code.
This is just going to make me swear at it more
We have nearly $40T in debt.
We have lobbyists that fight this.
We have weak feckless leaders.
We have a population that is focused only on what could have an ROI in the next three months.
If there is anything to be learned from Pam Bondi, it's that she is a horrible person.
so it's just fingerprinting?
browser extensions is a completely different animal, the article should be amended. It reads as if it is scaning your disk
the article references discovering what software is installed. Unles this is in Microsoft's own browser and they have some hidden feature to allow for that there's no way the browser security model would permit this
How is it possibly doing that through a browser?
I've never liked `with` in Elixir. So Zap is going to have a "catch basin" operator that will jump to when anywhere in the pipe returns {:error, _value}
