• 4 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle









  • Holy hell, a lot of what you just described hit right home with me.

    I started off as one of the cheap developers (“technical consultant”) for one of those Microsoft business products. Almost every single one of our customers are already ingrained into Microsoft ecosystems and setting up the system we customize and sell is mostly a matter of integrating into their existing AD, Exchange Mail Server and sometimes their private cloud. I was pretty ignorant of open source tools that would tremendously help even if you’re mostly using Microsoft. Ignorant might not be the right word. It would be more correct to say “afraid to peek out of the comfortable Microsoft bubble”. It wasn’t just me, a lot of propriety consultants don’t really bother with anything else. If something’s beyond our capabilities we can always get the support of Microsoft, supposedly. This chain of responsibility give end customers assurance somehow. Like you said, assurance on who to blame and sue at least.

    Took me a while to break out of Microsoft bubble and now I do open source ERP. I do get by okay, but I think it’s mostly because my country cannot afford Microsoft license fees.




  • You should make a detailed check list of things you do on windows. Down to every details as much as you can, so that there’s very little surprise when you switch to linux.

    For example, if you use MS Office Excel and you tend to use specific formula or expect something specific when you export to PDF or print things out. So that you can test these out on Libre Calc to see if it works for you.

    We tens to gloss over these tiny details when switching to linux and sometimes it makes or breaks adoption.

    Will also work to just dual boot and trybto do everything in linux. Might be tedious at first. Try to resist booting into windowsif you’re stuck for a while.


  • Been daily driving WSL Debian for about a year on my work laptop, without systemd and display server. At first, I was really only using it for application servers that just won’t run or too tedious to run on windows. But windows is just terrible for dev work that’s not part of windows eco system. So I found myself slowly moving most of my dev stuff to WSL. There are still some problems though.

    Off the top of my head, first is neovim and the system clipboard. I can use clip.exe but there’s a problem with unicode characters. It’s expecting some UTF-16 encoding or something but my bash is in UTF-8. And somehow that messes up copying some unicode characters. I have to either use iconv to convert the encoding before copying or may be change my bash encoding.

    Another recent problem I had is binding WSL ports to the window host’s network. WSL automatically binds the service ports to host window’s localhost with the same port number, which is pretty useful. But it only binds to localhost address. If you want it to bind to other addresses, you can’t configure it. You can to run some kind of a patch program someone wrote, that rebinds WSL ports the wildcard address. And it doesn’t work very well if the patch program’s version and your WSL’s versions are not compatible.

    Another minor problem is that there’s some kind of a freeze that lasts for about a minute when I’m doing fzf in bash. It happens sporadically. I’m not entirely sure if the problem’s with Windows Terminal or WSL. It’s likely WSL. It seems to happen with other terminal emulators as well.

    All in all, WSL makes having to be on windows a whole lot bearable. I’ll probably end up using only rudimentary UI apps on windows and move the rest to WSL.