i dont get it. I if am taking a dependency on database or another class and i mock it using its interface, what is the harm in it?
Essentially i have tested that given my dependencies working correctly my class would also work as expected.
so essentially if i have a VM, i can just install the apps i require and then use them for my business. This sounds great but then I need to make sure i am monitoring and debugging it if something breaks ?
a design decision would come from collaboration, sure you can get 1st draft ready in 10-15 mins then re iterate it 1 or 2 times to see all of its pro's and cons are visible to you but then you would need all stakeholder's time to get it through
I am curious to know how python is transpired in to JavaScript for tricky cases involving promises/async await
Since python usage is quite different from javascript and for promises it doesnt even exists.
actually, as per the docs the framework is converting python code to Javascript. So you would need to JS skills to debug.
Most of the problems in web front have been solved in JS (think CSS styles, state management)
re-writting it in python would be pain, especially when everything compiles to js
But wont it be that in real life no one would want to run a voice command which consumes lot of CPU and battery as opposed to making a network call to a service which has this model hosted ?
Agreed that this can always be improved and hardware can get more efficient and better to but at the end of the day, would it ever be better then an API call ?