6 ms·
As a front-end developer who attempts to keep up with the latest and greatest in my industry, I have to say that there does seem to be some sort of bubble with
by talmand 15y ago
As a front-end developer who attempts to keep up with the latest and greatest in my industry, I have to say that there does seem to be some sort of bubble with people on their Macs. Too many times I've seen documentation that assumes that everybody is on a Mac. Too many times I've seen demos that assumes that everybody is on a Mac. Too many times that software that can easily be cross-platform are not or they don't document it as such. Too many times I've seen comments that say if you aren't developing on a Mac then they heavily imply you're a loser.
Much of that also assumes that everyone has an iPhone or an iPad.
For instance, why is getting Phonegap up and running on a Windows machine such a tragic pain in the ass? I got it going on my laptop to play with and after that experience I'm considering putting "successfully installed Phonegap on a Windows machine" on my resume and LinkedIn profile. I may be missing something but even the Windows install documentation I've seen on their website is several versions behind the current release.
As a counter, getting SASS running on my Windows machine was a breeze in comparison.
Now, if it's software and you only want to develop it for OSX, that's cool. But if it's a simple tool that can easily run cross-platform, then don't pretend it doesn't.
It's like the complaints about webkit only prefixes on so much stuff on Github, I'm willing to bet it's because of Mac people not caring about every other browser/OS out there. That's a guess, nothing to back that up.
Most of the people who complain about developing for IE being difficult seem to be Mac people and more than likely have no idea what they're talking about. With my job I support gecko, webkit, and IE7+. Until recently that included IE6. I do not use hacks unless I absolutely have to and I avoid using IE-only style sheets. IT IS NOT THAT HARD!
If you think supporting modern versions of IE is too hard then you may need to reconsider your workflow as it's probably the problem. It is your job to support all the browsers your customers use despite your personal feelings on the matter. Of course, if the browser use is below a certain percentage you're comfortable with, then by all means go for it. I do.
I develop on a Windows machine because our platform is based on .Net. We have two Macs in the office that two of our designers prefer. If need be I can ask them to look at something for me. I personally do not develop for nor test for Safari on OSX so I have no idea of all the differences and challenges of developing for it. But I sure as hell don't say it's too hard to bother with.
- fellowniusmonk 15y agoWhen you run your own site your job is to do whatever you want, however you want, it's your chance to be opinionated and exclusionary, and as long as you are not begging me to invest money, more power to you. Also open source and sharing is more robust on linux and posix platforms, so people naturally develop tools they can use on their own platform, with their own workflow, and who cares if it gets ported to windows, I'm not creating a product to sell, I am sharing my personal toolset in a friendly way. Why are you complaining about the difficulty of installing a FREE opensource project on a platform that is not native to the Devs? Of course it's more difficult! Why are you complaining so loudly? Why are your expectation so entitled? Did you even bother asking for help on Stackoverflow?
- talmand 15y agoSimple, if it's an open source project that's a tool for web development and the only barrier to making it cross-platform is rather insignificant, such as vendor prefixes on CSS3 features as one example or even just proper documentation, then I'm going to complain about it. As is my right as a member of this open society we call the internet. The devs always have the right to ignore me and I'm sure many will. I'm fine with that. If we're talking about a native app and the devs don't feel the need to port it to another platform, then that's cool. Which is exactly what I said before, but you skipped mentioning that. But if they say the thing works on Windows and there's difficulty in getting it done, then there's a problem. If I have to go searching through third-party websites to get their app working, then there's a problem. If the documentation for the platform that they claim to support is outdated, then there's a problem. I don't understand why it's so bad for me to point this out. It's not like I'm saying that BBEdit doesn't work on my Windows machine and therefore it's bad software. I guess I only have the right to give criticism, constructive or otherwise, if I paid for the software? Then maybe all those complaints from the linux community aimed at Adobe for their lack of support of their platform should go away? Personally, I think their complaints are perfectly valid. It's funny, I've pointed out problems on other projects presented here and I was thanked for it. But I guess the response varies. Getting SASS working on my Windows machine did not seem as easy as it appears to be on a Mac, simply because of the difference in environments. Even just using it seems easier for some reason from what I've read. But you know what? They gave instructions on how to get it done, they were relatively easy, and I was up and running in a decent amount of time. That was a good experience, I did not feel that the devs were limiting me based on my needs for a specific development platform. Therefore, to me anyway, that is a good example of a software project meant to help in web development. But to be honest, I was not aware that I was complaining that loudly. Nor did I realize I was coming across as entitled as I thought I made it quite clear I do not think I am. Well, maybe I am about the complaining thing.