3 ms·

> ...it's crazy how much effort is wasted because everybody is writing separate mission control, monitoring and data analysis applications that do 95% of the sa

> ...it's crazy how much effort is wasted because everybody is writing separate mission control, monitoring and data analysis applications that do 95% of the same things, each with its own horrendous UX/UI, idiosyncrasies and bugs. Heh, sounds like they have a lot in common with JavaScript frameworks and web development in general. With this observation in mind I doubt making mission control "web based" will rectify the situation...

tekkk 8y ago
What do you mean? I save a lot of time in web development using solutions created by others. I don't think this problem is unique to JS/web development but to software development as a whole. "Not invented here" syndrome is quite prevalent in a lot of areas and sometimes lack of options doesn't mean it will make the product any better. Quite the contrary it can mean that everyone is using the same buggy solution because there are no alternatives. I do not know the details of mission control technology but my uneducated guess would be that this is a cultural/management problem in these organizations. Top-down hierarchy with very large resistance to change would make introducing of new ideas (open source solution in this case) a tough job for any single actor. Also the IT-contractors or companies benefitting from selling these solutions are probably doing everything they can to keep the status quo as it is.
- TeMPOraL 8y ago
  > What do you mean? I save a lot of time in web development using solutions created by others. How much time do you lose keeping track of those solutions and their dependencies? The JS world has probably the hugest fragmentation problem in software history. Every level in the stack is rapidly evolving, constantly spawning multiple half-baked alternative solutions to the same problems. I think GP's point is simply that if similar things are happening in NASA on small level and are considered a problem, then switching to a technology ecosystem that is a living embodiment of those issues isn't going to help.

tekkk 8y ago

What do you mean? I save a lot of time in web development using solutions created by others. I don't think this problem is unique to JS/web development but to software development as a whole. "Not invented here" syndrome is quite prevalent in a lot of areas and sometimes lack of options doesn't mean it will make the product any better. Quite the contrary it can mean that everyone is using the same buggy solution because there are no alternatives. I do not know the details of mission control technology but my uneducated guess would be that this is a cultural/management problem in these organizations. Top-down hierarchy with very large resistance to change would make introducing of new ideas (open source solution in this case) a tough job for any single actor. Also the IT-contractors or companies benefitting from selling these solutions are probably doing everything they can to keep the status quo as it is.

TeMPOraL 8y ago
> What do you mean? I save a lot of time in web development using solutions created by others. How much time do you lose keeping track of those solutions and their dependencies? The JS world has probably the hugest fragmentation problem in software history. Every level in the stack is rapidly evolving, constantly spawning multiple half-baked alternative solutions to the same problems. I think GP's point is simply that if similar things are happening in NASA on small level and are considered a problem, then switching to a technology ecosystem that is a living embodiment of those issues isn't going to help.