JupyterLab is ready for users

Re:JupyterLab is ready for users by esmi on Tuesday February 20, 2018 @01:50PM (#16422848)

My workflow is very similar. But I am often forced to use matlab for simulation because the vendors I work with only deliver matlab libraries. They choose matlab because many engineers know how to use it and have licenses for it but also it gives mechanisms to protect IP which is a big deal to many firms.

https://www.mathworks.com/help/matlab/matlab_prog/protect-yo...

[ Parent | on HN ]

Re:JupyterLab is ready for users by tsaoyu on Wednesday February 21, 2018 @07:04AM (#16428805)

I assume this situation also holds true for those using LabView to build their virtual instruments. IP wasn't really an issue for us since we have decided to open-source our project to broaden the knowledge of the public: https://github.com/Maritime-Robotics-Student-Society/sailing...

As a note, in Python, there is pyconcrete for code encryption. https://github.com/Falldog/pyconcrete

[ Parent | on HN ]