Maybe Go optimizing for serverless with reduced init time?
259 karma · joined February 15, 2021
This way I would blame it on my connection, not the other person, who is actually causing it. In a team setting, it goes like "Oh, so we're all hearing our own echoes. We should quit and try again" If there is one person acting as reflector with the right delay (echo generator) for everyone else, that could work, in theory.
In general, if we use any async APIs in your JS that modify shared state the order will consist of an interleaving of all events, including from timers (macrotasks), DOM events (macrotasks), resolved and finalized promises (microtasks) and DOM APIs like IntersectionObserver (microtask), IDB et al, along with synchronous calls (including any recursive calls) so looking at things in order does not mean anything in a complex UI with lots of interleaved events if you cannot filter by a named action (the action that caused a certain chain of events, which otherwise will be displayed intermingled with all other events from other actions) you can't really follow the data and control flow of your app. So order only matters in debugging and comprehension if you can filter by action. Another thing we should care about is domain driven design and domain aggregates for your state store to make sure that only one aggregate root is responsible for a given part of state. If more than one chain of events (more than one named action) modify the same part of state then trying to comprehend the relationship between state and action becomes too complicated and you lose consistency guarantee as a result (overlapping and interleaving reads and writes) unless you introduce some form of MVCC (multi-version concurrency control)
I've built tools to visualize how complex highly concurrent UIs work under the hood and found the principles and methods to be directly applicable to analysis of microservices based apps.
"Bitcoin Is A Waste of Time (and Resources)"
What Bitcoin has done is that it taught people they can come together in a sustained flash mob (like an on-the-fly hedge fund operation) and manipulate the price of speculative assets by creating artificial short-term pump-n-dump type demand. Bitcoin has trained our collective neural network to do this.
The huddled masses can take their new superpower and apply it to stock, crypto, commodities on the commodity exchange, and all kinds of speculative assets, especially the virtual kind.
It's taken a gambling-friendly society with feverish lust for winning (think for-profit fantasy sports, online poker, day trading, Vegas et al) and turned us into a giant decentralized casino.
I had to switch off Time Machine on MacbookHD (main disk) by excluding it from the Time Machine preferences, and reinstall the OS to erase the previous copies it had made, all ~400GB of it (on my 499GB disk)... As the user, I was not asked for permission to allow Time Machine to use up to 80% of available disk capacity. It was backing up so many copies of the data until I noticed I had left only 8GB of free space and I only noticed because Quicktime screen recording started crashing due to insufficient disk space. Basically, the decision by Apple is to use up to 80% of the available disk space to save copies of the data on that disk without user permission, and because it checks and reconciles the amount it's using every so often you can easily end up with 0% free capacity if you e.g. record a lot of videos in between.
What I did not say: the entire system sucks.
What you claim that I said: the entire system sucks.
That's the maze of the human psyche for you.