3 ms·
It wasn't the first issue I ran into being on osx and everyone else using windows. As someone who used these machines for work, I can't control what terrible p
by robotjosh 10y ago
It wasn't the first issue I ran into being on osx and everyone else using windows. As someone who used these machines for work, I can't control what terrible protocols people use, I just need it to work.
- sbuk 10y ago>"It wasn't the first issue I ran into being on osx and everyone else using windows." So Microsoft using outdated and insecure prototocols, as well as propriatery[0] ones is Apple's fault? It's perfectly fine to say "I don't like Apple/the direction they are taking, so I'm moving to another platform." Use what works best for you. Just don't use petty excuses for it. Sorry, you are baring the brunt of the glut of "Why I'm switching" articles. [0]Yes, I realise that Apple can also be a bad actor in this department too.
- robotjosh 10y agoThere are a lot more reasons I switched to windows than a vpn that stopped working. I tried for over 4 years to incorporate osx into an engineering work flow. The nominally cross platform eclipse stack I was using never became fully compatible with osx. It was always a usb driver or something stopping the osx version from working. Even when it did work, I would check in a project and someone else would be like "omg this doesn't work, did you do this in osx?". I had a total of 1 project ever where the client wanted to mess with the code in osx and was glad I could do it in osx. Ended up using parallels for almost all compiler toolchains. My saleae scope software is buggy in osx, ties up a cpu at 100% while its open for some reason- had to use that in parallels too. What DID I use native osx for? Browsers? Mac vim? Linux commandline? It clearly has not been worth the time and money.