I am not entirely sold on “isomorphic” code. While it might be handier to have your full stack in one language, I would argue it’s less common than we think to have people working both in the back-end and front-end. Even if the gap is closing in between the two, they still focus on fundamentally different concerns. I think “Isomorphic” code can be…
Been thinking about this reply a bit. I’m curious, what, in your opinion, would be “solid” reasons to choose one stack over another? I feel like we provided good reasons, albeit slightly contextual ones, but your comment rings true nonetheless.
Cool answers below! I would top it off with Scott Hansleman’s podcasts (https://www.hanselman.com/podcasts/) and the officials .net core docs (https://docs.microsoft.com/en-us/dotnet/core/tutorials/)
By the looks of it, it seems like most of the pains you encountered where linked to how the project was built, not with what? TBH, I haven’t done quite a lot of MVC.net, so I don’t have extended experience backing up this reply (we’re mostly using .NET web APIs).
Appreciate you dropping some relevant feedback though!
Great, relevant reply, Nick — thanks for taking the time to share your thoughts & experience.
I think it’s important to stress that the first reason why we built our app with .NET was our founder’s fluency and efficiency with it. At the time (2013), both tech & business constraints put us in a position where we needed to…
I’m sorry you feel like the post didn’t live up to your expectations, really.
Tried my best to distill and vulgarize API knowledge, which is no small task hehe!
However, I actually did provide examples. Sorry for asking, but, did you read the post in its entirety…