Post History
I largely agree with Olin Lathrop's answer. However, I think questions should be on-topic also if the trends have no direct technical motivations, on condition that the reasons can be backed by ha...
Answer
#2: Post edited
- I largely agree with Olin Lathrop's answer.
- However, I think questions should be on-topic also if the trends have no direct technical motivations, on condition that the reasons can be backed by hard data in the context of a potential or actual design.
- For example, imagine you are planning to design a tool that needs, say, an UART to interface X converter chip.
- Maybe the interface X is being replaced by the new standard Xv2 (for pure marketing reasons), or the MIX999X chip you intended to use is being phased out by its manufacturer in favor of BFG888X because of a recent acquisition of "Macrochip Inc".
If these facts can be backed by hard data, such as company statements or statistics from reputable sources, then I think they should be ok, since its all part of a sound design planning phase.Of course the questions and the relative answers should be well-written, so as to foster people to learn *why* and *how* an engineer has to cope with market forces when designing a thing.- Otherwise the answers could get too much opinionated (e.g. "I heard that Macrochip could be acquired...") and really unsuitable for this site.
- I largely agree with Olin Lathrop's answer.
- However, I think questions should be on-topic also if the trends have no direct technical motivations, on condition that the reasons can be backed by hard data in the context of a potential or actual design.
- For example, imagine you are planning to design a tool that needs, say, an UART to interface X converter chip.
- Maybe the interface X is being replaced by the new standard Xv2 (for pure marketing reasons), or the MIX999X chip you intended to use is being phased out by its manufacturer in favor of BFG888X because of a recent acquisition of "Macrochip Inc".
- If these facts can be backed by hard data, such as company statements or statistics from reputable sources, then I think they should be ok, since it's all part of a sound design planning phase.
- Of course the question and the relative answers should be well-written, so as to foster people to learn *why* and *how* an engineer has to cope with market forces when designing a thing.
- Otherwise the answers could get too much opinionated (e.g. "I heard that Macrochip could be acquired...") and really unsuitable for this site.
#1: Initial revision
I largely agree with Olin Lathrop's answer. However, I think questions should be on-topic also if the trends have no direct technical motivations, on condition that the reasons can be backed by hard data in the context of a potential or actual design. For example, imagine you are planning to design a tool that needs, say, an UART to interface X converter chip. Maybe the interface X is being replaced by the new standard Xv2 (for pure marketing reasons), or the MIX999X chip you intended to use is being phased out by its manufacturer in favor of BFG888X because of a recent acquisition of "Macrochip Inc". If these facts can be backed by hard data, such as company statements or statistics from reputable sources, then I think they should be ok, since its all part of a sound design planning phase. Of course the questions and the relative answers should be well-written, so as to foster people to learn *why* and *how* an engineer has to cope with market forces when designing a thing. Otherwise the answers could get too much opinionated (e.g. "I heard that Macrochip could be acquired...") and really unsuitable for this site.