WordPress Wars Continue, React Server Functions, and Web Component Backlash
Full Description
WP Engine is taking Automattic and Matt Mullenweg to court. The complaints are numerous and juicy: extortion, libel, slander, and include screenshots of text messages, tweets, and emails that look pretty damning against Automattic. The whole story has “Made for TV documentary” written all over it. In slightly less controversial news, React 19 has renamed its Server Actions to Server Functions. This name change brings React’s server functions more in line with other frameworks who support the same sort of functionality like SolidJS, Astro, TanStack Start, and others. Also in a follow up from the last episode where we talked about a new addition to the Web Components world allowing for web components with SSR via the Declarative Shadow DOM, a good number of JavaScript framework creators shared their misgivings about the creation of Web Components. Ryan Carniato and Rich Harris were two of the most vocal, and basically said WCs have made their work writing frameworks harder, not easier, and WCs are not the future. Our Fire Starter for today is a blast from the past: the marquee HTML element. For the youngsters out there, the marquee element existed since the earliest days of the web and was used to insert a scrolling area of text. It presented many accessibility issues, and has since been deprecated in favor of better ways to animate elements but it still exists in the wild. Check out the example in the MDN docs if you want, but don’t subject anyone to it.
Links
- Web components are not the future from Ryan Carniato
- Rich Harris agrees that web components have not been the boon we thought they'd be
- Server Actions become Server Functions in React 19
- Wordpress vs. WP Engine drama continues
- OpenAI raises $6.6 billion
- Waymo coming to Austin and Atlanta
- <marquee> HTML element
- The Tourist TV series
- The Wild Robot movie
- Adafruit sensors