Right now it's just a throttling mechanism. Everything has been paid by the investors. You have to wait until the bubble pops for it to become the meaningful value.

I'm still interested learning Rust and in how I would feel about its "read-write lock" approach after working for some time with it.

Yes, but these are relatively rare issues in millions of code-lines. Is it the most cost effective way to deal with those by pivoting the entire code structure? The answer might be similar to the one about FP. Of course, this might be just my perspective of a person working not in FAANG.

I would say in the business apps world not many people would even understand if there is some problem. GC doesn't care. When a "user" would loose its connection to the root, the entire chain (user-comment-user) would be put into garbage. Weak references and other stuff are used extremely rarely.

For example: www.bartoszsypytkowski.com/is-rust-a-go...

User has Comments. A comment has an Author. An author is a user. Linked lists are everywhere. Because of that you start using Arc and doing tons of excess memory operations. At least that's my current understanding as I just literally started with Rust.

I've started looking into Rust and first articles I've found tell how difficult it is to implement Linked Lists and similarities of typical business logic code to such structures.

Not giving up at which price?

Thanks, I've watched 20 minutes. Redux awaking thousands of connects of every change is a thing.

Yeah, kinda either we buy Oracle for a couple of $ millions or we are broke.

Speaking out load, I am not sure about the enterprise pricing. My manager would just say we don't have the budget or couldn't get an approve from the upper management and we would continue to use what is free and glue with custom code.

The flame is filled with RGB(254,254,254) not because it is white, but because the colors are compressed to SRD and you have sacrificed the range to be able to see a bit of candle. In HDR the flame would have more gradient and simultaneously the candle would have more shadow details.

SDR also skews the colors because of how you encode into limited range. So, on HDR some colors would have a slightly different tint. And when the movie is graded to 1000 nits, no one forbids you to ask the TV to tone map it to 300 nits if you have an eye strain. Reverse is impossible.

Only 300 nits means they didn't actually produce a real HDR master, but just pushed some lights to 300 and they are still fully white filled while the rest of the image is flat. And no additional details in shadows as well.

HDR is not about brighter. It's about showing more details on the screen. In shadows as well.

Thanks a lot for explanation!

The question would be if the readers would understand why it is here and how it works.

Yes, a controller component doing queries and deciding what to show + several children views. But for the docs I guess adding a condition to the Suspense would be enough, so you don't look at an empty screen on the first search.

I mean, SearchResults as an encapsulated component shows its state. No search results is one of them. It could look different depending on the design. So, now you have to extract "no results" into another component and lift the logic up. Not critical of course, just to keep in mind.