Of course, offline rendering is a different story.
5,063 karma · joined July 15, 2021
Of course, offline rendering is a different story.
I really ought to have been more specific with my first sentence to ward off any hair-splitting.
The author claimed to love software rendering, but the examples given to highlight the supposed positives of software rendering can all be achieved on GPUs. If the author had instead highlighted the ability to easily debug and inspect the inner workings of the rasterisation pipeline with a software renderer, that might have been a much more relevant argument.
Also, modern spatial anti-aliasing works by multisampling within a pixel (or even neighbouring pixels) and taking the average, rather than filtering across singly-sampled pixels, which massively reduces the quality. Not to mention temporal and machine learning AA techniques including DLSS, XeSS, FSR, and all the TAA implementations in many games.
I singled it out because I've been badly burnt by it in the past, and I dislike how it works compared to Win32. Back-targeting old glibc from newer (a very common case because developers tend to have newer distros than their users), requires either changes in source code (not build code, which is where it ought to be) to explicitly pin versions, or the ridiculousness of firing up an entire Docker container just for old glibc. It has regularly caused issues for things like Steam on Linux.
Within Google, a Chromium build uses remote build execution by default, upstream Clang by default (for the latest features and fixes, and Chromium developers regularly contribute to LLVM), and needs to cross-compile easily for at least a dozen different OS-architecture triples (Linux x86-64, Linux ARM, macOS, Windows x86-64, Windows on ARM, iOS, Android x86-64, Android ARM, Android TV, some BSDs, etc).
Everything you've listed—from ninja, to Clang, to libraries with custom patches, to Clang releases, including requiring pre-releases sometimes—is optimised for Google's scale, rather than the lone warrior developer. What you call 'sane Linux defaults' (especially the examples you have listed: GCC, automake, so-called 'system libraries') are highly antagonistic to all of the above.
They may make life easy for the so-called 'default case' of desktop Linux (arguable; Chromium was first released on Windows, and secondly since desktop Linux's most common C library, glibc has an unstable ABI, making back-portability impossible), but make it incredibly hard to get out a project of such immense complexity. All of Chromium's tooling and 'complexity' was developed in response to the 'sane' defaults being not so sane after all.
To get a GCC cross-compile for a given set of architecture triples, one needs a complete graph of GCC toolchains targeting every pair of host and target. On the other hand Clang is natively a cross-compiler; pass in `--sysroot` and the host compiler will redirect for the target instantly. Automake (and the autotools in general) is slow as molasses compared to ninja. It is based on computing and compilation from the 1970s, and their defaults probe for long-since-dead string comparison functions that are expected to work by default nowadays on most hosted systems. Not to mention it has an extraordinarily complicated configure step[1], and an equally appalling macro-based configure language.
Ninja is purely declarative, and is not even meant to be human-readable, as it is a back-end for a variety of build generator tools (CMake, XMake, build2, Bazel (Blaze internally at Google), Meson, probably more). Google have in fact rewritten Ninja to be a remote-build-capable tool from the outset[2], and they call it Siso. Siso has more than halved my Android build times even compared to Ninja because of its incredible use of RBE.
Frankly I think it should be evident why they have opted for 'rewriting the world' including vendoring and modifying system libraries, as well as including efforts like Skia, ANGLE, and more: directly relying on 'system libraries' is painful. I mentioned GPU drivers. Imagine rewriting the same code over and over to have precisely the same behaviour on D3D, Vulkan, OpenGL, Metal, and every single vendor GPU driver on every single system (and there are a lot more on mobile than on desktop: ARM Mali, Qualcomm Adreno, Samsung Xclipse, Imagination PowerVR, Huawei, MediaTek; this is not even close to exhaustive, just look at the Khronos vendor list).
When comments like yours are made I wonder if there is ever a consideration beyond 'it makes the developer's life hard'. As developers, our ultimate target audience are the users of our software. We should be willing to do anything come hell or high water, even making the dev-ex extraordinarily convoluted, if it means the user experience will be the smoothest and fastest possible. Sure, there is a balance, but I believe it should be strongly skewed towards the user story first.
[1]: https://upload.wikimedia.org/wikipedia/commons/8/84/Autoconf...
[2]: https://chromium.googlesource.com/build/+/refs/heads/main/si...
This sounds like Windows. ;)
Environment variables are stored in the registry; for the user, it's
HKCU\Environment
and for system-wide env vars, it's HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\EnvironmentInb4 (in this case in-after) trope answers (see below) like 'veneer of perfectly clean and orderly society', 'punitive'. It is small; that is why it can get stuff done.
Own a recent-ish BMW. Haven't had to pay for heated seats; I have a button on my climate control to switch it on/off/change the heat levels.
My point is that the land use in Singapore truly shows where LTA's priorities are. Look at Tengah or Bidadari, both brand-new neighbourhoods. Huge, wide 6+-lane dual-carriageways with hardly any traffic on them.
My family has a car in Singapore that has about 70000 km on the odometer after about 6 years of driving, which is quite a lot for purely urban driving. The fact is I can get to most of destinations in about half or a third the time it takes on public transport. It is primarily why I drive if I have to get there quicker.
Singapore uses about 11%[1] of its extremely limited land area for land transport (primarily, roads, since all railways are urban passenger rapid transit and not freight). I believe this is too much. 10-13 lane stroads are not uncommon, especially at junctions[2]. Singapore needs more light rail, trams, and permanent bus lanes with bus priority signals, as well as considerably more traffic calming measures in residential neighbourhoods.
Don't get me wrong, its mass rapid transit story is superb, first in class, but mixed-mode transport and last-kilometre connections need to be better.
Also, and related to the post: the Tamil in the website is wrong. Even in the colloquial register I haven't really heard anyone say 'வந்துட்டு'; it ideally ought to be the formal 'வந்துள்ளது'. Better still, a simpler and more accurate translation of 'Waymo in Singapore' is 'சிங்கப்பூரில் Waymo'.
In almost no situation are pickup trucks, SUVs, or even a crossover the correct kinds of vehicle.
Americans just buy much bigger vehicles than necessary.
SystemD has single-handedly consolidated and streamlined Linux administration. I think valid criticism is useful, but calling it malware is a non-sequitur.
It is essentially an entire Chromium instance around msn.com/weather.
> make technical writing parsable by the unwashed masses
> If the masses want to understand science they should just go to Oxford
This is a bad strawman. I learnt scientific notation in secondary school. I expect most educated people to understand what is meant by '1.5 × 10^8 km' in an instant. If they don't, then honestly, skill issue, and it is a big indictment of their parent country's education system.
You said these comparisons are made to make things real or relatable; I personally would expect more out of my audience and give them the magnitude and units directly. I'm not writing for a tabloid; having a strong grounding in units understanding without needing to relate to daily phenomena is in my view critical to not making apparently trivial mistakes that can potentially lead to horrible disasters.
> Enceladus is far smaller than the Jovian ocean worlds, roughly the size of Ohio
Why not just say 'has a diameter of about 500 km'? The propensity of astronomers to compare diameters of a small spherical object to a surface patch of a much larger spherical object is intriguing. Similar things happen with 'the Great Red Spot is about two Earths wide'.
Holy shit. RF to zero-click exploit is a new one. I guess digital-everything wasn't always a good idea, this probably wouldn't ever have been a problem with analogue antennas and CRTs.
What are the people at LG even doing?