@dpdonohue hardware based clinical software is the way forward. One issue though. Instead of handling all the headache of logistics and shipping & maintenance (let alone hardware issues) I reckon connecting with existing hardware will reduce a lot of pain. The partnership is good for all those hardware companies as well.
I need abigail’s advise on this. If, after careful examination, we see that React has significant benefit over Blaze, only then I want to change. But mongo will stay. I want to connect data science to our data later. Here is what I am thinking:
- Can Meteor in its current stage or with little bit of tweaking deliver the clinical apps we are going to make? That includes Now and in the foreseeable future.
- What is the cost-benefit ratio of adopting any new tech into our stack?
- The new tech in question must have benefits that can’t be had with our present tech. Any work around/hack is almost as complex as learning the new tech.
- Implementing any new tech in our stack should not create something we already have/don’t need.
Example : Is Flux useful for us ?
- The tech in question must be well supported by developers and easy to hire devs that know the tech.