While I can’t categorically say it gets better with time, it has for me. I have an 18 month old and an almost three year old. I’m back to quasi-normal sleep now. I do wish we had kids when we were younger (I’m 37), but we weren’t planning on having any.
Well my toddler is 16 months and things did really already improved a lot in terms of sleep, but the new baby is coming any minute now ... so I expect less of it in the next time ;)
I guess I should have been more verbose in my original comment. Windows is hot garbage, but there hardly exists a good reason for dual booting. Use a Windows VM from Linux if you can, WSL2 from Windows if you must.
I am considering building a PC for programming and am genuinely curious if WSL2 can be considered a replacement for dual booting Linux and Windows? I am currently rocking a dual boot system (with legacy bios) and haven't had any issues so far.
It's pretty close. Big pain point for me still is that running an IDE from Windows and accessing the Linux FS is not quite as snappy as native-Linux (I use IntelliJ). So for now I still dual-boot.
This is apparently being worked on... in the future I will be able to run the IDE inside WSL and it will bridge X11/Wayland to Windows.
If you can try using Visual Studio Code, with their remote plugins. One of the remote plugins is for wsl2 and it works great.
That means that VSC installs language server inside the wsl2 environment, I use it at home for my rust/python development and can't tell the difference.
I gave up on dual-booting a long time ago and 2 OSes fighting over overwriting the MBR every time I wanted to upgrade one or the other. It's just so much easier to maintain 2 machines.
I solved for this by simply giving Windows and Linux a hard drive each. The boot records are completely separate, and neither one tries to read data from the other. (Personally I have no need, my NAS handles any file level syncing, but that's minimal anyway.) Both Windows and the Linux boot are registered in UEFI, so I asked my BIOS to disable the hard drive preference and pop up the boot menu each time, letting me pick which OS to use manually.
> I gave up on dual-booting a long time ago and 2 OSes fighting over overwriting the MBR every time
This is why UEFI was invented, and if You actually read the post, you would know it details how you set this up with UEFI instead of legacy boot and have none of those troubles.
Isn't WSL2 a step backwards from WSL? A thinly veiled VM, vs. proper Linux emulation? What's the performance story and cross-execution (starting Windows programs from Linux side, or vice versa) on WSL2 now?
I don't agree (based on the fact that the host can run multiple images/VMs). In my opinion first of all the host should be secured (Firewall & Fail2ban etc...).
To distribute security to the single images/VMs increases complexity and the likeliness that some image/VM will miss some security filter, and leaves the host itself unprotected (e.g. network time sync & ssh & other stuff will probably be running, any update to the host's SW might result in unexpected services running, etc...).
An additional (dedicated) layer of security in the images/VMs would of course still be ok.
But you can also use a container as first contact and redirect to other containers. You can bind a network device to a container.
For example a reverse proxy container which redirects to a gitea container or a wordpress container depending on the request. The reverse proxy container can also centralize the security with certificate handling or fail2ban.
You still need access to the host, via ssh for example, to start the containers and do some basic maintenance. Won't you have fail2ban installed on the host since your ssh port would be open?
If you need direct access to the host, it’s probably a non production environment or you’re doing containers wrong. Kubernetes clusters provisioned with Terraform, for example, should almost never require ssh access to workers nodes.