sciprojguy
sciprojguy on Hacker News
"A big steaming pile of management work" might be a more apt description... ;-)
Former manager here - you'd be very surprised at how much effort it takes to act as a human shield for your developers to keep the interruptions to a minimum and keep their roadmap stable. It's work, and it can be delicate. Try running interference with a company president who wants to bother your developers when they're trying to get something out the door, or trying to make sure stupid ideas die before they become your team's problem.
Don't forget sales/marketing overpromisers and nosy executives who get in the developers' hair.
In a perfect world you would be right, but spend some time with a bunch of clueless executives who don't know how clueless they are (or are trying to pretend they do have a clue) and you'll realize there's no amount of context that will help them realize why there's bad news.
Not necessarily. macOS and iOS have multiple accommodations for users with accessibility needs, from dynamic type to UI element voiceover plus pretty decent speech-to-text recognition and haptic feedback. Developers that want to take the time can build apps that can be effectively used by users with visual and/or auditory deficits.
This line of argument sounds like a petition-gatherer trying to get signatures for a niche local issue and getting frustrated that they can't get enough people to see things their way.
"I'm spread too thin" isn't an actual lie as much as it's a reframing. Working with difficult people can take a lot of mental energy, which ought to be considered part of the work effort. It's the polite way of saying "I don't have the bandwidth to do the work and manage my way around your issues, so best of luck finding someone who does have that bandwidth" the same way that "Thank you for your input" is a polite way (in the business world) of saying "That was the dumbest thing I have heard all day".
This reads like an amateur with a grudge.
Was this a Seagate drive?
"Technologies like objective C, C sharp, Azure or swift are designed so you can not escape the company platform. So easy to get in, so hard to move your code to other platforms once you have been programming for years on them."
FYI, Swift is available on Linux and Windows along with a significant chunk of its core libraries (e.g. https://github.com/apple/swift-corelibs-foundation) and app frameworks such as Vapor (used for writing web apps and APIs).
You do not have a "duty to your job". Employers love it when they can get their workers to think that way because it raises the threshold amount they can overwork and over-stress you before you've had enough and quit. You have to protect your personal time and your mental and emotional health. (I have had to learn this lesson a couple of times in 40+ years as a software dev.)
It helps a lot to think your management knows what it's doing. If you're stressing out on the latest likely "swing and a miss" feature that you think they picked using a dart board and ransom-note cutouts from magazines, you can end up burnt out for a good long time.
"Samsung Branded iPhones"? This can't possibly be a thing.
How can this possibly go wrong?
Pretty sure you're wrong. If you drive, the commute can be a stressful waste of time.
I think you're right, and I think it will motivate those of us who want to work remotely to quit and find companies that have that as their culture and let the "back to the office" folks become more homogenized.
Already you sound adversarial, like this is a battle of work cultures and you want your side to win. You say things like "return to work", as if the people who are working from home aren't already working. Did you mean your comment to come across this way?
FWIW, the styling system mainly talks to the parameterized native components that the build system pulls down from GitHub. You can do the same kind of thing in SwiftUI using View Modifiers.
You make it sound like users are switching among Windows, Linux, macOS, Android and iOS all the time so the app UI has to have the lowest common denominator. By and large they're not and as such the native UI is the consistent UI: the apps launch the same way, you know how to get to settings or the trash can and the gestures all do pretty much the same thing to get the same result.
It's kind of odd that you mention Apple as a company that has "ditched standards", considering it's got very public, detailed design standards and has had them for a very long time.
https://developer.apple.com/design/human-interface-guideline...
The web is where you really get that kind of grab-bag of mismatching (or absent) UX affordances. Remember when clickable links were all blue underline text? I do. Those days are gone, and for way too many pages the only way to tell if something is clickable or not is to move the mouse over it and see if it gives you the finger.
"Smart Approaches to Marijuana". Right. Prohibition failed when it was tried with alcohol; it's been failing with cannabis for decades and decades but these modern-day bluenoses don't want to let it go.
This. If you're willing to routinely go "above and beyond" your normal work hours, then in management's mind that "above and beyond" will become your normal work hours and it will factor into their planning.
You might not have seen this:
https://developer.apple.com/swift-playgrounds/It's pretty nice to be able to build entire Swift playgrounds on your iPad, then share them with your Mac/MacBook. The IDE is simple and very straightforward, and it's useful for prototyping things on your iPad or iPad Pro.
No, it isn't always laziness.
Sometimes it's politics (I had a colleague leave a job because the new director of development mandated they rewrite their flagship enterprise apps in React Native because he got a song and dance from a React Native trainer/consultant and wouldn't listen to the people who knew what they were talking about).
Sometimes it's different priorities (a meetup buddy of mine some years ago had to write apps in PhoneGap because "We're in the oil bidness, not the app badness").
It isn't always "the best allocation of limited resources", either. Apart from having to do extra work to make the UX close to native (which isn't trivial), using a "cross platform" solution means you've just included a giant third party dependency that you don't control or maintain. Call it FUD if you want to, but in the forty-odd years I've done programming/development that's never been a good bet. If resources are really limited, the best bet is to have a decent design and very clear (reasonable) expectations and pay someone good to execute them.
Why, exactly, are they evil? It's not as if people who buy Apple (like me, and I develop for iPhone/iPad too) don't know what they're getting. I like the walled garden Apple has because:
* It makes my life as a developer much easier. I only have one App Store to aim at, and with a few hiccups here and there from inexperienced or overzealous reviewers the guidelines are pretty clear. If I had to design for half a dozen or more apps I'd have that many more versions of guidelines to worry about.
* I don't need to worry nearly as much about scam or knock-off apps siphoning off users, since Apple is proactive about that. Not perfect, but very proactive.
Those are just two off the top of my head. There are more, but I'm getting hungry.
"I feel that users will only install the necessary app from the alt store and not anything else."
Have you ever had to wipe a relative's computer to get rid of the malware-infested browser toolbars they installed, not knowing any better? Or worse, pay a ransom in bitcoins to unlock the billing systems that help control a gasoline distribution pipeline? You may be somewhat overestimating the sophistication of users when it comes to technology.
Long-time iOS developer here who does not want cross-platform dreck to become the standard. UIKit and SwiftUI are deep frameworks that let you build really great user experiences (if you're willing to put in the work to learn them), and Apple spends a ton of time and money making sure they can work together and build an iOS app that looks and feels like an iOS app, not someone's crappy "web site in a native wrapper" or "several extra layers of abstraction to hide an API and god help you if you need to debug an API problem" approach.