Pretty much, they are fundamentally both RPC flavors, so it's impossible for them to have different properties beyond more or less convenient tooling. It's always jarring to see those heated GraphQL vs REST APIs (as implemented in practice) vs gRPC discussions as if they are as different as, say, client-side CRDTs.
As a yet another filthy Russian, I don't understand all this eagerness to give people "traitor" (enemy of the people, 5th column and so on) labels. Especially since this is pretty much the favorite communist/putinist activity. This is not a healthy mindset. At some point we'll have to admit different people might have different opinions on running the country.
Java / OpenJDK never used semver in the first place. Also, large projects like Java have entire layers of different APIs, whose compatibility guaranties can't really be described with a single number, no matter what versioning scheme they use.
Manipulative much? I don't hate you (well, so far), you aren't being attacked, I'm just noting what a few informed people here don't like about your video. No, they aren't trolls. And, yes, everyone has different level of tolerance to exaggerations, of course.
Have you seen the video? The author even goes as far as suggesting the technique might useful for (generating?) entire operating systems at https://www.youtube.com/watch?v=udPY5rQVoW0&t=853s. That's just wild.
> You don't remember when GTX 1080 Tis could be had on eBay for as cheap as $400-$450??
That's slightly above half of its retail price (when it was new) and roughly in the same ballpark as RTX 2070 MSRP. Is this really "dirt cheap"? Do you expect video cards to never depreciate then?
More to the point, I don't remember the market being saturated with used video cards in way that could put a dent in retail prices. They always seem to sell at comparable performance/$ ratio to new cards. I'm genuinely curious if I missed any trends.
Well, they don't — AMD drivers for new hardware famously take a few kernel releases to stabilize. (G)GP specifically noted their stability problem started only 5 months ago, which means at least that issue is not really systemic. The real differentiator here is handling of existing complaints: Linux has mailing lists, Mesa has a normal open for everyone bug tracker, while Nvidia has a user support forum, which they mostly ignore.
> If the only differing bits were the portability framework, this would just be a matter of adding missing support. But it isn't — the FreeBSD object file Nvidia publishes lacks the internal symbols used by the Linux driver.
In fact it is. For Linux and FreeBSD Nvidia distributes exactly the same blob for compilation into nvidia.ko; the blobs for nvidia-modeset.ko are slightly different. (Don't take my word for it, download both drivers and compare kernel/nvidia/nv-kernel.o_binary with src/nvidia/nv-kernel.o.) Nothing is locked in the closed source part.
Native Linux stuff is not at all native for FreeBSD. If Nvidia suddenly decides to open their driver (to merge it into Linux), FreeBSD and Solaris support will be the first thing thrown out.
You might want to provide the source for this. (The phrase is not directly googlable.)