Julian S.

There is a saying in Germany. All good things come in threes. Today I received the last part of my three-part article series about rendering patterns published in the @entwickler magazine 🥳 It covers the topics #resumability, #reactservercomponents and #streaming #rsc #qwik

Open Source security back door mysteries with Cristian! Thanks for taking us on a chilly adventure! 😱🕵️‍♂️ #DevFest2024 #DevFestKA2024 @GDGKarlsruhe

.@GDGKarlsruhe DevFest is happening this Saturday! Join us at @DHBW_Karlsruhe for our community tech conf. We have world-class speakers, 3 inspiring tracks & an affordable ticket price of just €5. Only a few tickets left: devfestka.de #devfest #gdg #googledevelopers

A bunch of new followers here, so I thought I would introduce @ElectricSQL and how PGlite fits in. We are building a CDN native sync engine that can move your data in real time to where you need it. There are a few buzz words in there, so what do we mean? 🧵1/11

With PGlite + @ElectricSQL sync you can build an issue tracker handling 100k issues + 500k comments, synced from Postgres to PGlite in the browser! Super fast UI updates with all writes going though the local database, and Postgres FTS in PGlite for search 🔥

And sure, I'm dealing with these breaking changes daily. It's often frustrating, yet exciting, because shifting to a server-driven React world is no small task. But it will be worth it! That's why I'm working every day on my next course 👇 road-to-next.com

Announcing @voidzerodev: a company building the next-generation unified toolchain for JavaScript. We are the creators and core-contributors of Vite, Vitest, Rolldown and Oxc - and we will unite these projects under a coherent vision to power the next generation of web applications. We have raised $4.6M in seed funding led by @Accel - read more in the blog post: voidzero.dev/posts/announci…

Am Wochenende ist Europawahl! 🇪🇺 Jede Stimme zählt, auch Deine! 💪 Gemeinsam können wir viel bewegen. Und nicht vergessen: es darf zum ersten Mal ab 16 Jahren gewählt werden. #votewithattitude #Europawahl2024 #DeineStimmeZählt #WählenGehen #ZukunftGestalten

So, @vercel reverted all edge rendering back to Node.js 😬 Wanted to correct the record here as it's something I've advocated for in the past, and share what I've learned since then. Also, the "edge" naming has been a bit confusing, so let's clear that up here as well. What is edge, anyway? We have too many products with Edge 😅 First off, Vercel has an Edge Network. A request comes in for your site. The edge region can go grab some HTML or JS for your site and quickly return it. Great. Then, sometimes, you have routing rules. When that request comes in, redirect it, proxy it somewhere else, or add headers before continuing (e.g. Middleware). You don't need to go all the way back to the origin. This is also great. Sometimes those routing or configuration rules need to be read from a file. We have "Edge Config" which is like reading from a JSON file in every region. Again, still good. Now, what about rendering my application with edge compute? Not as great. But Lee, you said... Yeah, I gotta admit, this one fooled me. It sounded great at the start – running close to the visitor makes sense. If I constrain my site to use this limited runtime, and make the tradeoff for access to the Node.js package ecosystem, I can (hypothetically) get better performance. This hasn't worked for two reasons. First, and most obvious, is that your compute needs to be close to your database. Most data is not globally replicated. So running compute in many regions, which all connect to a us-east database, made no sense. I believe many folks understood this. But then, maybe this limited runtime was better even if I only run it close to my database? Well, that was wrong too. We tested it extensively with @v0. Using the Node.js runtime with 1 vCPU (our "Standard" performance) option for Vercel Functions had faster startups 🤯 Are there other reasons for edge rendering? If Node.js functions can be faster, especially with Node v20, what about cost? I expected an edge compute pricing model, which is based on only paying for when your compute runs (and never I/O), would always be cheaper. Turns out that was also wrong. It can be cheaper sometimes! But not for all workloads, so some nuance applied here. Same story for security. I wanted edge compute to work, but customers kept telling me they wanted a private connection to other services (i.e. Vercel Secure Compute), or had concerns (or no interest) in doing global data replication (e.g. data sovereignty). So now what? It's a good lesson for me to be careful with naming / nuance going forward. Also, networks have gotten really fast. We saw with @v0 that it was faster to do SSR + streaming with Node.js than edge rendering. Now we're running @v0 with Partial Prerendering to see if this is better or worse (it's still experimental). The summary of PPR is: user makes a request, the edge region starts streaming back the HTML for the fast initial visual, and then your compute still runs in us-east or wherever close to your data. So far this has been about 50% faster time to first byte than SSR + streaming. Pretty amazing. I'll be sharing more on Vercel Functions improvements soon, as well 🦀

Unser Softwarearchitektur-Kickstart mit Eberhard Wolff war ein voller Erfolg! 👏 Von Bounded Contexts bis Strategic Design haben wir viel gelernt – und das alles mit einer Prise Humor! 🧠 Vielen Dank, @ewolff, für die wertvollen Impulse! 🙏 #weiterbildung #architektur #haufencode

Du hast die #sugka letzte Woche verpasst? ☹️ Kein Problem, wir haben alles aufgezeichnet! 🎥 Die Vorträge von @rokatainment und @ewolff findest Du unter youtu.be/KOKrvzdNOzI und software-architektur.tv/2024/04/02/fol… #scrum #usergroup #agile

🔥 New video!! Learn how the browser's event loop, Web APIs, and (micro)task queues enable async non-blocking JavaScript youtu.be/eiC58R16hb8

Among contributors: @posva @renovatebot @_pi0_ @nicodevs @danielcroe @theoscoder @danielkelly_io @i5dr0id @lazzzis @ju_schaefer @PouyaMkh @nazarepiedady @lkirkun @broods_ @davidshq @dannyfeliz08 @Minighost_Alex @timipapi @SteBjoerne

🚨🚨🚨🚨 Apple will NOT remove PWA support on iOS 🥳🥳🥳🥳 👉This is an official statement form Apple that replaced today the previous excuses published around the removal. We did it, folks!

Rather than allow other browser engines to install-to-homescreen on iOS, Apple is removing the feature entirely in the EU. Some features are tied to install-to-homescreen, such as push messages. Apple is unshipping those for EU users. We need to act now: open-web-advocacy.org/apple-attempts…

Apple trying to break the Open Web by removing PWA functionality from iphone open-web-advocacy.org/blog/its-offic…

Open Source ist ein integraler Bestandteil unserer DNA. Wir entwickeln offen mit unserer Community seit Jahren unsere Software. Aus diesem Grund freut es uns, dass der etablierte Verein @osballiance auf uns setzt und unsere Urlaubsverwaltung im Einsatz hat. #OpenSource #HR

@angular Even if it is said that the JS universe is short-lived, it leads to competition. Other frameworks like as Astro already had some features before, but it's nice to see how the JS world no longer fights against each other but takes up and improves ideas. Grats!

Angular v17. The framework you love, with a fresh new look, and: 🦥 deferrable views ⚡️ up to 90% faster, intuitive built-in control flow 🏎️ up to 87% faster build times with hybrid rendering 🏗️ Vite + esbuild builds + more! goo.gle/angular-v17

Becoming a good engineer is about collecting experience. Each project, even small ones, is a chance to add new techniques and tools to your toolbox. ✍️ addyosmani.com/blog/collect-e…

Ich freue mich sehr über meinen ersten Artikel "In 6 Schritten eine Retrospektive mit ChatGPT durchführen" im @projektmagazin. 😊

I started @StorefrontUI four years ago. One of the things that I've learned is how broken most of the modern UI libraries are when you use them to solve the challenges of large-scale modern web applications. Almost always, you have to fight against the framework to achieve what you want, which makes using it counterproductive. This Friday at @WeAreDevs World Congress I'll share how we dealt with this problem in @StorefrontUI and how to leverage the same patterns for your own tools! Who am I meeting with?