Hacker Newsnew | past | comments | ask | show | jobs | submit | okanat's commentslogin

Well it made sense for France for multiple reasons even in 70s. France didn't trust / like Anglophone dominance in the world. They brutally kept their colonies, sometimes to the bitter end. The mistrust to US/UK hegemony and the strong sense of nationalism is the reason we have Ariane and Airbus programs. Henceforth, they also invested in their own nuclear program. To make small and cheaper nuclear weapons, you need plutonium which can only be created in reactors. Even with that knowledge they burned fossil fuels majorly before 70s.

France built majority of their nuclear reactors after 70s oil crisis. So it made sense to have independent resources for them. So they won't need to rely on other nations, some of which were their former colonies that hated them. They had two strong reasons to keep a nuclear base electricity generations.


Only Germany did. They were quite anti-nuclear in the 80s. So they didn't upgrade the reactors. The closure was inevitable. US also supported this more neutral position btw and everybody mocked French for being the lone wolf.

Onion routing is the protocol. Tor is the network and the name of the reference implementation.

WSL supports a kernel-based DirectX to Mesa bridge. It is better than any other VM implementation. However the latest releases caused some problems with auto detection mechanism in Mesa. Sometimes the Linux kernel module also fails to load.

You need to ensure that DirectX driver is used with tools like eglinfo. Most of the time, the main culprit is LLVMpipe software driver being used due to wrong detection.


You can't run a proper VM there though, something like a normal distro with systemd, KDE Wayland session and etc. At least from what I've figured out so far. Basically I need a normal full featured VM, not some gimped variant and with graphics acceleration preferably.


Umm you must be rather inexperienced in Windows and didn't do much search for that to happen.

1. WSL2 mounts Windows drives under /mnt/ . You can just cp things

2. WSL2 Distros are exposed as Network shares. WSL installs a virtual "Linux" shell folder to Desktop and explorer navigation bar. It is hard to miss. Moreover a simple search query would show you \\wsl$ share

This was the top result for me:

https://askubuntu.com/questions/1439131/access-root-user-dir...


I will start by saying I haven't used Windows as my full time desktop in 20 years. I did use VS/Windows for 2 years while I did a C# project in 2013-2014, managed a bunch of windows servers, used (and liked) powershell, everything, but that was inside a VM on my mac. And the other two windows full-time devs I was helping had never used linux or WSL (and one of them was not terribly keen on the whole idea). But we were all new to WSL. I knew WSL was very easy, and even many devs at MS use it.

So to provide more detail, things were slowed down further because this was one of those teams meetings where you can't just take over, but have to tell someone to type another command and wait for them to type it. The second thing was that the user didn't tell me that they were switching to another user when escalating to admin (cuz I couldn't see that elevated system dialog in the screen share). So it turned out they had installed WSL as a different admin user, so when they went to \\WSL$ (as their original user), it wasn't showing any shares. That set off a lot of googling and claude'ing that went nowhere.

Suffice to say I was ready to end the day after that meeting :-)

A red flag early on was when a bun install took 8 mins when trying to run it on /mnt/c, when it took 200ms on my machine. So I knew there had to be some weird filesystem overhead stuff going on. So then when we got it working beautifully by just using the VM's filesystem, I was personally happy with it but the person on the other end felt this was all too cumbersome and was soured on WSL, even though I tried to explain the differences.

I kept thinking that WSL was the greatest thing since sliced bread and got the message that MS had found a way to make them work beautifully together (especially in WSL2). I'm sure I could've figured this all out on my machine in probably 10 mins.


CAMM is adopted by the more expensive business class laptops. I think Thinkpad P1 / X1E adopted them first.


You need to enable sparse VHD! However it doesn't alwyas trigger. I have moderate success with enabling TRIM systemd service on the distro.

Here is the tracking issue:

https://github.com/microsoft/WSL/issues/12103

And if nothing works you can still manually optimize.

https://superuser.com/questions/1827953/reclaim-wsl2-disk-sp...


You can always buy some SKHynix or Micron shares.


That doesn't help me lock in prices when I'm giving quotes on hardware that still needs to be manufactured.


Vista wasn't that bad from purely OS side. On a VM it runs pretty stable.

However, Microsoft made a huge change to how the OS and drivers worked. If you still use Windows, you are still benefitting from some of the changes.

However HW vendors usually ship rather broken drivers, it was doubly bad since Vista overhauled the driver interface. By the time all vendors fixed their shitty and badly tested drivers we already had 7. It is also partly Microsoft's fault since they had absolute chaos in Vista development due to shitty hacks on top of hacks that was the consumer OS (XP).

Similarly Vista was very heavy for its contemporary average hardware. By the time HW caught up, 7 was released.


Anybody who experienced or knows how haphazardly the Microsoft consumer division forked and developed XP would prefer 2000 or 2003 over XP.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: