If you are new to Linux I would recommend buying a second drive or dual-booting for a bit just to ease into it. It has helped me persist with the transition because I always have the option of booting into Windows for a few hours if there’s something that I’m just too tired/frustrated to deal with at that given moment. Over time I’ve found myself booting into Windows less and less, to the extent that I’ll be able to drop it completely later this year without the big learning curve/wave of troubleshooting that I encountered the first time I tried to switch cold turkey.
@Ilandar this is a good solution . Another would be to just not jump ship head first, but rather replace everything wth FOSS alternatives instead if they’re not available on Linux (e.g.: replace MS Office with LibreOffice, Photoshop with GIMP or something else, etc.) and use them for a while. Most of the programs should also be available for Windows, and if not you could also use WSL to run them.
Once you get used to these programs, the actual Linux transition should be easier.
Yes, that’s a great strategy and one I began before even transitioning across. I guess the only reason I didn’t initially mention it is because I’ve found many Windows users immediately switch off the moment you tell them they might need to consider non-proprietary apps and services. There are a lot of really solid and reliable workarounds these days that mean you can keep some of that Windows workflow if you really want to, so I feel like maybe it’s best to just let them try the operating system first and see how much they can get away with.
@Ilandar you’re right, I didn’t think about this. However I might add that there are still programs that do not function well even under Wine. For example, the latest version of Office is always problematic to set up.
If you are new to Linux I would recommend buying a second drive or dual-booting for a bit just to ease into it. It has helped me persist with the transition because I always have the option of booting into Windows for a few hours if there’s something that I’m just too tired/frustrated to deal with at that given moment. Over time I’ve found myself booting into Windows less and less, to the extent that I’ll be able to drop it completely later this year without the big learning curve/wave of troubleshooting that I encountered the first time I tried to switch cold turkey.
@Ilandar this is a good solution . Another would be to just not jump ship head first, but rather replace everything wth FOSS alternatives instead if they’re not available on Linux (e.g.: replace MS Office with LibreOffice, Photoshop with GIMP or something else, etc.) and use them for a while. Most of the programs should also be available for Windows, and if not you could also use WSL to run them.
Once you get used to these programs, the actual Linux transition should be easier.
@Onii-Chan
Yes, that’s a great strategy and one I began before even transitioning across. I guess the only reason I didn’t initially mention it is because I’ve found many Windows users immediately switch off the moment you tell them they might need to consider non-proprietary apps and services. There are a lot of really solid and reliable workarounds these days that mean you can keep some of that Windows workflow if you really want to, so I feel like maybe it’s best to just let them try the operating system first and see how much they can get away with.
@Ilandar you’re right, I didn’t think about this. However I might add that there are still programs that do not function well even under Wine. For example, the latest version of Office is always problematic to set up.