> It is a call for more communication and understanding of different opinions.
It's a poorly argued rationalization for antisocial behavior from someone with a bad case of engineer's disease.
> Since I’ve posted it this article got flagged and unflagged multiple times, the first flag appeared within minutes (i.e. the user pressing the button did not even have a chance to read the article).
You don't have to eat the whole apple to know it's bad.
> I wonder what made people so aggressive and short-tempered about different points of view recently.
It might have something to do with the ongoing pandemic. I'm really not interested in yet another article from someone who's too precious to be vaccinated.
> Back in college, I would go to house parties and bars and do everything that everyone else was doing; the only difference is that I would have a Coke in my hand instead of a Rum & Coke.
I have found that I get fewer questions about my drink if I have the bartender put a lime in the Coke.
> My guess is that the customer here is asking because of a mandate to prefer open source solutions wherever possible.
I don't think that HPC or the DoE have anything close to such a mandate. My guess is that the request comes from a a user who wants to try compiling their code with gfortran.
> AWS then stopped providing service to Parler due to the content they were hosting exposed by this action. Well within their rights! But they excuse the same sort of content hosed by Twitter....
> However, the manager of the other group should get some management training. He did a piss poor job at communicating. All it would've taken is explaining the group's prioritization and roadmap and the OP would've not left with "THIS COMPANY CAN'T DO SHIT!" feeling.
My impression of the OP is that he expects other teams to drop everything and make the change. He may have been told about the roadmap but feel that his project is more important. That seems more likely than the following excerpt from the post.
> So I reach out to the manager and ask what is going on. This is a simple task, I said. Why does it take an entire quarter for your team to deliver? He doesn't have an answer.
> I'm working on migrating our apps to the parent company's VM launching and deploy platform. Should be fairly straightforward, I think. Unfortunately, the deploy tooling isn't entirely compatible with our app so I ask the team if they can implement $X feature to support our app.
It's probably easier and quicker to change the app to work with their platform. If nothing else, it's going to be much easier to staff the project; your team knows the app.
> The first engineer I talk to doesn't even attempt to answer my question but redirects me to their manager. Ok, that's odd, I think, but whatever.
> Manager says sure, just fill out this feature request doc. It's a Google Docs template with 4 (!) pages of required documentation to just explain why I want this feature implemented. It asks for my team name, the motivation, why I can't solve the problem some other way, yada yada...ok, I guess it's good to document your work, so sure. I fill it out and submit it.
This strongly suggests that ad hoc feature requests are or have been an issue for the team. It's also a good way to weed out requests that the requester isn't serious about or has an available alternative.
> No response after two days. Then I get an automated email that their skip level manager has approved the work. Huh? This is followed by an email that the team's eng manager approved the work. Why do two layers of management need to approve work on something they have no knowledge about?
These managers are running interference for their team so they can get work done.
> Finally, after many rounds of arguing about why this needs to be done in the first place (ahem: you told us to migrate to your platform, and it literally does not work for our app), they quote us a delivery timeline of end of Q1 in 2022.
Most development teams have a backlog; I'd be concerned about the work quality of one that didn't.
> At this point I am in absolute shock. This should take no more than a few days to implement.
The change might take a few days but the team already has a backlog of WIP (work in progress) (http://www.leanmanufacture.net/leanterms/wip.aspx). The time to completion is based on the other tasks in the queue. If the migration needs to happen sooner then that's between your manager and the manager of the other team.
> So I reach out to the manager and ask what is going on. This is a simple task, I said. Why does it take an entire quarter for your team to deliver? He doesn't have an answer.
Every task is simple when you aren't the one doing it.
This was a bad move tactically; calling him out is not going to get you the results you want.
> I tell him I'm happy to fix the issue myself, if they link me to the relevant codebase. "It shouldn't be too hard to dig in and submit a patch," I think to myself. He says he cannot give me access to the codebase for compliance reasons, and that only members of his team have R/W on that repo. What???
Maybe they don't want to support bespoke features for your app. You can check in the code and be done but they're stuck supporting the change forever.
If it's an enterprise (https://zwischenzugs.com/2018/10/02/why-are-enterprises-so-s...) the latter will be a much easier sell to management. Paying for support is a given but contributing developer time will require many approvals from different departments if it can be done at all.
> Correct me if I’m wrong, but aren’t there open source licenses that don’t permit unauthorized distribution? If so, couldn’t they safely release the source code without worrying about competition from forks?
They would still be faced with knock-offs that either copy code or violate the license; Paint.net (https://en.wikipedia.org/wiki/Paint.net#History) is an example of this happening for an open source project.
> If information security people would spend the same amount of time they are spending complaining about this vulnerability trying to educate their organisations on the importance of supporting open source solutions they depend on we wouldn’t be in this situation.
Security teams are stuck with securing the tire fire; they didn't choose the library or platform. If anyone should be advocating for supporting open source, it's the developers who benefit by using open source libraries.
> The company that created Java went out of business and was sold to Oracle for a fraction of its original worth. So Java was a business failure -- or at least I'd be interested to see someone defend Java as a business success.
Sun and its peers declined because PCs running Linux became good enough; selling commodity hardware is a different business model (https://yarchive.net/comp/sgi_market.html) and it's incredibly difficult to move down market.
Oracle acquired Sun because they didn't want Java be owned by a competitor (https://www.reuters.com/article/us-oracle-alphabet-trial/ora...). Java was also why IBM offered to buy Sun; it seems hard to consider Java a business failure when it's most of the remaining value of the business.
It's a poorly argued rationalization for antisocial behavior from someone with a bad case of engineer's disease.
> Since I’ve posted it this article got flagged and unflagged multiple times, the first flag appeared within minutes (i.e. the user pressing the button did not even have a chance to read the article).
You don't have to eat the whole apple to know it's bad.
> I wonder what made people so aggressive and short-tempered about different points of view recently.
It might have something to do with the ongoing pandemic. I'm really not interested in yet another article from someone who's too precious to be vaccinated.