aboutsummaryrefslogtreecommitdiff
path: root/public/my-love-and-hate-relationship-with-nodejs.html
diff options
context:
space:
mode:
authorMitja Felicijan <mitja.felicijan@gmail.com>2023-10-31 11:05:28 +0100
committerMitja Felicijan <mitja.felicijan@gmail.com>2023-10-31 11:05:28 +0100
commitc9d51c7de97f8af318fa7eb866c138a69676e1d7 (patch)
tree18f51726efa1ea45366d4e0f01a99888cf51d995 /public/my-love-and-hate-relationship-with-nodejs.html
parent6ee7245390cdf4e19fef82c2423ba325adea4114 (diff)
downloadmitjafelicijan.com-c9d51c7de97f8af318fa7eb866c138a69676e1d7.tar.gz
Made a bunch of content fixes
Diffstat (limited to 'public/my-love-and-hate-relationship-with-nodejs.html')
-rwxr-xr-xpublic/my-love-and-hate-relationship-with-nodejs.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/public/my-love-and-hate-relationship-with-nodejs.html b/public/my-love-and-hate-relationship-with-nodejs.html
index de525a7..55a3382 100755
--- a/public/my-love-and-hate-relationship-with-nodejs.html
+++ b/public/my-love-and-hate-relationship-with-nodejs.html
@@ -72,7 +72,7 @@ application. And you don't get this in <strong>marketing material</strong> for E
72etc. They never tell you this. Making Node.js scale on infrastructure or in 72etc. They never tell you this. Making Node.js scale on infrastructure or in
73codebase is really <strong>more of an art than a science</strong>. And just like with the 73codebase is really <strong>more of an art than a science</strong>. And just like with the
74whole JavaScript ecosystem:<ul><li>impossible to master,<li>half of your time you work on your tooling,<li>just accept transpilers that convert one code into another (holly smokes),<li>error handling is a joke,<li>standards? What standards?</ul><p>But on the other hand. As I did, you will also learn to love it. Learn to use it 74whole JavaScript ecosystem:<ul><li>impossible to master,<li>half of your time you work on your tooling,<li>just accept transpilers that convert one code into another (holly smokes),<li>error handling is a joke,<li>standards? What standards?</ul><p>But on the other hand. As I did, you will also learn to love it. Learn to use it
75quickly and do impossible things in crazy limited time.<p>I hate to admit it. But I love Node.js. Dammit, I love it :)<p>2023 Update: I hate Node.js!</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 75quickly and do impossible things in crazy limited time.<p>I hate to admit it. But I love Node.js. Dammit, I love it :)<p><strong>2023 Update</strong>: I hate Node.js!</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
76a lock on a Linux NFS server, which turned 76a lock on a Linux NFS server, which turned
77out to be specific to NFS v3 (which I really should have seen coming, 77out to be specific to NFS v3 (which I really should have seen coming,
78since it involved NLM and lockd). Finding the NFS v4 client that 78since it involved NLM and lockd). Finding the NFS v4 client that