Yes and I've used Plex mobile app for years. Completely frustrating experience every time I need to use the download functionality.

I couldn't agree more and I've been in this same situation. When your codebase is hundreds of thousands of lines of JavaScript suddenly promises with async await make a lot of sense.

Await is nice, but even with promises, I'd settle with people using them correcly: return something in the promise to the next one can use it without nesting.

But people use promises... and keep nesting.

Even back in early Node days we figured this out with ideas/libs like async.waterfall, which let you turn nesting into a serial flow:

    async.waterfall([function(callback) { callback(null, 'one', 'two'); },
                     function(arg1, arg2, callback) { callback(null, 'three'); },
                     function(arg1, callback) { callback(null, 'done'); }]);

Thus you don't need to make things like 'one' and 'two' into scoped variables that require nesting the second function into the first one so it can see them, and you can split those functions out of being inline lambdas.

Or early Promise libs like coolaj86's futures which included a sequence, letting you do the same sort of thing:

    var seq  = Futures.sequence();
    
    seq
    .then(function(next) { setupContextObj(next, obj)})
    .then(retrieveMD)
    ...
    .then(postUrlDataToS3)
    ...

while also being able to make nice little future() objects you could return from functions and pass around. To be fair it's still JS and lots of third party code needed regular old callbacks so it was still easy to get excessive levels of nesting of various things that leave you with function-closing sequences like });}});return future;} or });}}).end(buf);} that could make a Lisper blush.

These days it's quite a bit nicer having native Promises, a better community-wide understanding of how to use them, but also the syntactic sugar of async/await improves over the waterfall/sequence/.then&.catch chaining styles (especially when it comes to modifications where you want to use data from previous stages of the chain in later stages).

The ResultAsync class in neverthrow has chaining as well as splitting on ok/error - I find this really nice because you can also do away with exceptions at the same time.

I feel like fp-ts is even more powerful for this - provided you (and your entire team / every new hire) can navigate the steep learning curve which tbh defeated me when I tried to learn it in a couple of days last week

I'd argue (from memory!) that there are solid edge cases for nesting promises .. probably all scope-related, where multiple async operations are required for a result that would otherwise require scope-leak / pollution.

Great advise! I wanted to add a bit more to it. As you age the number of novel experiences and "space" for those experiences in your brain decreases. So the first 20 years of your life you accumulated a lot of new experiences while your brain was growing an expanding. For this reason it feels like you lived in regular time. Your final 20 years will mostly be nothing new and what is new will largely include a base that is shared based on past experiences. This is why as you get older time moves faster.

If I had a dollar for every proof of concept that I've made that's still in production today serving users I would probably have like 15 dollars.

Prolific!

Me and all my friends have used signal for years. What do you mean you gave up? I've never had any issues and it beats the hell out of text. Like I said, I communicate with probably 15 people at least daily consistently via IM and 3 of those are text the rest signal.

My entire family, most of my friends... I hardly ever get a regular SMS, usually it's spam or a company message.

Granted I did a little bit of work to convince them, but "you can use it on your computer and do video calls with your phone number" was good enough, even if vaguely inaccurate. It's much more functional than SMS.

But that's also in the US, I think other apps are more popular plenty of places which are just as much better than SMS anyway. Signal I think has good adoption in the US because the competitor was so terrible.

What does your comment even mean? A lot of people get angry about a lot of things but the solution is what exactly? Based on your statement I would assume your suggestion is "they shouldn't be free to have their own rules and do what they want" because...?

>Based on your statement I would assume your suggestion is "they shouldn't be free to have their own rules and do what they want" because...?

That question is better asked of PradeetPatel, the person who wants to figure out how to stop people from using a decentralized system.

The end of eternity by Issac Asimov touches on this. I believe the analogy is that of a bird being left behind by earth as it flies through the air because earth is moving through space. So as you travel through time you move in time with whatever it is you're traveling on, I guess is the argument the book makes.

My $10k Toyota Corolla has android auto. What happened?

Luxury automakers have often been more restrictive and exclusive about features, mostly because they can be. BMW was known for their annual subscription CarPlay option which required ongoing payments for what was clearly a one-time software update. Porsche likely has even more brand loyalty driven by other elements of their cars, so I’m not surprised that they’d choose to negotiate some exclusivity with Apple CarPlay or otherwise just not bother adding Android Auto until 2022.

You're spot on about the 5 year difference. I never thought I would see my shit box I bought a few years ago for more than I ever thought it was worth triple in value. It's literally the difference of 5 years as you said. I want to be part of the pray for the collapse team but I know good honest people who would be devastated by it. People who are just victims of the system.