I was going to say this was too unrealistic, then I remembered what timeline we're in.
405 karma · joined November 21, 2010
I was going to say this was too unrealistic, then I remembered what timeline we're in.
Or "this situation sucks, that's why I'm excited. I want to lead the charge out of the darkness and into the light" or some such self-aggrandizing metaphor. Assuming, of course, you are willing to take a job whose primary function is fixing a broken team.
TO BOLDLY GO? No, motherfuckers, you go boldly.
This is what I'm talking about, for what it's worth, a programmer doesn't immediately see the utility in the tool and doesn't use it, and that's the story for 99% of the things an IDE does. It's always faster to do it yourself once, or twice, especially considering setup time and learning curve, so people don't make use of the tools. I see people using grep instead of their IDE search because they cbf to figure out how to do it in the IDE!
It's like we're carpenters who hate power tools.
I don't believe this to be true. I think the difference is graphic designers tend to use much more of their toolings' functions, whereas almost every day I'm surprised someone I work with doesn't even know some IDE feature was possible, let alone how to use it. Hell, almost every frontend developer I've ever seen use either VSCode or WebStorm orchestrates everything from the built-in terminal and is baffled when they never see me use one - because it's all configured via run configurations, and that's a _basic_ feature.
I used Go extensively at my last job and I was left feeling that there were pretty much always better choices. If you care about developer velocity with your more unskilled engineers, Go is a bad choice for a multitude of reasons. If you're going to need the performance over something else, the JVM is right there, and so too is Rust.
Github is and always has been a closed platform. It's also responsible for the largest explosion of open source activity from any single source in the last twenty years. Your argument relies on the assumption that the cost of migrating away from Github is a cost a FOSS project can pay and survive, which is a pretty heavy assumption as far as those things go. Even if the alternatives were comparable in UX, and they're not, there are entire ecosystems (Node, Golang, RubyGems, brew, etc.) that explicitly depend on Github. If you measure your software's success by any metric other than how well it aligns to your ethics, it's hard to justify anything but Github for a FOSS project.
Most people, IME, write FOSS software so people can find and use it. I remember the era when SourceForge was more-or-less the best thing you could hope for as far as central repositories were concerned, but they weren't much more than free static web hosting. I remember how difficult it was to contribute to Apache projects because figuring out their esoteric source control and patch process was so daunting. I remember googling for software packages to use and not having an easy route to quickly gauge whether its quality was worth investing further research. I wouldn't like to go back to a world where everything was hosted on free software if it means losing all the knowledge that exists in that one place.
There definitely seem like more important windmills to tilt at than pointing at the engine that drives the entire FOSS ecosystem and saying it's not good enough by the most stringent of ethical standards.
I don't know a single person in any professional context that doesn't have one of Slack, Teams, or Discord installed.
I may be overstating how much smaller your pool is, but to say that choosing Discord or Slack doesn't grossly expand your reach is just naive.
I'm sure this project's community would welcome a contribution to mirror their git in a read-only state somewhere else, because why wouldn't they? Similarly, I'm sure they'd be fine with collaborating on setting up bidirectional chat bots so you can communicate with them as you want.
But to expect these things from a nascent project seems ridiculous. We're not talking about React or Spring here, we're talking about a brand new project who should be investing as much time as possible making their software work, not catering to every potential communications niche.
If you've decided that contributing to someone else's code on Github violates your sense of ethics or privacy, that's well within your rights and I respect you for it, but you must have enough self-awareness to recognize that that puts you in the far extreme of digital ethicists. And that shouldn't come with an expectation that your ethics have been catered to.
I don't think we've evolved to live in small groups.
This isn't a huge issue, but it's one of the larger issues why FOSS alternatives are not often as well received as their proprietary counterparts (see: unix). Consumers/users should be the first/only consideration when designing user-facing software, but it's a rare sight to see in FOSS. I wish more FOSS developers cared about the software instead of the code, because the difference manifests in decisions like this.
> I have the sense things I have said have triggered an emotional reaction on your part, and a lot of what you are saying is really more about your own emotions than about anything I have said.
You're so very close to getting it. This entire interaction has been incredibly frustrating to you, because I engaged in it in bad faith from a place of (supposed) irrational emotional anger, same as you described. I called you out on a personal failing, and it caused you some level of frustration or hurt. Even when I have over-emphasized the point and flipped the tables, you're still not getting it. You treated that poor lady horribly, more horribly than I have treated you (unless you really think a random curse word on the internet is more devastating than being told in as many words, to your face, that you're too stupid to do your job, which is what you described your interaction as) and you're ready to back out of this interaction. The tables are reversed and you think I'm an asshole. What do you think that lady thinks about you?
Start by convincing paying customers that cyber security and/or their privacy are important.
Empathy is a skill high-functioning people on the spectrum can learn. I spent a lot of time in therapy as a child pretty much solely focused on learning empathy. Your behavior showed a complete disregard for her emotional well-being and _her feelings_, which is synonymous with a total lack of empathy. That you are capable of commenting on Hacker News and getting married means you could learn the skill too; everyone has to learn it, like any other skill, and it doesn't come easy to people on the spectrum.
I understand the double empathy problem and I do not agree with it whatsoever. My exposure to adults on the spectrum who wear their autism as a badge of pride or disclaimer in conversation do so as a means to dodge responsibility for their part in a social interaction because it makes them uncomfortable.
> Finally, where's your empathy for me in your comment?
Doesn't feel good to have your intellectual / personal short comings aired out in public does it?
> What does that make you?
Speaking how you speak to others, but to you. As a narrative decision.
I was around when React took off. People may have been aware of it because of marketing, but every web developer I know wanted to immediately switch to it, even before class components, because it represented a fundamental paradigm shift in how web applications would be built, and it was self-evidently better than anything else anyone had thought to suggest.
The was a popular talk because _it was true_. React changed frontend web development from a tedious chore offloaded to the junior-most members of your team and elevated it to something everyone takes seriously.
It was a very, very long time before there was anything useful competing with React. Nothing really started to compete with the sheer volume of people who wanted to work with it until JSX proliferated across the frameworks. Just JSX alone was enough to convince people to switch to React.
This isn't being blunt, this being a straight up dick. I hope you went back and apologized for acting out later. If this is your definitions of bluntness and is standard fare for your behavior, you are actually the capital A Asshole the comment chain is referring to. It's not about the truth of the matter, it's the total lack of empathy in your entire comment about this interaction.
There isn't infinite time and money in the world. Every hour making one feature more stable means an hour not invested in another. Flexibility and control are just additional features. If you want to change the system font, you have to test (and support) a much wider array of things, especially if your UI guidelines are as restrictive as Apple's. Every piece of control you expose to the user increases the engineering cost of writing and maintaining the software.
And frankly, if more people wanted that level of control, this year TRULY would be the year of linux on the desktop. But they don't.