3 ms·
Are you under the impression that rebuilding the whole thing on any of the popular development options currently available would result in lower maintenance cos
by fencepost 8y ago
Are you under the impression that rebuilding the whole thing on any of the popular development options currently available would result in lower maintenance costs? Or a more open system?
Let's say they rebuild it with a Ruby backend (or maybe Go? That's trendy these days), a bunch of React (or vue, or maybe whatever's current for Angular), Postgres (or MariaDB, maybe Oracle's MySQL, maybe even Mongo), maybe throw it on some Linux boxes with Apache. In 20 years that's all going to sound like "We built it on Notes and now pay $7500/month in maintenance and update costs" along with everything that'll happen in between when ECMAScript 10 deprecates a bunch of language features.
Could it be better? Absolutely. Should the current system be kept and extended? Heck no. Is data migration a significant issue? Only in that it's a very complex system with a huge range of different types of structured data. They have programmatic access to the raw data, dumping it out is logistics.
- saagarjha 8y agoI meant open as in not proprietary. It's a lot easier to migrate an SQL database than a Lotus one, because one is open and people have written code to allow data to be exported.
- v-erne 8y agoActually its not true - notes (or rather domino) data metamodel is really simple (except for rich text maybe). The real problem is lack of schema which ecourages people who dont know better to build horrendous things. And if there is no schema and no documentation then is it really notes fault that migration is sisiphus work?