> Each inbound WebSocket connection runs your program in a dedicated process.
Connections are isolated by process.
I see you and 10,900 other "software developers" get the point of WebSocket. It's especially "impressive" when you written the whole thing in Go and could have used goroutines and channels, which could easily handle hundreds of thousand of connections (maybe millions). Terrible design!
For a long time I thought every software developer must be smart, but a lot of them don't see the big picture very often.
Why this bothers me so much? You created something that a lot of developers think is good enough, so less innovation will happen and more and more slow websites will appear because of tech like this...
Stupid shit like this is the reason I moved everything to my own Nextcloud instance. It's completely free, open source and surprisingly have a BETTER user interface than Dropbox. Rclone can sync to the WebDav interface.
The article has 9 subchapters. It could have 2 or 3 by saying "Install GitLab", but maybe GitLab can't run on a Raspberry? If you are not restricted to a Pi however, try GitLab and you are done with all the steps described in this article.
This is very good explanation, but only explains what happens with the files, nothing about the graph what is a git repository. This talk helped me tremendously to finally understand what's going on in git: https://www.youtube.com/watch?v=1ffBJ4sVUb4
It is one of the best talks about git for beginners with an unfortunate title :D
For me personally, the only reason for doing something is always that if it is useful for others (solves a problem, creates real value in the world) it worth doing. Extra points if I could make money with it :). If not, I was not able to continue working on it.
Depression is a serious mental illness, in which 7-10% of the patients die (because of suicide). Not kidding. It is caused by the imbalance of serotonin and readrenalin neurotransmitters.
Depression is NOT a synonym for "bad mood" or "being tired", it's much more serious than that.
And you can write your own. I use i3wm and was not satisfied how it handles Window Titles by default, so I wrote my own daemon for renaming windows automatically, which makes a huge difference for me: https://github.com/kissgyorgy/i3-window-title-changer
I don't understand how is this a question? Do you really want to learn it because it seems to me that you are trying to find a bogus reason not to... no offense, but if you don't like it, you shouldn't pursue this career, otherwise the simple answer is there is huge demand and good salary for Web Developers.
They are enabled by default and you can't simply just disable, some of them will still start. You have to mask them in order to block them entirely. Also it doesn't matter if you have ntpd running, systemd-timesyncd still started for us...
That's starting to be not true. In the beginning, there was just systemd, now starting with bionic, it's components are tied together so much that's it's hard to turn them off or not use it. I liked systemd a lot, but started to understand the complaints when we had a lot of problems with systemd-timesync, systemd-resolved and co...
I know most of these things in detail, I can understand them and use most of them daily. I know NOTHING about JavaScript at all. It's ok, you work on frontend, I'm on backend.
This is NOT Open Source in a way you think it is yet, because the repo doesn't have a LICENSE attached to it, so the owner own every right and you are not allowed to sell it or do whatever you want with it.
I see you and 10,900 other "software developers" get the point of WebSocket. It's especially "impressive" when you written the whole thing in Go and could have used goroutines and channels, which could easily handle hundreds of thousand of connections (maybe millions). Terrible design!
For a long time I thought every software developer must be smart, but a lot of them don't see the big picture very often.
Why this bothers me so much? You created something that a lot of developers think is good enough, so less innovation will happen and more and more slow websites will appear because of tech like this...