5,063 karma · joined July 15, 2021
As someone who regularly uses both, and even in spite of the ad avalanche that (a bog-standard home install of) Windows has become: [X] to doubt. I regularly have issues on my corporate Linux laptop that I suspect wouldn't ever happen on Windows. Fleet management is easiest on Windows, with Active Directory, Group Policy, images, etc. Maybe package managers make software management easier on Linux, but fleet sysadmin is basically built-in on Windows.
Linux is superb for servers—I use Proxmox VE as the hypervisor on my homelab—but it still has a rather long way to go as a sharp-edge-free desktop OS, regardless of whether it is for home or corporate use.
In fact I am not very happy with the little things when it comes to LTA.
They ruined MRT wayfinding with highly abstract symbols[2] in the new Thomson-East Coast Line, so much so that station staff have had to regularly supplant it with ugly printed signs that aren't standardised. They also changed from using alphabetical exits to numbered exits, with no listing of nearby landmarks. Older stations still have this wayfinding, but I suspect they will be replaced in short order, as everything in Singapore is wont to be.
Speaking of standardised, LTA have two corporate typefaces: LTA Identity, and Ocean Sans. They stopped using both and moved to Stroudley, which just looks bad, with ugly vertical terminators on the 'a', 'e', and 'g' glyphs. Ocean Sans is simultaneously superbly readable and yet very distinctive, something very few fonts have achieved.
I must also be in the minority but I do not like the new map[3]; it makes the city centre too cluttered. I much prefer the one from ~2010[4], which is quite reminiscent of the London Underground's map. In fact I believe they could've simplified it further by getting rid of station codes. Which passenger needs to know Dhoby Ghaut is NE6/CC1/NE24? Even as a (self-professed) transport nerd I don't really care.
I have other rants about the giant stroads, weird cycling paths, and their decision to use 'anticlockwise' and 'clockwise' for the full Circle Line, but that is neither here nor there, and I think other creators discuss that better than I ever could. Singapore's public transport is great, no doubt, but it could be so much better still. It needs trams.
[1]: https://blog.sgtrains.com/wp-content/uploads/2020/07/c151-st...
[2]: https://www.sgtrains.com/guide-wayfinding.html
[3]: https://blog.sgtrains.com/wp-content/uploads/2020/06/05-sm-2...
[4]: https://blog.sgtrains.com/wp-content/uploads/2020/06/03-Netw...
Quite the contrary: many new OLEDs are moving back to an RGB stripe subpixel arrangement.
All glyphs are indistinguishable from Source Sans. The 'thin'/'light' weights are kerned further apart (and in my opinion, worse) than in Source Sans. Given these, why does this typeface deserve a new name? It is Source Sans, full stop.
At least Arial (Helvetica copy) and Segoe UI and Myriad (Frutiger copies) have a handful of distinguishing glyphs.
I have a very hot take—with typefaces, you absolutely get what you pay for. I don't like the vast majority of SIL Open Font Licence type faces, with a handful of exceptions. Most of them have glyphs that are an absolute eyesore, are weighted, sized, hinted, and kerned terribly, don't have any character whatsoever (they're all copies of copies of copies of Helvetica) and don't encode nearly enough glyphs/combining marks in Unicode.
Hint: if I can't type IAST/ISO 15919 without tofu showing up, then the font doesn't have enough Latin glyphs.
The majority of digital fonts are either not hinted at all (which makes them look like crap on low – medium resolution monitors), or appear to be hinted on and for macOS, which doesn't have sub-pixel anti-aliasing, but rather greyscale (i.e. full-pixel) AA. The result looks quite bad on Windows and Linux. It looks bad on macOS in monitors with lower pixel density, too.
I will gladly pay for a well-designed typeface (or by proxy, pay a font database subscription). The effort that designers have to put in to design something new from complete scratch is immense. Designers have to come up with unique glyphs, and then when actually setting up the curves, then have to think about how the typeface will vary along several dimensions: weight, size, display pixel density, print versus display, and so on. It's no wonder that the best fonts cost thousands.
Good fonts that have both character and are immediately legible without being unnecessarily fancy is an extremely fine line to tread and in my opinion only a handful of typefaces have managed to balance all of these through the centuries. Some of my favourites follow.
Sans-serifs include Helvetica, Frutiger, Futura, Myriad, Johnston, Optima, Transport, DIN (and its many variants; my favourite is FF DIN), Ocean Sans, and Segoe UI.
Serifs include Roman-cut (including Trajan), Garamond, Minion, a handful of Didone types, Berkeley Old Style, and Palatino.
It's a bit like 'smallest hello world in assembly' but the code is just setting up the calling convention and then passing the zero-terminated character string into `write`. Cool, but that could be done a bit more straightforwardly in C, too. A lot of assembly (including in the linked repository) is book-keeping for the platform's calling convention.
I never disparaged it; I said having it doesn't make it any more useful that OSs that don't, because the practical reality is that the kernel interface is narrow and highly technical, and a stable kernel binary interface has little to do with a user's day-to-day experience with an OS.
I daresay Android would still work pretty well even sans the kernel ABI stability, because the kernel is usually built from source, and if it isn't, then every Android source tree has kernel prebuilts for the kernel version shipping. I also never said nor implied glibc should be uniquely privileged; I think you have misrepresented my comment.
This is exactly the attitude I meant by 'the kernel developers also have to take responsibility for, rather than shrugging their shoulders and pawning it off to GNU' and 'an OS is much more than just a kernel, it is a platform'.
By 'platform', I mean windowing toolkits, such as Wayland. Audio libraries like ALSA and PipeWire. Desktop idioms and libraries like DBus, and the entire freedesktop.org effort including Mesa and more. Init systems like systemd. Bootloaders like GRUB/systemd-boot. Networking, including systemd-networkd, iwd, and NetworkManager. Power and device management including PowerDevil, Bluez.
If all of this is considered 'user space' then my point is strongly vindicated. On most competitor OSs these comprise the 'platform'. You won't ever encounter a Windows or OS X developer arguing that USER32.DLL or Foundation is 'userspace' even if it is technically true and code from those libraries may only ever run in ring 3. From the average user's point of view, the only 'userspace' are end-user applications that they have installed, like Chrome, video games, etc. From that perspective, even purely user-mode applications that ship with the distro ought to considered 'platform'. This includes such trivia like calculator and camera applications.
We need to talk about the practical realities of a platform, not a theoretical, unattainable, and as I mentioned, useless ideal. These practical realities mean shipping a unified set of useful 'batteries included' user-mode libraries and applications. If one wants to develop the platform itself, then sure, the kernel has a nice stable interface, but on most Linux distributions the kernel is built from source anyway, so even that nicety is moot.
This is a noble but practically worthless ideal. Hardly anything is written against the kernel ABI except glibc itself. End-user application developers don't write against the kernel interface. Platform library and application developers like KDE and GNOME don't really write against the kernel interface either. Nowadays even driver developers don't entirely write against the kernel interface, instead also linking in glibc and lib{std}c++ for things like shader compilers (which is nowadays usually just a fork of Clang). Like it or not, glibc is the singular entry point for desktop Linux, which is the point of essentially every comment under this post.
That 'desktop Linux ≡ glibc' is something that I daresay the kernel developers also have to take responsibility for, rather than shrugging their shoulders and pawning it off to GNU. Linux's unstable user-mode is the entire reason for Docker's existence. It is bodge upon bodge and has led to much gnashing of teeth. The GNU/Linux community (I don't care for Stallman's meme rant here) have to grow a backbone and understand that an OS is much more than just a kernel, it is a platform, and currently the Linux platform is a disparate set of communities with highly divergent goals.
That's why I've always said the best Linux is Android, because Android is a platform.
This is categorically false; UCRT[1] is a thing. The 'U' stands for universal. Unlike Linux, Windows allows developers to choose their ABI boundary and also ship that boundary if they desire, or use the 'system' one and ask older platforms to install redistributables or Windows update packages. There's the old and new C runtimes in MSVCRT.DLL and UCRTBASE.DLL, the C++ runtime in VCRUNTIME140.DLL, Win32 in KERNEL32.DLL, USER32.DLL and more, and then the stable-ish kernel interfaces in NTDLL.DLL, in order of 'closeness to the kernel'.
And also, 'libc' is a UNIXism; on Windows the term is CRT, for 'C runtime'.
[1]: https://learn.microsoft.com/en-gb/cpp/porting/upgrade-your-c...
- Windows Internals, Parts I and II
- Windows 10 System Programming, Parts I and II
- Windows Kernel Programming, Second Edition
- Programming Windows, 5th and 6th Editions
Surely you mean leanest and meanest :P
I'd also say that tooling on Windows is simultaneously better and easier to use than on Linux; the noob case of green play button in an IDE is taken care of, but if you want detailed performance and memory profiling, record-replay debugging, hot-reload, all of this is straightforwardly available on Windows.
Oddly enough the open-source nature of the latter kind of takes away some of the thrill. Eerything is just... there, whereas with Windows there's always quite a bit of digging and investigation involved. Or maybe this is Stockholm syndrome; I dunno.
??? We don't need any AI for this.
Start with separated sewage/wastewater and stormwater drains. Then accredited and highly scrutinised wastewater treatment and discharge into water bodies (or see below for a high-tech solution). As for clean water to the home, direct those stormwater drains to new reservoirs which sustain freshwater aquatic life. Protect aquifers from over-drainage, and build pipelines from water-abundant regions to water-scarce regions.
To reclaim waste water or treat unknown water sources back to potable/semiconductor standards we have ultrafiltration, reverse osmosis, UV treatment, pH adjustment, fluoridation, desalination, softening (which is generally obviated by RO...). This is basically Singapore's NEWater.
Good sanitation is a financial and political problem. The engineering has been solved for decades now.
People had bad experiences on Vista because they tried to run Windows Aero on 2001 hardware, and hardware vendors for once strong-armed MS into certifying their half-decade-old hardware as 'ready for Vista'.
And in my opinion, the most slept-on: the fact it runs on the CLR and direct access to .NET objects and types which means access to P/Invoke and thence the Windows API. One can write business logic in the fast language and write a nice CLI wrapper around that in the natural shell language, and not worry about painful FFI unlike everyone else trying to fit Python or Bash into whatever world they're using.
The typical counter to this will be: PowerShell is verbose, PowerShell used `curl` as an alias to Invoke-WebRequest instead of the Real Thing™. Neither are real arguments.
But maybe that's because I'm the sucker, and since PowerShell is more verbose it costs me more tokens than the terseness of Unix shells. Oh well.
I think the key idea is fixed minimum/maximum boundaries for a lot of astrophysical phenomena—stellar protium fusion, the Chandrasekhar limit, Tolman–Oppenheimer–Volkoff limit, etc.
Most desktop OS compositors provide a void** buffer that can be blitted to. Sure, this buffer will probably end up going through the compositor which does GPU hardware acceleration anyway, but it is definitely possible to shrink the application-side stack without relying on D2D/GLUT/GLEW/GLFW/SDL/WGPU in this case.
On Windows: CreateDIBSection and BitBlt
On macOS: CALayer and CATransaction commit
Not sure about Linux, too many stacks involved.