I think that is a very valid criticism. I wanted to keep the article concise, but I should have elaborated more on why Go+HTMX+Templ solves the dependency management fatigue.
As I said in the article, it is mainly anecdotal evidence, i.e. the experience from having to maintain projects with either React or Go+HTMX.
For example, in the Go+HTMX project I handle state management and routing solely with the Go stdlib (which is very very stable IMHO), I don't have to ever worry that a dependency update will force me to perform painful refactoring work.
Maybe in a future article I can expand on these points, thank you for the feedback :)
Hi, author here.
At least from my personal experience, there are still many jobs in which the main focus isn't frontend development, and per se React.
I do have to work with React from time to time. But it isn't my main focus. I usually work implementing backend systems (with Go, SQL [Postgres], Redis, etc.) and infrastructure as code with Terraform.
It is nonetheless extremely cheap (in comparison to rents in Augsburg and near-by Munich) and has life-changing consequences for the people living there, since they do not have to allocate a big amount of their income into housing.
In comparison: The average rent in Augsburg for a 60m³ flat is around 756 Euros (way more for new contracts and furnished flats), the median net income in Germany is ~ 2244 Euros.
One downside, if you're on the taller side, is that the doors in the Fuggerei are only like 5'8, though - and if you're taller than 6'4 or so, even the ceiling height becomes a problem. :D
I don't know why medieval homies built doors so short. They weren't short people. There's documented incidents of medieval kings accidentally dying from hitting their head on door lintels,
- "Charles died in 1498, two and a half years after his retreat from Italy, as the result of an accident. While on his way to watch a game of jeu de paume (real tennis) in Amboise he struck his head on the lintel of a door.[22]."
This surprised me, as I'd heard otherwise. Per https://www.sarahwoodbury.com/how-tall-are-you/, "the average height of people who lived in the 9-11th centuries was comparable to ours today. It then declined slightly during the 12th through 16th centuries, and hit an all-time low during the 17th and 18th centuries – when those doorframes were made."
A 2.5 inch difference in mean heights isn't enormous, and I think doesn't fully explain what the parent comment was surprised by—the merely 5'8" (173 cm) tall doorframes in the Fuggerei. Considering individual variations, something like a quarter of medieval adults should be outright taller than that.
Hi Fatih,
I just wanted to let you know that I am a very avid reader of your email newsletter. I really get happy every time an email with one of your new articles arrives at my inbox. Thanks to your reviews of keyboards I will hopefully soon be able to get one of them myself.
In summary, I just wanted to thank you for taking the time to write the articles. It's definitely more time consuming than tweeting (I don't have a twitter account at all, I dislike the atmosphere there and I also prefer to consume longer texts with more content), so I just wanted to let you know that there's a bunch of people out here reading your texts and enjoying them!
Hi there. Thanks a lot for the kind words. One of the reasons I started to spend more time on my blog is because of the reasons you listed. I know X/Twitter has still its place, but I've discovered that people like to read long-form with nice pictures.
I am currently almost entirely developing in Go. And for that I have a highly customized Vim environment, which really took me a while to get to where it is right now (it works very well, thanks to the great 'vim-go' plugin). Nonetheless, I am starting to have to develop more stuff in other languages like js and Elixir, and I definitely do not want to invest all that time tweaking my vimrc to have all the IDE bare functionality that works so well in Go. I was starting to consider making the transition into neovim, but Helix sounds almost like a plug-and-play solution with sane defaults (which is exactly what I would like to have). Is it better that I go for Helix, or is LunarVim or AstroVim actually what I am looking for?
Helix is a simple install, easy to give it a try and see what you think. For most people, there’s no configuration necessary to get started. I jumped through the hoops to get C++ tools in a variety of editors, and nothing was as simple as Helix for me.
Do you work with Svelte and SvelteKit professionally or primarily on side project? How do you deal with the breaking changes that have taking place within SvelteKit, i. e. SvelteKit still not being on a major stable version yet?
Thanks a lot for the feedback. I am starting to get serious about learning the frontend side of things (coming from a backend/DevOps professional background). Especially the part of "React is a hot mess with so many ways to do all the things..." has made me prefer Svelte over React, and I really enjoy Svelte's idiomatic way of handling reactivity, I find it super intuitive. I guess I was just feeling insecure about putting so much time into Svelte, because I mostly only hear about people working with React.
Yeah, at this moment there is a lot of momentum behind React, and so there are lots of jobs/opportunities out there.
But just like jQuery had its time, and Angular, so too will React fade. And we will look back and think, "whoa that was crazy".
Svelte's surface area is small enough and sane enough that I wouldn't feel bad investing there. You can just spend time getting stuff done instead of obsessing in React land about useEffect vs useCallback and nesting components 20 levels deep etc.
If you want to keep the sanity of Svelte but go for a larger job market and community, Vue is also a pretty good option.
The first two CMU courses are goated. I recommend reading at least some of the papers Pavlo says to, but if I'd have to recommend a particular one it'd be "Architecture of a Database System": https://dsf.berkeley.edu/papers/fntdb07-architecture.pdf
I am trying to get a more than superficial level of knowledge on deploying services on relational databases with a lot of traffic. I don't know if it makes sense to grab any manual of a relational database, like PostgreSQL or MySQL, or if that is too specific and it makes more sense to start with a more general book.
[Please do not suggest Designing Data Intensive Applications, I am already reading it :) ]
Moreover, what are the best resources you know of that you used to learn SQL queries and their syntax properly? Thank you very much!
I think that is a very valid criticism. I wanted to keep the article concise, but I should have elaborated more on why Go+HTMX+Templ solves the dependency management fatigue.
As I said in the article, it is mainly anecdotal evidence, i.e. the experience from having to maintain projects with either React or Go+HTMX. For example, in the Go+HTMX project I handle state management and routing solely with the Go stdlib (which is very very stable IMHO), I don't have to ever worry that a dependency update will force me to perform painful refactoring work.
Maybe in a future article I can expand on these points, thank you for the feedback :)