This was a classic resource used by everyone. It looks quite pared down and in a non-intuitive format. And to be honest I tried a few strains and found it lacking from the previous version.
1 Like
well if you have a more than 15 year old code base you are always making tradeoffs. You can handle it like restricting public access for security reasons. Or you ignore issues while waiting for a patch that will never arrive like a original spare part for your orginal Fort-T model in North-Korea. Without a code rewrite there are no improvements possible like having less mandatory reviews for public inputs based on user roles. Or you end like European banks who desperate looking for experts in COBOL who are able to master their 60 years old mainframe code.
2 Likes
there were yesterday some issues on the new server with email, so everything that required an email sucked yesterday
1 Like
a more than 15 years old code base makes no fun. After the owner changed I was the only one who understood the legacy code and a code rewrite was in midterm the better solution. When it comes to the lineage tree and other data-porn, it simply an database output / visualization - so something not so difficult to solve with access to the legacy code.
4 Likes
Thanks for letting us know what’s going on. It makes sense when you describe the situation. If it’s possible to easily change the lineage tree then that would solve a lot of issues people are having with the new setup
1 Like