amp.dev
WSL
Our great sponsors
| amp.dev | WSL | |
|---|---|---|
| 1 | 25 | |
| 576 | 1,845 | |
| 0.2% | 1.7% | |
| 9.1 | 8.9 | |
| 6 days ago | 6 days ago | |
| HTML | PowerShell | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
amp.dev
-
WebAssembly
Here's one: https://amp.dev/documentation/examples/components/amp-analyt..., backed by https://github.com/ampproject/amp.dev/blob/future/examples/s...
WSL
- Windows VBS
- [Bashonubuntuonwindows] \"Veuillez activer la fonctionnalité Windows Virtual Machine Platform et vous assurer que la virtualisation est activée dans le BIOS.\ »
- Why do I get two different results from different PCs
-
can't use WSL2 despite virtualization and Windows machine platform feature enabled, and error message says thye're not.
I have found some documentation here https://github.com/MicrosoftDocs/WSL/issues/536 and here https://learn.microsoft.com/en-us/windows/wsl/faq#will-i-be-able-to-run-wsl-2-and-other-3rd-party-virtualization-tools-such-as-vmware--or-VirtualBox and intend to read them fully including the links inside them tomorrow or the day after when I have time.
-
There are literally no reasons to choose an iPhone over an Android smartphone
Off the top of my head was this bug that caused a lot of people using vbox to swap to vmware. Just a bunch of really annoying compatibility bugs that made it a nightmare if you were trying to use it like a native linux instance.
-
Is Microsoft's CBL-Mariner Going to Become Microsoft Linux?
>and I’m almost certain that when you run multiple wsl distros they are all in one VM, though that may be wrong
Yes, they run as containers.
From https://github.com/MicrosoftDocs/WSL/issues/1573#issuecommen...:
WSL distributions (instances) are not VMs. They are best described as "containers" running inside the WSL2 VM. Each WSL2 distribution/instance has its own isolated:
PID namespace
-
Unable to run any docker container using WSL2
(As I've understood, Hyper-V Management Tools should not be needed when using WSL2, based on: https://github.com/MicrosoftDocs/WSL/issues/899)
-
Kernel Panic when trying to install AlmaLinux 9 in VirtualBox
Here https://github.com/MicrosoftDocs/WSL/issues/536
- Docker for Windows failing to start: "WSL system related access rights are not set correctly"
- AlmaLinux / WSL2 / Start Apache
What are some alternatives?
content - The content behind MDN Web Docs
Chocolatey - Chocolatey - the package manager for Windows
sorbet - A fast, powerful type checker designed for Ruby
toolchains_llvm - LLVM toolchain for bazel
design - WebAssembly Design Documents
dnf - Package manager based on libdnf and libsolv. Replaces YUM.
noclip.website - A digital museum of video game levels
ipe-wiki - A Wiki for tips and tricks related to Ipe
Files - Building the best file manager for Windows
berry - 📦🐈 Active development trunk for Yarn ⚒