Ahh cool thanks, pretty sure I saw somewhere that Buildkite was using Phlex too by the way.
13.09.2025 17:55
👍 0
🔁 0
💬 1
📌 0
Ahh cool thanks, pretty sure I saw somewhere that Buildkite was using Phlex too by the way.
@joel.drapper.me Do you have a list of companies using Phlex?
Trying to convince people to switch from ERB and having this would make it easier.
Indeed!
Any plans to bring some of these ideas to the "Phlex ecosystem"?
Not only that, but it live reloads it, uses Capacitor plugins when possible and falls back to their web implementation when not compatible. What?!
capacitor.nexusbrowser.com/capacitor
TIL about Nexus Browser by @damiant.bsky.social, an iOS/Android app that detects and runs the @ionic.io project you're running on VS Code automatically.
I literally opened the app on my phone and the project I'm working on on my laptop appeared out of nowhere 🤯
The extension is simply awesome. Great job working on that and please don't abandon it!
Awesome, that helps, thanks a lot!
@mhenrixon.bsky.social found a nice way to get the same behavior (I hope) by using vanish on before_template (github.com/PhlexyUI/phl...)
If you have some time, please let us know if that's a good way to get the same behavior!
(Or if it's going to be documented, we'll read it there 😃)
@joel.drapper.me Just found out that Phlex 2.0 is going to remove Phlex::DeferredRender, yet I can't find docs mentioning that for upgrading from v1.
Is that going to be documented?
Just a heads up in case y'all are missing adding that since I couldn't find any beta docs repo on Github.
I don't think there's anything you can do though.
Anyway, I'm building an app for the Mexico GDL region and learned about this when I spin up a Bucharest machine and noticed latency still was bad. I ended up temporarily disabling Cloudflare for the app.
You can search for "cloudflare ewr from europe" to find out more. e.g. community.cloudflare.com/t/our-server...
The images I shared are from today, and you can see that when this happens, it can make websites load VERY slow.
Yeah I think I know what's up, same thing happened to me:
Apparently there's a dispute between Cloudflare and some ISPs like Deutsche Telekom, so even though the user is in Europe, sometimes it will go through the Newark, NJ, USA server.
See the response headers on attached pics (EWR vs VIE).
In other words, perhaps starting with the "legacy" approach named as "simple", since that's more familiar to those coming from default Rails. Then explaining there are better ways and why (streaming).
Of course, this is not critical, just some thoughts about making the docs a bit newbie-friendly.
Nice!
I'm reposting this here from X (hadn't realized you were fully gone):
The new layout system is tripping up beginners (seeing this with some junior devs I'm coaching). Maybe the "legacy" approach could be renamed to "basic" or "simple" to help newcomers ease in better.
💡 Would be nice to edit it via CSS too, for example, if you already have your theme configured and would like to tweak it via the theme generator, you'd paste it in there and tweak away.
Looks awesome!
Takes quite to load in Europe (Budapest). A whooping 22.6 seconds. I'm guessing it's the same server as the main docs site, because that's also pretty slow from here too, albeit not as bad.
Still, I'm personally excited about this. It'll give me a solid foundation to code exactly how I want to, which sounds pretty fun.
The interesting thing about Rails though, is that its opinionated nature means you can clone an app and be immediately productive - you know where things are and how to change them. So Yippee's flexibility becomes a double-edged sword.
Loving the router implementation in Yippee.
After years of seeing the same Rails routing/controller patterns over and over, it's a breath of fresh air. The flexibility to handle routing however you want is great for building apps exactly your way.
