<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>svelte on jawr</title><link>https://jawr.github.io/jl-lu/tags/svelte/</link><description>Recent content in svelte on jawr</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© {year}</copyright><lastBuildDate>Mon, 22 Mar 2021 18:02:55 +0900</lastBuildDate><atom:link href="https://jawr.github.io/jl-lu/tags/svelte/index.xml" rel="self" type="application/rss+xml"/><item><title>it svelte good</title><link>https://jawr.github.io/jl-lu/blog/swapping-out-react-for-svelte/</link><pubDate>Mon, 22 Mar 2021 18:02:55 +0900</pubDate><guid>https://jawr.github.io/jl-lu/blog/swapping-out-react-for-svelte/</guid><description>React I have been using React with Redux for many projects over the last few years and although I appreciate the new design patterns it introduced me to and the dynamic interfaces it allows, there has always been a slight annoyance with the amount of boilerplate required when following particular recommended patterns.
Of course I appreciate that these patterns are mostly targeted at very large and complex applications.
As an attempt to resolve this my most recent projects have used the classic server side generated templates with small Javascript functionality added with the tiny AlpineJS .</description></item></channel></rss>