> 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.
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.
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.
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.
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).
They also had HomeSite (originally by Allaire, then bought by Macromedia), which is also a text editor. However, it seems that they abandoned it right after acquisition of Macromedia.
> When containing images and image sequences encoded in a particular format (e.g. HEVC or AVC) its use becomes subject to the licensing of patents on the coding format.
But font antialiasing was available starting from Windows 95 with Microsoft Plus!. I don't remember for sure, but I doubt browsers were exception and didn't use system-wide font antialiasing.
Is this website about internal combustion engine fuels? Or it's just an aggregator of all american newspapers? I thought HN is something about software and programming.
Looks like a crutch for poor managery practices which are very common in today's IT companies: management stubbornly wants to get rid of ancient technology of writing and to return to even earlier oral-only society.
As in oral-only societies, information becomes stored only in minds. After video meetings, no recorded information remains, so let's add recording of videos. Recorded videos are unsearchable and poorly seekable, so let's add voice recognition.
This is ridiculous: supporting desire of managers to return to prehistoric times and trying to fix it with frigging cutting-edge deep learning. I would not say "trusted by great teams".
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.