@[email protected] π
@brianleroux
Followers
21K
Following
38K
Media
5K
Statuses
96K
helping build @sanity_io; aws serverless heroes; indieweb developer π€
unceded Coast Salish territory
Joined January 2007
the best solution to a problem is eliminating the conditions that create that problem rather than adding another solution that creates new unique problems
14
63
348
Hometown hero π Arshdeep Bains is tonightβs first star!
12
178
2K
Netlify is the only place outside of Vercel where Next can be deployed on a serverless front-end cloud with support for all the advanced features. Today we're joining Open Next and starting to share our expertise with the broader community to help make Next run on more
π€ We're moving our open-source Next.js adapter to the OpenNext GitHub organization and will begin collaborating across providers, like @Cloudflare and @SST_dev, to make sure Next.js runs well everywhere.
12
29
521
Big congrats to @begin's team, @brianleroux @macdonst et al... on joining @sanity_io! ππΎ. π
sanity.io
Sanity welcomes the Begin.com team, enhancing our Content Operating System with powerful content compute capabilities.
0
1
6
compute isolation is a good idea but nothing beats learning why the hard way π
0
0
1
Note: I'm not saying you *can't* use click and submit events. If you look at the Enhance readme you can see how (even vanilla extending HTML element works perfectly fine serverside as long as you implement a render method... we call this "implementing an interface"... )
0
0
0
SSR for web components is demonstrably not hard. But I ack maybe it is if you are trying to completely emulate a browser in a backend context. Tonnes of conditionals required to render. So ..don't do that? Backend doesn't have click and submit events for good reasons..
1
0
1
Source, released in 2021, is here https://t.co/bZFFZi8xKe
github.com
Server side render for custom elements. Contribute to enhance-dev/enhance-ssr development by creating an account on GitHub.
1
0
0
Enhance implements serverside rendering for web components. It's less than 500 LOC, interpreted not transpiled, using the standards compliant parse5 library. You can still upgrade elements clientside (but most don't require that thx to css). No conditionals to render!
2
1
7
It's ok if they aren't right for you. But if you're going to write a lengthy article about it recommend learning about logical fallacies first. It'll make your arguments less cringe to web platform experts. who knows? Maybe your feedback could improve the web for everyone even.
0
0
5
Check out https://t.co/nmbRTJx0Mr to see what you can do. Make sure to test with a performance tool like lighthouse. Vastly better on any metric we can measure.
enhance.dev
The HTML first full stack web framework
1
1
5
I laugh at all this βweb component vs frameworks nonsenseβ specially from a pragmatic point of view. If we had adopted βFramework Xβ when we rewrote the Salesforce UI a decade ago, they would have been complete fucked right now due to the incompatibility of βnew ideasβ and the
"Frameworks are a testbed for ideas that may or may not work out. We all need to be OK with that. Even framework authors. Especially framework authors. More importantly, we all need to stop being salty when our way isnβt what makes it into the browser." https://t.co/Ph5tTwhMb3
5
7
59
Incredible how much drama and strife there is here for.. *checks notes* ..rendering HTML
1
0
6
Seesh!! Big numbers from @awscloud - excellent rationale from @donkersgood at @AWScomsum on why #Serverless makes sense.
2
4
13
Took us 5 years to land the first million developers. Now 4 years later we crossed 5 million developers on our platform. Come celebrate with us at Netlify Compose! https://t.co/APLC329wnb
netlify.com
Today, Netlify celebrates five million developers. Join us and celebrate on the web, with our celebration site and interactive 3D game.
17
8
133
clientside code should have no concept of auth. either you are authenticated, with an httponly cookie, or you aren't. code delivered should reflect that. if not, good news, there's an opportunity to improve! π
3
2
15