Quentin Renard

@addyosmani @googlechrome Can't wait to see what you're up to next, Addy! I learned so much through your content in the past 10+ years.

After ~14 years working on Chrome, it's time for a new chapter. When I joined the @googlechrome team, I walked into a group that believed the web could be fast, simple, safe, and a joy to build on. I still believe that today, and I am continually in awe of what the team and the broader web community do every day. My last day with Chrome will be today. After that, I am excited to be moving into a new role at Google. More on that soon. Over the years I have been lucky enough to work with many teams across Chrome on new APIs, performance, DevTools, benchmarks, extensions, automation, and the broader evolution of the web platform. From Core Web Vitals and Lighthouse, to @ChromeDevTools and CDP, to efforts like Speedometer, Interop, Baseline, PWAs, AI, and our collaborations with frameworks and platforms, the constant has been the same: make the web faster, more reliable, and easier to build on. What I will remember most is not any single launch, but the way this team builds. Listening to users and developers. Measuring. Sweating the details. Making hard calls with empathy. Taking the long view while still shipping with urgency. That culture is the reason Chrome has had the impact it has on the ecosystem. To everyone in the @ChromiumDev and web community I have had the chance to work with: thank you. Thank you for the trust, the feedback, the late nights, the careful reviews, and the countless ways you pushed the platform and its tooling forward. It has been a privilege to learn from you and to build alongside you. I will still be cheering for Chrome and for the open web. If we have worked together or share an interest in the future of the web, AI, and developer experience, I would love to stay in touch as this next chapter begins.

@iamdevloper @gammaapp

Is there a Cursor for building Keynote talk slides?

@taylorotwell @r9ray There are definitely better approaches to implement that scenario (eg. using dedicated relationships), but this is the first thing that came to mind where someone enabling it globally might run into more queries than before. 2/2

@taylorotwell @r9ray Big one indeed! Eager to test it 😁 In a scenario where only the first or first few comments are rendered, or similarly, only the posts of the first user retrieved are rendered, this would end up loading a lot more than needed. 1/2

This is a big one. In this code snippet, Laravel is essentially calling $users->load('posts.comments') automatically for you behind the scenes, just in time. 🧠 Thank you for your work on this @r9ray. 🙏

@VotrubaT @karpathy @jeremyphoward Thanks for @rectorphp, man! One of the best things that happened for the PHP community in the past few years ❤️

@iFox @karpathy @jeremyphoward Awesome, I was looking exactly for this. Will check, thanks for sharing!

It's 2025 and most content is still written for humans instead of LLMs. 99.9% of attention is about to be LLM attention, not human attention. E.g. 99% of libraries still have docs that basically render to some pretty .html static pages assuming a human will click through them. In 2025 the docs should be a single your_project.md text file that is intended to go into the context window of an LLM. Repeat for everything.

@VotrubaT @karpathy @jeremyphoward We launched the directory a couple months ago with 70 files. Hundreds of people have been reaching out since then + we crawled @Cloudflare's top 100k domains to find more recently, and we just crossed 450 entries!

@VotrubaT @karpathy Great minds think alike! Check llmstxt.org from @jeremyphoward and the directory of adopters I've been working on directory.llmstxt.cloud.

@dazzagreenwood @joyceverheije We added it a couple days ago! Look for Agent in search. I guess we should remove that space in the name, sorry!

@iFox @joyceverheije Beep Boop: Just checking in on adding OnAgents.org to your most excellent directory, please?

@iFox @joyceverheije Big LLMS fan here! How do I add onagents.org/llms-full.txt and onagents.org/llms.txt to your awesome LLMS directory?

@dazzagreenwood @joyceverheije Or just a tweet like you did works too! We'll add them later today.

@dazzagreenwood @joyceverheije 👋 you can DM us for now, but we're working on open sourcing the dataset and make contributions as seamless as possible.

Twill 3.4.0 is now available! 🚀 This release brings general improvements and bug fixes requested by the community. Check out the release notes below and stay tuned for more soon! 👇 #Laravel #OpenSource #CMS

@chrisjack @PovilasKorop @twillcms and @lunarphp can be used together in the same @laravelphp app, they make a great combo! Twill is used by many as a highly flexible product information management tool, too. It is frontend agnostic though, so the frontend experience is entirely up to you (no themes).

@PovilasKorop are those ones you listed well-support an e-commerce site as a module or plugin like woocommerce?

Ok, with the recent events, I feel the need to review Laravel CMS options in a video. Most popular ones: - Statamic - Winter CMS - October CMS - Twill Anything else I need to add to that review? P.S. Still not sure if it will be one video or a series.

@sander_scode @alexmansfield @photomatt x.com/iFox/status/18…

@alexmansfield @photomatt We need a community movement to build a new CMS on Laravel

Please consider my plugins hosted on wordpress.org to be abandoned. When @photomatt was asked if owning an ACF license banned users from logging into .org, he replied "Consult an attorney" See:

@GBBourdages @joshmanders Better WordPress isn't how I describe it, as nobody can compete with plugins or themes at that scale, but @twillcms is a mature and flexible solution for projects that require a scalable architecture and the ability to manage complex data, without the bloat or security concerns.

@joshmanders Time to build a better WordPress with Laravel

You know what the craziest thing about this #wpdrama is? Usually when a for-profit entity starts getting uppity about people making millions off their open source by following the licenses they set forward, the community usually hard forks it and moves forward telling the stewards they can have their OG code, but everyone else is moving on with a fork. But with WordPress, it's in an interesting spot where the energy and effort to fork and upgrade everywhere is just not worth it, so instead the community is fracturing into other communities and completely replacing WordPress. This could be the end of WordPress as we know it.

@CodeWithCaen @aap_twak @statamic @filamentphp @HydeFramework @twillcms @CodeWithCaen 👋 let's chat!

@aap_twak @statamic @filamentphp @HydeFramework @twillcms How have I not heard more about this? Wonder if a HydePHP integration is incoming...

#Laravel-based alternatives to #WordPress: @statamic If you need a CMS @filamentphp If you need an Admin Panel @HydeFramework If you want a blog without security vulnerabilities and expensive hosting

@philsola_123 @twillcms @laravelphp @TightenCo Regarding the menu system, Twill is built to be flexible. While the default UI uses a top menu, it's totally possible to customize the layout to suit different navigation needs, including a sidebar. I’d be happy to point you in the right direction if you decide to give it a go!

@philsola_123 @twillcms @laravelphp @TightenCo Twill has been around for a while now, we launched it publicly in 2018. We’ve been constantly evolving it since then based on community feedback and real-world use cases. As for the docs, they’ll definitely keep expanding. They are open for contributions as well!

What planet are these people living on? $99 / month for 3 users and 3 user roles with a limit on blog posts & pages - Jeez! The CMS market is absolutely ripe for the taking I'd say...

@philsola_123 @twillcms @laravelphp Exactly, it's a blank slate with a lot of core CMS features ready to compose your own tailored CMS from. This article from @TightenCo is a great introduction: tighten.com/insights/getti…

@iFox @twillcms @laravelphp Thanks Quentin for reaching out! I actually hadn’t come across twill before so will definitely be taking a look at this. Is the idea you build your own CMS with the building blocks?

@philsola_123 My team and I have been on a mission to offer those premium features for free and under a permissive OSS licence, check out @twillcms if you are into @laravelphp!

@philsola_123 I hear you! Most SaaS CMS pricing is ridiculous. Not even talking about enterprise plans, often needed for fundamental security features like MFA or SSO.