aboutsummaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
Diffstat (limited to 'content')
-rw-r--r--content/posts/2022-10-06- state-of-web-technologies-in-year-2022.md13
1 files changed, 11 insertions, 2 deletions
diff --git a/content/posts/2022-10-06- state-of-web-technologies-in-year-2022.md b/content/posts/2022-10-06- state-of-web-technologies-in-year-2022.md
index e8d7611..47938d7 100644
--- a/content/posts/2022-10-06- state-of-web-technologies-in-year-2022.md
+++ b/content/posts/2022-10-06- state-of-web-technologies-in-year-2022.md
@@ -11,8 +11,9 @@ draft: false
113. [Bundlers and Transpilers](#bundlers-and-transpilers) 113. [Bundlers and Transpilers](#bundlers-and-transpilers)
124. [Jam Stack, Mach Stack no snack](#jam-stack-mach-stack-no-snack) 124. [Jam Stack, Mach Stack no snack](#jam-stack-mach-stack-no-snack)
135. [Tailwind CSS still rocks!](#tailwind-css-still-rocks) 135. [Tailwind CSS still rocks!](#tailwind-css-still-rocks)
146. [Web development has a marketing issue](#web-development-has-a-marketing-issue) 146. [Code maintainability](#code-maintainability)
157. [Conclusion](#conclusion) 157. [Web development has a marketing issue](#web-development-has-a-marketing-issue)
168. [Conclusion](#conclusion)
16 17
17## Introduction 18## Introduction
18 19
@@ -108,6 +109,14 @@ I have also noticed that people who criticize Tailwind the most never actually u
108 109
109But you know, whatever floats your boat! 110But you know, whatever floats your boat!
110 111
112## Code maintainability
113
114Somehow, people also stopped talking about maintenance. If you constantly try to catch the latest and greatest train, you are by that logic always trying new things. Which is a good thing if you want to learn about technologies and try them. But for the production environment, you have to have a stable stack that doesn’t change every 6 months.
115
116You can lock dependencies for sure. Nevertheless, the hype train moves along anyway. And the mindset this breads goes against locking the code. These bleeding-edge rolling release cycle is not helping. That is why enterprise solutions usually look down on these popular stacks and only do bare minimum to appear hip and cool.
117
118With that said, I still think that progress is good, but should be taken with a grain of salt. If your project is something that should be built once and then rarely updated, going with the latest stack is a possible way to go. But, if you are working on a project that lasts for years, you should probably approach it with some level of caution. Web development is often times too volatile.
119
111## Web development has a marketing issue 120## Web development has a marketing issue
112 121
113I noticed that almost every project now has this marketing spin put on it. Everything is blazingly fast now. I get it, they are competing for your attention, but what happened to just being truthful and not inflating reality. 122I noticed that almost every project now has this marketing spin put on it. Everything is blazingly fast now. I get it, they are competing for your attention, but what happened to just being truthful and not inflating reality.