1 reactions
WSL2 is actually fire
Been programming for years on the Mac for work, while having a separate laptop for gaming. I always hear people talking shit about WSL2, saying how it's super slow, clunky, people getting annoyed about setting things up, etc. I decided to take the plunge and worked on a fairly large side project - fullstack - programming on my gaming laptop with WSL2, and the experience has been great. Here are my takes on the issues I'd mentioned above:
* Slow, clunky, etc. - get more RAM. Don't know if this is *the* solution to the issue, but, at 32 GB of RAM, I have absolutely 0 issues. Keep in mind, though, YMMV, as I think that it depends on what you're doing. I do web development, working with the usual client-side stuff (React, Svelte) and Node, Deno, and Golang for backend stuff, depending on the situation. All work fine.
* Annoying setting things up - Just set up a dotfile with a bare Git repo. Boom, problem solved.
Glad I finally took the jump. Now I don't have to lug around a Macbook anymore; just gonna keep my work laptop at the office and program with my gaming laptop at home.
---
Good morning, y'all. Seen a lot of comments get added overnight. There were some interesting conversations going, and there were some crazies, but, overall, I'm glad to see that a lot of us agree that what matters most is what we prefer + what works for us, which is what this post was about. I wasn't saying that WSL2 > MacOS, nor was I even trying to compare them or other OS's in that way. All I was saying is that WSL2 works for me and my preferences and offering potential solutions for those who want to use WSL or are using WSL. I still use MacOS at work, and never have I said that I dislike it; I love MacOS for what MacOS offers, much like how I like WSL2 for what *it* offers. It's as simple as that; time and place.
source
Been programming for years on the Mac for work, while having a separate laptop for gaming. I always hear people talking shit about WSL2, saying how it's super slow, clunky, people getting annoyed about setting things up, etc. I decided to take the plunge and worked on a fairly large side project - fullstack - programming on my gaming laptop with WSL2, and the experience has been great. Here are my takes on the issues I'd mentioned above:
* Slow, clunky, etc. - get more RAM. Don't know if this is *the* solution to the issue, but, at 32 GB of RAM, I have absolutely 0 issues. Keep in mind, though, YMMV, as I think that it depends on what you're doing. I do web development, working with the usual client-side stuff (React, Svelte) and Node, Deno, and Golang for backend stuff, depending on the situation. All work fine.
* Annoying setting things up - Just set up a dotfile with a bare Git repo. Boom, problem solved.
Glad I finally took the jump. Now I don't have to lug around a Macbook anymore; just gonna keep my work laptop at the office and program with my gaming laptop at home.
---
Good morning, y'all. Seen a lot of comments get added overnight. There were some interesting conversations going, and there were some crazies, but, overall, I'm glad to see that a lot of us agree that what matters most is what we prefer + what works for us, which is what this post was about. I wasn't saying that WSL2 > MacOS, nor was I even trying to compare them or other OS's in that way. All I was saying is that WSL2 works for me and my preferences and offering potential solutions for those who want to use WSL or are using WSL. I still use MacOS at work, and never have I said that I dislike it; I love MacOS for what MacOS offers, much like how I like WSL2 for what *it* offers. It's as simple as that; time and place.
source
| 11,000 mlx | |
| 21 | |
| 1 |