diff options
Diffstat (limited to 'public/state-of-web-technologies-and-web-development-in-year-2022.html')
| -rwxr-xr-x | public/state-of-web-technologies-and-web-development-in-year-2022.html | 220 |
1 files changed, 0 insertions, 220 deletions
diff --git a/public/state-of-web-technologies-and-web-development-in-year-2022.html b/public/state-of-web-technologies-and-web-development-in-year-2022.html deleted file mode 100755 index 2d9e622..0000000 --- a/public/state-of-web-technologies-and-web-development-in-year-2022.html +++ /dev/null | |||
| @@ -1,220 +0,0 @@ | |||
| 1 | <!doctype html><html lang=en-us><meta charset=utf-8><meta name=viewport content="width=device-width,initial-scale=1"><meta name=generator content="JBMAFP - github.com/mitjafelicijan/jbmafp"><link href="data:image/x-icon;base64,AAABAAEAEBAAAAEAIABoBAAAFgAAACgAAAAQAAAAIAAAAAEAIAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAL69vf8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAv76+/8LBwQkAAAAAAAAAAAAAAAC+vb3/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAL+9vf/Bv78JAAAAAAAAAAAAAAAAu7q6/wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC7ubr/vr29CAAAAAAAAAAAy8nJAZ6foP8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAnqGj/6GipAoAAAAAHLjU/xcXHf/BwsL/I8XY/yPK3v8XGiD/IbjL/yPF2f8XGiD/Fxkf/yLF2f8gnK3/Fxog/62ztv8fwNf/FRcd/x271v8mz93/GRsi/xkXHf8p097/GiIp/xobIv8p0t3/KdPe/xocIv8fYmr/KNPe/xoZH/8aHCL/J87c/xy81/8VFxz/IsPZ/8zS0/8XGiD/Ir/R/yPH2/8XGiD/Fxkf/yPH2/8dd4T/GBog/yPJ3f8jyNr/uru9/xcUGv8cudb/EhITDKi5vRKlvMP/RUpOERwcHRAdOj4QHTk8EBwdHRAdNTgQHTo/EBwcHRAcHB0QSGduEKW4vf+koqQfHzg+EBqz0ewSFRv7EyMr/xq51vsTERb7ExUb+xq41fsau9j7ExUb+xiPp/sZudb7ExUb+xMVG/sZuNX/GKvI/BIUGfMdvdn/IrfL/xcaIP8n1eb/J9Dh/xkcIf8ZGR7/J8/f/xxCSv8ZGyH/J9Dg/ybQ4P8ZHCL/FSQs/yPK3/8UExj/GE1b/ybS5P8ZGB7/Ghwj/ynW5P8p2Ob/Ghwi/yWrtv8p1eH/Ghwi/xocIv8p1uT/J8XT/xkcIv8m1un/Hb7d/xUYH/8hzOr/HtHu/xcaIf8XGB//I8vi/xgxOv8XGSD/I8rg/yPK4P8XGiD/GUFL/yPP6f8SERj/Fhkh/x3A4f8AAAAAJ2f9/ydr//8mZPH/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAlYu38J2v//ydo/f8AAAAAAAAAAAd8/fkFqf//Iob8sAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMY39awWr//8FfP3/AAAAAAAAAAAFm/7/SfD//wR+/f8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAOB/f9B7v//BaX+/wAAAAAAAAAAQ878SAyZ/v9n1v4KAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADu9v8DDJb+/z3N/XgAAAAA3/sAAN/7AADf+wAA3/sAAAAAAAAAAAAAAAAAAN/7AAAAAAAAAAAAAAAAAAAAAAAAj/EAAI/5AACP8QAA3/sAAA==" rel=icon type=image/x-icon><title>State of Web Technologies and Web development in year 2022</title><meta name=description content="Initial thoughtsThis post is a critique on the current state of web development."><meta name=author content="Mitja Felicijan"><link rel=alternate type=application/rss+xml title="Mitja Felicijan's posts" href=https://mitjafelicijan.com/index.xml><link rel=alternate type=application/rss+xml title="Mitja Felicijan's notes" href=https://mitjafelicijan.com/notes.xml><style>:root{--border-color:gainsboro;--border-size:2px;--link-color:blue;--bg-color:#eee}*::selection{background:var(--link-color);color:#fff}*::-moz-selection{background:var(--link-color);color:#fff}*::-webkit-selection{background:var(--link-color);color:#fff}body{padding:2.5rem;max-width:1900px;background:#fff;font-family:sans-serif;line-height:1.35rem;font-size:16px}hr{border:0;border-bottom:var(--border-size)solid var(--border-color);margin-block-start:1.5rem}a{color:var(--link-color);text-decoration:none}h1,h2,h3{line-height:initial}h1{font-size:xx-large}footer{margin-block-start:2rem}cap{text-transform:capitalize}blockquote{font-style:italic}table{max-width:100%;border:var(--border-size)solid var(--border-color);border-collapse:separate;border-spacing:0}table thead tr th{border-bottom:var(--border-size)solid var(--border-color);text-align:left}table th,table td{padding:.5em .8em}ul.list li{padding:.2em 0}ul{line-height:1.35em}pre{text-wrap:nowrap;overflow-x:auto;padding:0 1em;border:var(--border-size)solid var(--border-color)}code{padding:0 3px;font-size:14px;border:0;background:var(--bg-color)}pre code{line-height:1.3em;background:#fff}pre,code,pre *,code *{font-family:monospace}figure{margin-inline-start:0;margin-inline-end:0}figcaption{width:800px;max-width:100%;text-align:center}figcaption p{margin:.3em 0 1.5em;font-style:italic}img,video,audio{width:800px;max-width:100%;border:var(--border-size)solid var(--border-color);padding:.5em}header nav{display:flex;gap:.9rem}article iframe{margin:0!important}audio::-webkit-media-controls-enclosure{border-radius:0}@media only screen and (max-width:600px){body{padding:.5em;word-wrap:break-word}header nav{gap:.7rem}header nav .hob{display:none}a{word-wrap:break-word}img,video,audio{padding:0}}</style><header><nav class=main itemscope itemtype=http://schema.org/SiteNavigationElement role=navigation aria-label="Main navigation"><a href=/>Home</a> | ||
| 2 | <a href=/#posts>Posts</a> | ||
| 3 | <a href=/#notes>Notes</a> | ||
| 4 | <a href=/#sideprojects class=hob>Side Projects</a> | ||
| 5 | <a href=/vault.html>Vault</a> | ||
| 6 | <a href=https://github.com/mitjafelicijan target=_blank>Code</a> | ||
| 7 | <a href=/mitjafelicijan.pgp.pub.txt target=_blank class=hob>PGP</a> | ||
| 8 | <a href=/curriculum-vitae.html>CV</a> | ||
| 9 | <a href=/index.xml target=_blank class=hob>RSS</a></nav></header><main role=main><article itemtype=http://schema.org/Article><h1 itemtype=headline>State of Web Technologies and Web development in year 2022</h1><p><cap>post</cap>, Oct 6, 2022 on <a href=https://mitjafelicijan.com>Mitja Felicijan's blog</a><div><h2 id=initial-thoughts>Initial thoughts</h2><p><em>This post is a critique on the current state of web development. It is an | ||
| 10 | opinionated post! I will learn more about this in the future, and probably | ||
| 11 | slightly change my mind about some of the things I criticize.</em><p>I have started working on a hobby project about two weeks ago, and I wanted to | ||
| 12 | use that situation as a learning one. Trying new things, new technologies, new | ||
| 13 | tools. I always considered myself to be an adventurous person when it comes to | ||
| 14 | technology. I never shy away from trying new languages, new operating systems | ||
| 15 | etc. Likewise, I find the whole experience satisfying, and it tickles that part | ||
| 16 | of my brain that finds discovery the highest of the mountains to climb.<p>What I always wanted to make was a coding game, that you would play in a browser | ||
| 17 | (just to eliminate building binaries for each operating system) where you would | ||
| 18 | level up your character and go into these scriptable battles. You know, RPG | ||
| 19 | elements.<p>So, the natural way to go would be some sort of SPA (single page application) | ||
| 20 | with basic routing and some state management. Nothing crazy.<blockquote><p><strong>Before we move on</strong>, I have to be transparent. Take my views on this with | ||
| 21 | a grain of salt. I have only scratched the surface with these technologies, | ||
| 22 | and my knowledge is full of gaps. This is my experience using some of these | ||
| 23 | products for the first time or in a limited capacity.</blockquote><p>Having this out of the way, I got myself a fresh pot of coffee and down the | ||
| 24 | rabbit hole I went.<h2 id=giving-react-js-a-spin>Giving React JS a spin</h2><p>I first tried <a href=https://reactjs.org/>React JS</a>. I kind of like it. Furthermore, | ||
| 25 | I have worked with libraries like this in the past and also wrote a couple of | ||
| 26 | them (nothing compared to that level), but I had the basic understanding of what | ||
| 27 | was going on. I rolled up a project quickly and had basic things done in a | ||
| 28 | matter of two hours, which was impressive.<p>I prefer using <a href=https://tailwindcss.com/>Tailwind CSS</a> for my styling | ||
| 29 | pleasures, and integrating that was also a painless experience. It was actually | ||
| 30 | nice to see that some things got better with time. In about 2 minutes I got | ||
| 31 | Tailwind working, and I was able to use classes at my disposal. All that | ||
| 32 | <code>postcss</code> stuff was taken care of by adding a couple of things in config files | ||
| 33 | (all described really well in their documentation).<p>It is not that different from Vue which I have had more encounters with in the | ||
| 34 | past People will probably call me a lunatic for saying this. But you know, it is | ||
| 35 | the truth. Same same, but different. I still believe that using libraries like | ||
| 36 | this is beneficial. I am not a JavaScript purist. They all have their quirks, | ||
| 37 | but at the end of the day, I truly believe it’s worth it.<h2 id=bundlers-and-transpilers>Bundlers and Transpilers</h2><p>I still reject calling <a href=https://www.typescriptlang.org/>Typescript</a> to | ||
| 38 | <a href=https://www.javascript.com/>JavaScript</a> conversion a "compilation process". I | ||
| 39 | call them <a href=https://devopedia.org/transpiler>transpilers</a>, and I don’t care! 😈<p>The first one that I ever used was <a href=https://webpack.js.org/>webpack</a>, and it | ||
| 40 | was an absolute horrific experience. Saying this, it is an absolutely fantastic | ||
| 41 | tool. I felt more like a config editor than actually a programmer. To be fair, | ||
| 42 | I am a huge fan of <a href=https://www.gnu.org/software/make/>make</a>, and you can do as | ||
| 43 | you wish with this information. I like my build systems simple.<p>Also, isn’t it interesting that we need something like | ||
| 44 | <a href=https://babeljs.io/>Babel</a> to make JavaScript code work in a browser that has | ||
| 45 | only one client side scripting available, which is by no accident also | ||
| 46 | JavaScript. Why? I know why it’s needed, but seriously, why.<p>I haven’t used Babel for years now. Or if I did, it was packaged together by | ||
| 47 | some other bundler thingy. Which does not make things better, but at least I | ||
| 48 | didn’t need to worry about it.<p>I really don’t like complicated build systems. I really don’t like abstracting | ||
| 49 | code and making things appear magical. The older I get, the more I appreciate | ||
| 50 | clear and clean, expressive code. No one-liners, if possible.<p>But I have to give props to <a href=https://vitejs.dev/>Vite</a>! This was one of the | ||
| 51 | best developer experiences I have ever had. Granted, it still has magical | ||
| 52 | properties. And yes, it still is a bundler and abstracts things to the nth | ||
| 53 | degree. But at least it didn’t force me to configure 700 lines of JSON. And I | ||
| 54 | know that this makes me a hypocrite. You can’t have it all. Nonetheless, my | ||
| 55 | reasoning here is, if using bundlers is inevitable, then at least they should | ||
| 56 | provide an excellent developer experience.<p>I also noticed that now the catch-all phrase is “blazingly fast” and “lightning | ||
| 57 | fast” and “next generation” and stuff like that. I mean, yeah, tools should get | ||
| 58 | faster with time. But saying that starting a project now takes 2 seconds instead | ||
| 59 | of 20 seconds is something that is a break it or make it kind of a deal is | ||
| 60 | ridiculous. I don’t mind waiting a couple of seconds every couple of days. I | ||
| 61 | also don’t create 700 projects every day, and also who does? This argument has | ||
| 62 | no bite. All I want is a decent reload time (~100ms is more than good enough for | ||
| 63 | me) and that is it.<p>You don’t need to sell me benefits if I only get them when I start a fresh | ||
| 64 | project, and then try to convince me that this is somehow changing the fate of | ||
| 65 | the universe. First of all, it is not. And second, if this is your only argument | ||
| 66 | for your tool, I would advise you to maybe re-focus your efforts to something | ||
| 67 | else. Vite says that startup times are really fast. And if that would be the | ||
| 68 | only thing differentiating it from other tools, I would ignore it. But it has | ||
| 69 | some really compelling features like <a href=https://www.geeksforgeeks.org/reactjs-hot-module-replacement/>Hot Module | ||
| 70 | Replacement</a> that | ||
| 71 | really works well. It was a joy to use.<p>So, I will be definitely using Vite in the future.<h2 id=jam-stack-mach-stack-no-snack>Jam Stack, Mach Stack no snack</h2><p>Let's get a couple of the acronyms out of the way, so we all know what we are | ||
| 72 | talking about:<ul><li>Jam Stack - JavaScript, API and Markup<li>Mach Stack - Microservices, API-first, Cloud-Native SaaS, Headless</ul><p>It is so hard to follow all these new trendy things happening around you, that | ||
| 73 | it makes you have a massive <strong>FOMO</strong> all the time. But on the other hand, you | ||
| 74 | also don’t want to be that old fart that doesn’t move with the times and still | ||
| 75 | writes his trusty jQuery code while listening to Blink 182 All the small things | ||
| 76 | on full blast. It’s a good song, don’t get me wrong, but there are other songs | ||
| 77 | out there.<p>I have to admit. <a href=https://vercel.com/>Vercel</a> is really cool! Love the | ||
| 78 | simplicity of the service. You could compare it to | ||
| 79 | <a href=https://www.netlify.com/>Netlify</a>. I haven’t tried Netlify extensively, but | ||
| 80 | from a couple of experimental deployments I still prefer Vercel. It is much more | ||
| 81 | streamlined, but maybe this is bias in me. I really like Vercel’s Analytics, | ||
| 82 | which give you a <a href=https://web.dev/vitals/>Core Web Vitals report</a> in their | ||
| 83 | admin console. Kind of cool, I’m not going to lie.<p>This whole idea about frontend and backend merging into <a href=https://www.debugbear.com/blog/server-side-rendering>SSR (server-side | ||
| 84 | rendering)</a> looks so good | ||
| 85 | on paper. It almost doesn’t come with any major flaws.<p>But when it comes to the actual implementation, there is much to be desired. | ||
| 86 | I’m going to lump <a href=https://nextjs.org/>Next.js</a> and | ||
| 87 | <a href=https://nuxtjs.org/>Nuxt.js</a> together because they are essentially the same | ||
| 88 | thing, just a different library.<p>Now comes the reality. Mixing backend and frontend in this manner creates this | ||
| 89 | weird mental model where you kind of rely on magical properties of these | ||
| 90 | libraries. You relinquish control over to them for better developer experience. | ||
| 91 | But is that really true? Initially, I was so stoked about it. However, the more | ||
| 92 | I used them, the more I felt uncomfortable. I felt dirty, actually. Maybe this | ||
| 93 | is because I come from old ways of doing things where you control every step of | ||
| 94 | request, and allowing something to hijack it feels like blasphemy.<p>More than that, some pretty significant technical issues arose from this. How do | ||
| 95 | you do JWT token authentication? You put it in <code>api</code> folder and then do some | ||
| 96 | fetching and storing into local state management. But doing this also requires | ||
| 97 | some tinkering with await/async stuff on the React/Vue side of things. And then | ||
| 98 | you need to write middleware for it. And the more I look at it, the more I see | ||
| 99 | that this whole thing was not meant to be used like this, and it all feels and | ||
| 100 | looks like a huge hack.<p>The issue I have with this is that they over-promise and under-deliver. They | ||
| 101 | want to be an all-in-one replacement for everything, and they don’t deliver on | ||
| 102 | this promise. And how could they?! We have to be fair. It is an impossible task.<p>They sell you <a href=https://www.geeksforgeeks.org/overview-of-noops/>NoOps</a>, but | ||
| 103 | when you need to accomplish something a little bit more out of the scope of | ||
| 104 | Hello World, you have to make hacky decisions to make it work. And having a | ||
| 105 | deployment strategy that relies on many moving parts is never a good idea. | ||
| 106 | Abstracting too much is usually a sign of bad architecture.<p>Lately, this has become a huge trend that will for sure bite us in the future. | ||
| 107 | And let’s not get it twisted. By doing this, PaaS providers like | ||
| 108 | <a href=https://aws.amazon.com/>AWS</a>, <a href=https://cloud.google.com/>GCS</a>, etc. obscure | ||
| 109 | their billing, and you end up paying more than you really should. And even if | ||
| 110 | that is not an issue, it comes down to the principle of things. AWS is known for | ||
| 111 | having multiple “currencies“ inside their projects like write operations, read | ||
| 112 | operations, etc. which add up, and it creates this impossible to track billing | ||
| 113 | scheme. It all behaves suspiciously like a pay-to-win game you could find on | ||
| 114 | mobile phones that scams you out of your money.<p>And as far as I am concerned, the most important thing was me not coding the | ||
| 115 | functionalities for the game I want to make. I was battling libraries and cloud | ||
| 116 | providers. How to deploy, what settings are relevant. Bad documentation or | ||
| 117 | multiple versions of achieving the same thing. You are getting bombarded by all | ||
| 118 | this information, and you don’t really have any control over it. | ||
| 119 | Production-ready code becomes a joke, essentially. Especially if you tend to | ||
| 120 | work on that project for a prolonged period of time.<p>All of these options end up creating a fatigue. What to choose, what not to | ||
| 121 | choose. Unnecessary worrying about if the stack will still be deemed worthy in | ||
| 122 | six months. There is elegance in simplicity.<blockquote><p>JavaScript UI frameworks and libraries work in cycles. Every six months or | ||
| 123 | so, a new one pops up, claiming that it has revolutionized UI development. | ||
| 124 | Thousands of developers adopt it into their new projects, blog posts are | ||
| 125 | written, Stack Overflow questions are asked and answered, and then a newer | ||
| 126 | (and even more revolutionary) framework pops up to usurp the throne. | ||
| 127 | — Ian Allen</blockquote><p>And this jab at these libraries and cloud providers is not done out of malice. | ||
| 128 | It is a real concern that I have about them. In my life, I have seen | ||
| 129 | technologies come and go, but the basics always stick around. So surrendering | ||
| 130 | all the power you have to a library or a cloud provider is in my opinion a | ||
| 131 | stupid move.<h2 id=tailwind-css-still-rocks>Tailwind CSS still rocks!</h2><p>You know, many people say negative things about Tailwind. And after a lot of | ||
| 132 | deliberation, I came to the conclusion that Tailwind is good for two types of | ||
| 133 | developers. Tailwind is good for a complete noob or a senior developer. A | ||
| 134 | complete noob doesn’t really care about inner workings of CSS, and a senior | ||
| 135 | developer also doesn’t care about CSS. Well, at least, not anymore. And | ||
| 136 | developers in between usually have the biggest issues with it. Not always of | ||
| 137 | course, but in a lot of cases.<p>I like the creature comforts of Tailwind. Being utility first would make me | ||
| 138 | argue that it is actually more similar to <a href=https://sass-lang.com/>Sass</a> or | ||
| 139 | <a href=https://lesscss.org/>Less</a> than something like Bootstrap. Not technically, but | ||
| 140 | ideologically. After I started using it, I never looked back. I use it every | ||
| 141 | time I need to do something web related.<p>Writing CSS for general things feels like going several steps back. Instead of | ||
| 142 | focusing on what you are actually trying to achieve, you focus on notations like | ||
| 143 | <a href=https://en.bem.info/methodology/css/>BEM</a>, code structuring, optimizing HTML | ||
| 144 | size. Just doing things that make 0.1% difference. You know that saying: Early | ||
| 145 | optimization is the root of all evil. Exactly that.<p>I am also not saying that Tailwind is the cure for everything. Sometimes custom | ||
| 146 | CSS is necessary. But from what I found out in using it for almost two years in | ||
| 147 | a production environment (on a site getting quite a lot of traffic and | ||
| 148 | constantly being changed), I can say without any reservations that Tailwind | ||
| 149 | saved our asses countless times. We would be rewriting CSS all the time without | ||
| 150 | it. And I don’t really think writing CSS is the best way to spend my time.<p>I have also noticed that people who criticize Tailwind the most never actually | ||
| 151 | used it in a real project that has a long lifetime with plenty of changes that | ||
| 152 | will happen in the future.<p>But you know, whatever floats your boat!<h2 id=code-maintainability>Code maintainability</h2><p>Somehow, people also stopped talking about maintenance. If you constantly try to | ||
| 153 | catch the latest and greatest train, you are by that logic always trying new | ||
| 154 | things. Which is a good thing if you want to learn about technologies and try | ||
| 155 | them. But for the production environment, you have to have a stable stack that | ||
| 156 | doesn’t change every 6 months.<p>You can lock dependencies for sure. Nevertheless, the hype train moves along | ||
| 157 | anyway. And the mindset this breeds goes against locking the code. This | ||
| 158 | bleeding-edge rolling release cycle is not helping. That is why enterprise | ||
| 159 | solutions usually look down on these popular stacks and only do bare minimum to | ||
| 160 | appear hip and cool.<p>With that said, I still think that progress is good, but should be taken with a | ||
| 161 | grain of salt. If your project is something that should be built once and then | ||
| 162 | rarely updated, going with the latest stack is a possible way to go. But, if you | ||
| 163 | are working on a project that lasts for years, you should probably approach it | ||
| 164 | with some level of caution. Web development is often times too volatile.<h2 id=web-development-has-a-marketing-issue>Web development has a marketing issue</h2><p>I noticed that almost every project now has this marketing spin put on it. | ||
| 165 | Everything is blazingly fast now. I get it, they are competing for your | ||
| 166 | attention, but what happened to just being truthful and not inflating reality.<p>And in order to appeal to mass market, they leave things out of their marketing | ||
| 167 | materials. These open-source projects are now behaving more and more like | ||
| 168 | companies do. Which is a scary thought on its self.<p>And we are also seeing a rise in a concept of building a company in the open, | ||
| 169 | which is a good thing, don't get me wrong. But when it is using open-source to | ||
| 170 | lure people and then lock them in their ecosystem, there is where I have issues | ||
| 171 | with it.<p>This might be because I have been using GNU/Linux for 20 years now and have been | ||
| 172 | so beholden for my success to open-source that I see issues when open-source is | ||
| 173 | being used to trick people into a false sense of security that these projects | ||
| 174 | are built in the spirit of open-source. Because there is a difference. They are | ||
| 175 | NOT! They have a really specific goal in mind. And the open-source is being used | ||
| 176 | as a delivery system. Which is in my opinion disgusting!<h2 id=conclusion>Conclusion</h2><p>I will end my post with this. Web development is running now in circles. People | ||
| 177 | are discovering <a href=https://www.tutorialspoint.com/remote-procedure-call-rpc>RPC</a> | ||
| 178 | now and this is the now the next big thing. <a href=https://graphql.org/>GraphQL</a> is | ||
| 179 | so passé. And I am so tired of it all. Of blazingly fast libraries, of all these | ||
| 180 | new technologies that are actually just a remake of old ones. Of just the | ||
| 181 | general spirit of the web. I will just use what I already know. Which worked 10 | ||
| 182 | years ago and will work 10 years after this. I will adopt a couple of little | ||
| 183 | tools like Vite. But I will not waste my time on this anymore.<p>It was a good exercise to get in touch with what’s new now. Nothing really | ||
| 184 | changed that much. FOMO is now cured! Now I have to get my ass back to actually | ||
| 185 | code and make the project that I wanted to make in the first place.</div></article></main><section><hr><h2>Posts from blogs I follow around the net</h2><ul><li><a href=https://utcc.utoronto.ca/~cks/space/blog/linux/NFSv4ServerLockClients target=_blank rel=noopener>Finding which NFSv4 client owns a lock on a Linux NFS(v4) server</a> — <a href=https://utcc.utoronto.ca/~cks/space/blog/>Chris's Wiki :: blog</a><div>A while back I wrote an entry about finding which NFS client owns | ||
| 186 | a lock on a Linux NFS server, which turned | ||
| 187 | out to be specific to NFS v3 (which I really should have seen coming, | ||
| 188 | since it involved NLM and lockd). Finding the NFS v4 client that | ||
| 189 | owns a lock is, depending on your perspective, either simpl…<li><a href=http://www.landley.net/notes-2023.html#28-10-2023 target=_blank rel=noopener>October 28, 2023</a> — <a href=http://www.landley.net/notes-2023.html>Rob Landley's Blog Thing for 2023</a><div>Oh good grief, two of my least favorite licensing people, Larry Rosen | ||
| 190 | and Bradley Kuhn, are interacting on the OSI's license-discuss | ||
| 191 | list where the're doing | ||
| 192 | bad computer history and insisting that a guy Larry Rosen | ||
| 193 | coincidentally interviewed for a book years ago is clearly the origin of | ||
| 194 | somethin…<li><a href="http://offbeatpursuit.com:80/blog/?id=25" target=_blank rel=noopener>A fix by any other name</a> — <a href=http://offbeatpursuit.com:80/blog/>WLOG - blog</a><div>tags: | ||
| 195 | i2c, plan9 | ||
| 196 | Another month, another file system. | ||
| 197 | Well, if you can’t fix it in software, fix it in hardware (looking at | ||
| 198 | you, bme680, we’re not | ||
| 199 | done yet). The show must go on, as they say, and I would like my | ||
| 200 | experiments to go on. | ||
| 201 | So a “new” addition to the environmental sensor family connected to | ||
| 202 | the h…<li><a href=https://mirzapandzo.com/next-image-url-parameter-is-valid-but-upstream-response-is-invalid target=_blank rel=noopener>Next/Image "url" parameter is valid but upstream response is invalid</a> — <a href=https://mirzapandzo.com/>Mirza Pandzo's Blog</a><div>Getting "url" parameter is valid but upstream response is invalid error with Next/Image on WSL2<li><a href=https://drewdevault.com/2023/10/13/Going-off-script.html target=_blank rel=noopener>Going off-script</a> — <a href=https://drewdevault.com>Drew DeVault's blog</a><div>There is a phenomenon in society which I find quite bizarre. Upon our entry to | ||
| 203 | this mortal coil, we are endowed with self-awareness, agency, and free will. | ||
| 204 | Each of the 8 billion members of this human race represents a unique person, a | ||
| 205 | unique worldview, and a unique agency. Yet, many of us have the sam…<li><a href=https://szymonkaliski.com/writing/2023-10-02-building-a-diy-pen-plotter/ target=_blank rel=noopener>Building a DIY Pen Plotter</a> — <a href=http://github.com/dylang/node-rss>Szymon Kaliski</a><div>This article documents my learnings from designing and building a DIY Pen Plotter during the summer of 2023. | ||
| 206 | My ultimate goal is to build my…<li><a href=https://neil.computer/notes/chart-of-accounts-for-startups-and-saas-companies/ target=_blank rel=noopener>Chart of Accounts for Startups and SaaS Companies</a> — <a href=https://neil.computer/>Neil Panchal</a><div>Accounting is fundamental to starting a business. You need to have a basic understanding of accounting principles and essential bookkeeping. I had to learn it. There was no choice. For filing taxes, your CPA is going to ask you for an Income Statement (also known as P/L statement). If<li><a href=https://journal.valeriansaliou.name/deploy-a-nomad-cluster-on-alpine-linux-with-vultr/ target=_blank rel=noopener>Deploy a Nomad Cluster on Alpine Linux with Vultr</a> — <a href=https://journal.valeriansaliou.name/>Valerian Saliou</a><div>After spending countless hours trying to understand how to deploy my apps on Kubernetes for the first time to host Mirage, an AI API service that I run, I ended up making myself a promise that the next app I work on would be using a more productive & simpler<li><a href=https://jcs.org/2023/10/25/wifi_da target=_blank rel=noopener>BlueSCSI Wi-Fi Desk Accessory 1.0 Released</a> — <a href=https://jcs.org/>joshua stein</a><div>BlueSCSI Wi-Fi Desk Accessory | ||
| 207 | 1.0 has been released: | ||
| 208 | wifi_da-1.0.sit | ||
| 209 | (StuffIt 3 archive) | ||
| 210 | SHA256: ccfc9d27dd5da7412d10cef73b81119a1fec3848e4d1d88ff652a07ffdc6a69aSHA1: ff124972f202ceda6d7fa4788110a67ccda6a13a | ||
| 211 | This is the initial public release of my BlueSCSI Wi-Fi Desk Accessory for | ||
| 212 | classic MacOS.<li><a href=https://michael.stapelberg.ch/posts/2023-10-25-my-all-flash-zfs-network-storage-build/ target=_blank rel=noopener>My 2023 all-flash ZFS NAS (Network Storage) build</a> — <a href=https://michael.stapelberg.ch/>Michael Stapelbergs Website</a><div>For over 10 years now, I run two self-built NAS (Network Storage) devices which serve media (currently via Jellyfin) and run daily backups of all my PCs and servers. | ||
| 213 | In this article, I describe my goals, which hardware I picked for my new build (and why) and how I set it up. | ||
| 214 | Design Goals | ||
| 215 | I use my netw…</ul><p>Generated with <a href=https://git.sr.ht/~sircmpwn/openring target=_blank rel=noopener>openring</a>.</section><footer><hr><p><big><strong>Want to comment or have something to add?</strong></big><p>You can write me an email | ||
| 216 | at <a href=mailto:mitja.felicijan@gmail.com>mitja.felicijan@gmail.com</a> or | ||
| 217 | catch up with me <a href=https://telegram.me/mitjafelicijan target=_blank>on Telegram</a>.<hr><p>This website does not track you. Content is made available under the <a href=https://creativecommons.org/licenses/by/4.0/ target=_blank rel=noreferrer>CC BY 4.0 license</a> unless | ||
| 218 | specified otherwise. Blog is also available as <a href=/index.xml target=_blank>RSS feed</a>.</footer><script> | ||
| 219 | window.va = window.va || function () { (window.vaq = window.vaq || []).push(arguments); }; | ||
| 220 | </script><script defer src=/_vercel/insights/script.js></script> \ No newline at end of file | ||
