(no title)
thepostman0 | 2 years ago
Interesting view with cloud vendors, there does seem to be a shift from traditional LAMP stack.
thepostman0 | 2 years ago
Interesting view with cloud vendors, there does seem to be a shift from traditional LAMP stack.
HideousKojima|2 years ago
chasil|2 years ago
Cygwin and busybox performance is awful in code that calls fork() often, but I understand that WSL1 behavior is very different, because fork() isn't fighting through layers of Windows.
The reason that the POSIX layer exists in NT is that Microsoft was the largest UNIX vendor in the early 80s with their XENIX variant, where the largest market segment ran on the TRS-80 Model 2 (68k-based, 3 simultaneous users, two attached rs-232 terminals).
"Broad software compatibility was initially achieved with support for several API "personalities", including Windows API, POSIX, and OS/2 APIs – the latter two were phased out starting with Windows XP."
https://en.m.wikipedia.org/wiki/Windows_NT
jmmv|2 years ago
https://jmmv.dev/2020/11/wsl-lost-potential.html
jonhohle|2 years ago
My mental model is that they shed any UNIX business to focus on Windows, but then POSIX happened and they had to provide something in the market to meet the requirement.
CoolCold|2 years ago
Postgresql will become cool once they start thinking on operators - they still lack simple `show slave status\G` statements for quick checking replication status. Googling everytime for the WTH of tables needs to be queried.
fragmede|2 years ago