netwake
WSL
netwake | WSL | |
---|---|---|
3 | 406 | |
53 | 16,652 | |
- | 0.6% | |
0.0 | 8.6 | |
over 2 years ago | 6 days ago | |
C | PowerShell | |
BSD 2-clause "Simplified" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
netwake
-
Windows 95 went the extra mile to ensure compatibility of SimCity, other games
I wrote one to try. It also uses runtime feature detection to enable modern stuff like theming and high-DPI on Windows version that support it.
-
The Windows Malloc() Implementation Is a Trash Fire
> Ideally you'd like to build for all targets, including older systems, from a single, modern environment (this is trivial in Windows)
https://github.com/sjmulder/netwake does what you're talking about, but it does a lot of gymnastics to make it work, and it also needs to use MinGW rather than MSVC.
-
Windows 11: a survey of text boxes
> if you wrote a Windows Desktop app in the last 30 years, the only way it would still be supported today ... is if it was based directly on the old Win32 API
I thought the same and did just that to see if it holds true: https://github.com/sjmulder/netwake
By default you get Windows 95 styling and Windows 3 fonts. You have to opt into 'visual styles' (introduced in XP) with a declaration in the app manifest and have to manually query and use the system font. DPI awareness is also opt in and puts all the work (sizing/positioning, scaling/reloading fonts) on you. But when you do that, it does look fine on Windows 10.
Not so much on Windows 11. Some of the widgets have been updated to mimic the new style but when you put it together it looks messy and old fashioned (e.g. fonts + you don't get the new context menus).
I'm curious to learn how one would create a 'proper' Windows app without having to reimplement the system's widget styling.
WSL
-
GoboLinux
It absolutely 100% can be true.
As an example: Windows Services for Linux 2 used a special init daemon to interact with the host OS.
That meant no systemd. That meant that the `systemctl` program wasn't there.
This baffled legions, armies, of wannabe sysadmins.
https://stackoverflow.com/questions/55579342/why-systemd-is-...
https://superuser.com/questions/1785697/systemd-in-wsl-on-wi...
https://github.com/microsoft/WSL/issues/9477
https://askubuntu.com/questions/1132230/unable-to-run-any-sy...
People on the whole have no idea how this stuff works, and they just copy magic incantations from StackOverflow to get stuff to happen. If that doesn't work, then this OS is broken. The end.
For these guys, WSL was broken.
Result:
MS hired Lennart Poettering.
https://www.theregister.com/2022/07/07/lennart_poettering_re...
He "fixed" it. Systemd now works in WSL2. All those guides for noobs now work. Everyone is happy.
In a world where tools like Flatpak and Snap are proliferating and it's driving deep divisions between Linux distros, if you think the average person struggling with Linux is going to use `ldd` to work out where the dependencies for something live, I'm afraid you are a deep guru who lives on a different plane of existence.
We now have widely-used packaging systems which simply embed an apps entire dependency tree into a package to avoid people having to work out the difference between `apt` and `rpm`. Thousands of terabytes of disk are being burned to make this stuff go away.
Yes, this is too hard. Way too hard.
-
Why Linux utilities tend to run poorly on Windows
Better source: https://github.com/Microsoft/WSL/issues/873#issuecomment-425...
- Weird graphical glitch/problem in Ubuntu WSLg (OpenGL)
-
RamRamRamEveryoneSleepingOnDocker
One of the bugs where on the Docker side. As I have said, there have been several since release with a lot of impact period overlap. The latest and greatest is not resolved.
-
Laravel dev in Windows - Laragon vs Docker?
It's the issue of abysmal I/O performance in communication between the mounted WSL2 virtual hard disk and Windows mounts inside the WSL2 distro.
- WSL freeze seems fixed in 2.0.12
-
What's the right way to open files in the system's default program from Ubuntu 22.04 in WSL 2 please?
I found this github page and I was able to reproduce this from the answer
-
Ask HN: Best Docker open source alternative?
* Docker engine and not Docker Desktop in a VM. WSL2 works well after some configuration: https://github.com/microsoft/WSL/issues/6655#issuecomment-11...
-
Broadcom to Cut Almost 1,300 VMware Jobs in California After Takeover
Seems to more of a Defender issue than a WSL one, see https://github.com/microsoft/WSL/issues/8995
After adding exclusions for the fsnotifier-wsl process and and both variants of the WSL distro path my disk performance was improved.
Adding the idea64.exe process also helped since I was trying to run IntelliJ against projects inside WSL.
- Bricked WSL 2 after 2.0.9 / Windows 10
What are some alternatives?
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
genie - A quick way into a systemd "bottle" for WSL
Scoop - A command-line installer for Windows.
Single-GPU-Passthrough
setup-msys2 - GitHub Action to setup MSYS2
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
UTM - Virtual machines for iOS and macOS
usbip-wsl2-instructions
FFmpeg - Mirror of https://git.ffmpeg.org/ffmpeg.git
azurelinux - Linux OS for Azure 1P services and edge appliances
tilt-extensions - Extensions for Tilt
gvisor - Application Kernel for Containers