It’s reinforcement learning over decades
In accordance with this view, I think project architecture should be approached with an emphasis around how much state is necessary for it to run. This is why simulations like say someone making a game or simcity with like relatively independent entities that map to something in real life use OOP. If you're writing a service doing requests, you want as minimal state as possible. Singletons are state. Initialized/non-static objects are state. The smaller amount you have the easier it is to reason about the system.
As I write this however, I worry a little that my view is overly simplistic, or maybe applicable only to domains that I have worked in. If anyone wouldn't mind poking holes in this argument or offering examples I would appreciate it.
It’s obviously blog content designed to promote your product, hosted on the company’s product website. I don’t see how the FYI is unfair.
I added it because the content was valuable but HN can be finicky about blog posts from companies advertising their own products. Trying to get ahead of indignant dismissals.
I'm not usually so insulting--but as a father of two, if my 3 year old and 1.5 year old could only read one book, it would have to be "Oh, the places you'll go" by Dr. Suess.
Sorry to stomp on Das Kapital and its ilk, but if you get only one book, I can't imagine a better first message to convey than the endless possibilities inherent in each of us.
The world is your oyster! Even if you're old and have wasted most of what you were given. Especially today, in some of the most amazing times that have ever existed (even if you didn't draw the long straw). Today is SO much better than most of history.
Latest experiment was one teaspoon of fermented green squash daily, seemed to work out okay for 5 days or so, then depression came back, BUT I could smell it in my armpits 1-2 days before the thoughts were back.
https://gutsense.org has a lot about fiber - the only fiber I can use seems to be animal based, like eggwhites
"Peer-to-peer calls require more bandwidth than calls routed through a server and are thus not suited for a large number of participants. In the future, we plan to also develop calls via a forwarding server to solve resource issues on the client side and to allow for calls with more participants."
User B: Is user C's stream dead for anyone else? User A: I see user C. User C: Sorry, what? I'm right here.
Honestly, other than a 1-1 chat, I can't think of a situation where p2p is worthwhile. Even then, it's almost always better to use an SFU.