Honestly Nebula always felt off to me because of this marketing. They never sold it as a place where creators had a more equitable share, or where they had more creative freedom and control (which seem to be true), but they used the idea that they were "fighting the man" by going at it alone. It always felt like a half truth which, turns out, it is.

Also the price always felt too good to be true to me so I always suspected some sort of investment from somewhere to create a loss leader. Though the jury's still out on that. But having worked on video streaming online myself I know first hand how expensive it can get so I wonder how profitable the company is.

I do agree that logging and spans are very similar, but I disagree that logs are just spans because they aren't exactly the same.

I also agree that you can collect all metrics from spans and, in fact, it might be a better way to tackle it. But it's just not feasible to do so monetarily so you do need to have some sort of collection step closer to the metric producers.

What I do agree with is that the terminology and the implementation of OTEL's SDK is incredibly confusing and hard to implement/keep up to date. I spent way too many hours of my career struggling with conflicting versions of OTEL so I know the pain and I desperately wish they would at least take to heart the idea of separating implementation from API.

You wouldn't happen to have an example of what you're doing laying around would you? I'd be genuinely curious to try stuff like that out.

Either the person quits.

Or the person resigns to giving mediocre output and coasts.

Neither is good for the business and yet people keep pushing workers (not even just in tech) into that position to the point it's now a cliché.

While Legoland still exists, it's now a license and the parks owned by a separate company

Because of that, they quickly reach for the escape hatch that useEffect provides everytime they need to change something.

I genuinely don't know how to help my fellow team members grasp the basic concept of components better. It doesn't seem, to me, like it's something everyone gets eventually. I've actually seen far too many developers who just don't seem to get there even after long months working with component libraries.

As a side note: I don't get all the love for class components. All I remember from using them were the endless bugs because we somehow missed something on willUpdateProps or whatever. Class components could have worked but they always felt like the different life cycle methods were all cobbled together with little overall consistency (see Vue for an example of life cycle hooks done better, even if I have plenty of other gripes with Vue's design)

And don't forget the SUVs

https://www.youtube.com/watch?v=JtUAAXe_0VI

Not saying you're doing this but it was the first threat scenario that came to mind and it's not even something particularly uncommon in the browser extension world.