We've been doing a lot of agentic forecasting and missing good visibility into what's working what's not. Surprisingly there are very limited solutions to track forecasts. Open sourcing this which we've been using internally - ForecastOps, a library that gives observability to production forecasts. Interested in thoughts, I have some ideas of where this can go (like a/b et).
Is it a breeze to work with and seamlessly supports SSR, isomorphic code, and type safe library and data sharing, because it uses the same language on the client and server, and does it inspire joy and delight because it's fun and easy to work with like SvelteKit? Since not, then why bother with PHP? Because the alternatives are so much better.
In no way is PHP better than JavaScript, and the simple fact that JS runs natively in both the front and back end is astronomically more important than a point-by-point comparison of language features that PHP loses anyway.
1. Yes, SSR matters. SvelteKit users sometimes get frustrated that it's too SSR-centric, and we have plans to address that in the next major version. But SSR is the default for a reason! Our ultimate responsibility is to end users
Ben McCann @BenjaminMcCann:
Some data from Google (big thank you to @rick_viscomi and @imkevdev !)
Client-side-only SPAs are extremely detrimental to latency as they add a network round-trip before rendering begins.
You can win at LCP by making it harder to build client-side apps
This is really interesting, and idea that I have been considering building for a while. I think this is better than anything I could've whipped up in that time.
I'm interested in the community starts regarding the ethics and copyright aspect of this application of AI. If we're training, models off the continent of books, and the user hasn't purchased the book, where does that leave us?
reply