3 ms·
Porting forwards is in my view typically done to move a project from A to B once. That can be a longer process due to complexity, but it's a phase that starts a
by detaro 6y ago
Porting forwards is in my view typically done to move a project from A to B once. That can be a longer process due to complexity, but it's a phase that starts and ends and ideally is short. In contrast, compiling "backwards" is often done for a longer time for platform support -> compiling languages to run in the browser with JS, to run on platforms that only have a C compiler, to bootstrap a compiler toolchain off a C/C++ compiler.
<EDIT> Doing it fully automatically often has problems with the usability of the source code for further development. Automatically converted code will work, but typically not look like properly human-written code in the target language. Fixing that is additional difficulty or human work, so often semi-automated is actually better. </EDIT>
At the same time, building such tools requires different skillsets than typical application development or manual porting. If you are massive, or the type of company that has uses for this skillset elsewhere, it might still be viable to hire for those skills. But for many companies, they don't want to have this problem around long-term. They do not want to long-term maintain migration tooling, they're the happiest if the migration happens and they never need to think about anything related to it again. That's a poor motivation to maintain an open project. (they'd of course love if other people had done that and open-sourced their work)
On the other hand, specialized knowledge required on a per-project basis is pretty much the perfect scenario for consulting work. And a company that repeatedly does ports for customers has an interest in a) having deep knowledge about it b) automating the work where possible, even if automation is expensive up-front c) being paid for said investment in knowledge and not giving it away for free.
- zxienin 6y ago> But for many companies, they don't want to have this problem around long-term. They do not want to long-term maintain migration tooling, they're the happiest if the migration happens and they never need to think about anything related to it again. Treating $(subject) tool to be equivalent of day 2 ops, does the trick. What makes it viable to do it with a team of (say) 6 folks? Community driven core, adopted internally by this team. So is it mostly about mindset change, or it just really doesn’t have a place in org internal engineering team setups?