> Unfortunately (to me) the focus on ease-of-use has meant that OpenTelemetry concepts are structured in such a way to preclude even the possibility of a very efficient implementation
Looks like Opentelemetry (at least its precedessor, OpenCensus) is originated from Google. From OpenCensus website (https://opencensus.io/):
> OpenCensus and OpenTracing have merged to form OpenTelemetry
> OpenCensus originates from Google, where a set of libraries called Census are used to automatically capture traces and metrics from services.
Original internal Google tracing system was probably designed for scale. And opentelemetry's design is probably based on that internal system.
So, maybe poor performance is just an implementations issue.
OpenCensus bears no resemblance whatsoever to Google Census, except for the name. Census at Google is wired tight as hell. Any time it showed up on the first page of fleet-wide profiles it would get hammered back down. At the same time it also has more capabilities than its open source successors. Unfortunately, nothing has ever been published about it.
Domain experts may lie, they might be sure that idea will never work but still propose it in order to increase company valuation, get funding, etc.
Example: self-driving cars. Probably, experts that work in this field are confident that self-driving cars are impossible even 100 years in future, but working on self-driving cars gives them money.
Class diagrams, the most used of UML diagram types, are not exactly for system design, they're too low-level, and yes, "Round-trip engineering" that generates code from class diagrams (and class diagrams from code) was advertised as important feature of advanced UML tools.
Converting classes into UML diagrams can be usefull regardless if you classify UML as obsolete or not. It's a nice why to understand how a given class or interface is used throughout.
What are key differences between Hypercard and "Rapid Application Development", "Visual Programming" tools like Visual Basic?
Visual Basic is not dead, it's still in development (although in .NET form, which might have steeper learning curve). It was highly hyped in past too, but now it has only niche uses, and it's used not as "bicycle for mind", instead mostly for handling bureaucracy in large corporations.
I'm sure "calculator" example will be very similar in Visual Basic.
There are lots of no-code, low-code tools but they almost always fail and become discontinued quickly. Only spreadsheets thrive out of these.
There should be other reasons for that, not "corporations don't want users to program their computers".
Replacing iPhone battery feels like reassembling a mechanical watch. It isn’t soldered, but it’s glued in weird way requiring applying heat. To change battery, you have to disconnect 4-5 tiniest connectors, looking like LPT for fleas, extremely fragile.
Changing the battery is an operation that you likely only do once in the phone's lifetime. It doesn't make sense to have design constraints just to make that operation super-quick.
Currently it takes an hour at most to do at any repair shop. It's good enough. What matters is that it's possible for a reasonable price.
Well yeah, I've replaced the battery and the button on my iPhone 4s myself back in the day. Handling those tiny connectors feels like you're performing an open heart surgery if you're not doing it for a living. But let's be honest, personal computing devices are going to get smaller and more intricate in the next decades. The days of replacing the battery yourself are long gone.
Topmost bar still consists of lots of unused space with clock in the center — a design decision surely copied from old mobile phones. Too much of screen space is wasted, in the most "expensive" area, where "Rule of the infinite edges" of Fitts's law applies.
And what would you put there? I do like some sway/i3-like bar with many stats, but I don’t miss that on gnome, it is sort of a feel-good thing there for me.
I don't like how mouse scrolling works in Firefox. I can't determine exact details what's wrong (jitter? inertia? delay?), but it feels subtly broken, and after a while it makes me nervous.
Multimedia died in late 90s. No one no longer wanted to read text in tiny unscrollable unsearchable rectangle with "real book-like" page flipping animation and colorful textured background. All these things looked garish and vulgar long before "web 2.0" and mass javascriptization.
Flash was only good for games, short animated movies and tolerable for videos and audio (before web video standards).
Looks like Opentelemetry (at least its precedessor, OpenCensus) is originated from Google. From OpenCensus website (https://opencensus.io/):
> OpenCensus and OpenTracing have merged to form OpenTelemetry
> OpenCensus originates from Google, where a set of libraries called Census are used to automatically capture traces and metrics from services.
Original internal Google tracing system was probably designed for scale. And opentelemetry's design is probably based on that internal system.
So, maybe poor performance is just an implementations issue.