Because it's slow and difficult to use compared to sketch. Plus I need my files on my drive 100% of the time and routinely work without reliable network access.
I get kind of why Figma is popular, it solves issues with sharing and collaboration. But the day to day usage is crippled by the fact it's in a browser and not a standalone app where I need it to have total control over keybindings and shortcuts for my workflow. Meanwhile in the browser, hijacking that behavior is a UX antipattern.
Sketch is just so much less cumbersome than Figma it's not even funny. It's easier to use than illustrator and Xd too.
I don't think it's as big a problem, first because everyone will have bad experiences at some point and that's a growth opportunity in and of itself. Secondly because good candidates are apprehensive about bad companies regardless of their experience level.
And frankly the market is competitive enough that you can always quit a bad job to find a better one, if you're qualified.
Sketch is a great app. It's a shame that it's Mac native, I had to stop using it when they killed off support for High Sierra.
I wouldn't be proud of building on an increasingly user and developer hostile platform, but thats just me.
> For us, the ultimate benefit of being a native macOS app is that it puts the choice in your hands.
That's... kind of a weird opinion but all the power to you. I have never felt like "choice" was a core value of Sketch, since it doesn't give me the choice to run on my hardware or software versions. But thanks for letting me own my own data.
If there's a lesson from the ongoing collapse of GE, it should be "stay the fuck out of finance."
There's an interesting take that's opposite here which I don't see mentioned, which is that software businesses make absurd margins and right now the best place to put that money is in the pocket of their employees or new employees (or overseas, or in buybacks). That money could be put to use to increase their margins through financial services but personally I don't want to be a part of that.
They're great for implementing complex language semantics like cooperative multitasking (using macros to expand yield/resume points into a state machine for stackless coroutines, for example). Or cool object systems like type classes and multi methods.
Smaller stuff like hand rolled parsers and serializers are much easier to get working fast (both time to write and time to run) using macros. Since a good chunk of my work is data flow in one form or another, I miss LISP macros a lot.
Weird not to mention acoustics. Temples, churches and venues (opera halls, in particular) needed high ceilings to carry sound before electronic amplification.
I have lived in a home with high ceilings. I find them gaudy and poor design features, unless you live alone. If you have high ceilings, particularly in open floor plans, everyone is going to hear everything all the time. Doubly true if the stair case opens up to a wide space instead of being closed off.
Lots of people in a business aren't submitting code, but that's not really my point. Depending on a manager's style they can increase synchronization overhead between team members and different teams to the point that everyone's productivity is reduced while the manager has never been busier or productive on paper.
I get kind of why Figma is popular, it solves issues with sharing and collaboration. But the day to day usage is crippled by the fact it's in a browser and not a standalone app where I need it to have total control over keybindings and shortcuts for my workflow. Meanwhile in the browser, hijacking that behavior is a UX antipattern.
Sketch is just so much less cumbersome than Figma it's not even funny. It's easier to use than illustrator and Xd too.