23,650 karma · joined October 15, 2013
From my side of the world (Europe), this whole "Mercator projection is associated with colonialism" drama seems to have originated a couple of years ago in the US and was mostly amplified by artificial social media outrage.
Ancient mediterranean maps often were South up, as well as maps of Islamic cartoghraphers.
There were also Roman road maps which were entirely schematic, more like our modern public transport maps (e.g. such maps only cared about how locations were connected by roads and their distances, but not about any geographical mapping)
I doubt that any of us will still be alive at the time when GTA 7 releases - at least when looking at the trajectory of GTA release dates ;)
I wonder how many examples there actually are of the people in the trenches doing the actual work getting a 'fat bonus'.
E.g. the idea that unionization might not be a bad idea usually starts with teams not getting any bonuses after they created a highly successful game, and instead the company preventing such 'problems' by firing most of the team right before a game ships.
At least in Germany (and both former East and West) it certainly isn't in use since at least the 1950s (and probably much earlier), but instead a projection type that maps land masses closer to their actual relative sizes. Mercator is extremely rare and only used in very specialized professional maps (e.g. for navigation), but certainly not as the popular map projection in education.
Also don't schools use physical globes anymore?
This whole drama sounds like it's about a century late to the party tbh.
Lol, Diablo 2 was the last good Diablo (it has a great remaster now btw).
From what I've seen, success and following decline are directly related. Once a studio becomes successful, they start to attract the sort of people (especially in leading positions) who are great at selling themselves but not much else, and the studio founders haven't learned yet to separate the chaff from the wheat. And then after a while suddenly the company is full of 'mercenaries' which only care about their own carreer advancement but not about the games they create.
By that definition India would be its own continent because the country largely sits on its own tectonic plate.
Also Europe and Asia are continents, they're not on the same continent (same landmass: sure).
Sorry but that's just made up bullshit. The EU is not a "United States of Europe", and thinking along that line will ineviatably lead to tons of misconceptions.
I guess the confusion comes from thinking of "European" as some sort of cultural identity (which frankly doesn't exist, unless you only look at the last hundred years or so, and even that is generous), instead of the people living in the geographical region called "Europe".
That's a bit oversimplified. The Russians got quite a few important scientists and engineers in other areas (aircraft design, nuclear physics, electronics, radar, optics), they just didn't make as good use of them as the US (e.g. the 'American Germans' essentially won the space race for the US).
What? Scandinavia isn't part of Europe now? The "EU" is an organization, "Europe" is a continent. "European" includes everybody living in Europe (and yes, that even includes the Brits and most Russians).
Once the knowledge was "extracted" the Germans were allowed to return though (good thing Stalin was already dead at that time).
Former Junkers engineer Brunolf Baade then went on to build the first and only German jet airliner for East Germany - which then of course was cancelled as soon as it was ready to enter production: https://en.wikipedia.org/wiki/Baade_152).
Linked lists fell out of fashion once the cpu/memory latency gap opened up towards the end of the 1990s. For most use cases it's simply better to use a tightly packed array, even use cases where linked lists would intuitively make more sense.
E.g. an AmigaOS list node looks conventional, it has two pointers, one to the next node (succ), and one to the previous node (pred):
struct Node {
struct Node* ln_Succ;
struct Node* ln_Pred;
};
Most AmigaOS structs embed such a Node struct at the start....but the list header has three pointers which basically form two overlapped Node structs:
struct List {
struct Node* lh_Head;
struct Node* lh_Tail;
struct Node* lh_TailPred;
};
In an empty list, lh_Head points to &lh_Tail, and lh_TailPred points to &lh_Head. The lh_Tail pointer is always null (this is the 'end marker').In a populated list, lh_Head points to the embedded Node struct of the first list node, and lh_TailPred points to the embedded Node struct of the last list node. The ln_Succ pointer of the last node points to the address of the list header's lh_Tail pointer (...which is always null).
That way you only need an existing node pointer to walk forward and backward, or insert or remove a node. When walking the list by following the succ or pred pointers you know you've reached the end when encountering a null pointer.
Apparently the Linux-style lists in the article require to know the address of the list header to detect when the end is reached which isn't needed for the Amiga style list (at the cost of an additional 'sentinel null pointer' in the list header).
Pretty much all of AmigaOS was held together by such doubly linked lists.
(I hope I got that all right, it's been a long time)
Exactly, and having a Vulkan-only codebase won't make that problem go away. And IME it's much more likely to encounter vendor-specific driver issues on Windows Vulkan drivers than for D3D drivers.
Vulkan drivers on Linux are in a much better shape because they are centralized under the MESA project (except NVIDIA's drivers, which also have significant behaviour differences to the MESA drivers, at least in the window system glue).
> You may note that I specifically said "PC game developers" Your whole but consoles argument, completely misses the mark.
Why should a game developer support the tiny Mac market, but ignore the much bigger game console market though? From a business perspective, Mac support simply doesn't make sense, it's too much hassle for too little return (and the hassle isn't about the different 3D API, Metal is actually one of the best parts of the whole Apple developer ecosystem).
They probably stopped supporting macOS when Apple introduced the notarization bullshit. Can't blame the DF team tbh, macOS is a royal PITA to support (even without notarization), Apple doesn't mind breaking stuff from one OS release to another.
> Optimization and bug hunting makes supporting multiple graphics api's a pain.
The problems usually lurk in the graphics drivers, and not in the 3D API layer (e.g. optimization and bug hunting isn't much difference even when your code only supports a single API, and especially Vulkan drivers from different vendors may behave wildly differently on Windows, at least compared to D3D).
> I can see PC game developers seriously considering Vulkan over directx
Lol. That train has left the station long ago (around the time when Stadia was shut down, Vulkan saw a small uptick because of Stadia, but that soon fizzled out). Games need to support multiple 3D APIs anyway once they release on consoles. One or two more for the PC and Mac version doesn't make much of a difference (and most games are built on top of an off-the-shelf-engine anyway).
I wouldn't call Vulkan 'vendor neutral', but instead a collection of more-or-less adhoc design decisions to make Vulkan 1.0 work on specific GPUs that didn't match the AMD architecture (which Mantle was designed for, and then when Vulkan was derived from Mantle it had to add all the bells and whistles to extend the Mantle programming model for other GPU architectures, especially mobile GPUs).
From that PoV, at some specific point in time Vulkan might indeed not have been a good match for Apple hardware and might have required extensions to make certain features work efficiently (and those extensions might then later be rolled into core Vulkan). FWIW though, since somewhat recently Vulkan and Metal have started to 'harmonize' a lot (Vulkan via 'new' features like dynamic rendering - which is pretty much a 1:1 copy of the Metal render pass model, and from the other direction, Metal4 adopted some features from Vulkan/D3D12).
FWIW though, you can ask an LLM to write in 'Simplified Technical English' (see: https://www.asd-ste100.org/), which at times reads like its written for a child, but it is much better for inclusion of non-native speakers.