4 ms·

My team started being more serious about our switching from .NET to a mix of Django, Flask and Vue.js this year, so I've been focusing on those. I personally pl

by jaabe 8y ago

My team started being more serious about our switching from .NET to a mix of Django, Flask and Vue.js this year, so I've been focusing on those. I personally played around with GraphQL (Apollo, Yoga and Graphene) for a while, but ultimately I didn't find a good use case for it in our setups and kind of left it at that. Our 2019 will be spent on building our AWS and Azure skills along with container setups, as we look to move further away from our .NET and IIS heavy setup. With an increased focus on getting better with Python and Vue, possibly moving our JavaScript to Typescript. I don't have anything negative to say about .NET, in case anyone was wondering. I think .NET core and Blazor.NET are especially interesting. We've just had so much more fun with Python and that's frankly really motivational. We're also using more and more Python when we do data-driven development, incorporate GIS stuff or do various forms of scripting, so it sort of makes sense to consolidate.

closed 8y ago
When have you been using Django compared to Flask? I'm curious, since I often use Flask + vue, but haven't used Django much.
- jaabe 8y ago
  When we know the project is going to see a lot of end-users that'll need their own "profile" styled page and/or if we know we'll see a lot of database changes over time. Which hasn't been a lot of times yet, if I'm being honest. One example that I can share, that would have also been a good Django candidate is our system for handling employee absence. When it launched it only let you report the two types of paid vacation we have, but being the public sector of Denmark, we actually have around 80 different types of legal absence, with various rules attached, and we knew we'd want to add more over time. We also knew every employee would need their own profile to keep track of their accounts, and we knew some managers would want to outsource the responsibility to secretaries and such. So that's what would be an obvious Django project to us, but it was build in .NET because that's what we were most comfortable with at the time.
  - closed 8y ago
    Thanks for your response--it's helpful to hear! I've mostly been using flask for simple APIs / dashboards, but have wondered lately whether a more "batteries included" approach like Django could be helpful once a db / more logic is added..
- douglaswlance 8y ago
  Django is great for "batteries-included" development. It has a lot of extra stuff included in the framework that you might not need for a smaller app, but if you don't care about that extra overhead (or you need to use it) then Django is a great choice. It also has a fantastic ecosystem of "apps" (what Django calls plugins or packages) that you can drop into your project which can save a substantial amount of time; which makes it great for consulting work.
bpicolo 8y ago
I've never had to write .NET as a day job, but Dotnet Core is tons of fun for me. I think it's a super productive environment. I did the opposite as you - started with a tremendous amount of python
Pxtl 8y ago
Having done both Python and .NET, Im surprised to hear somebody migrate in the opposite direction. Python may have a better history as an open language for web dev, but it feels like .NET has a far brighter future.

by jaabe 8y ago

closed 8y ago

When have you been using Django compared to Flask? I'm curious, since I often use Flask + vue, but haven't used Django much.

jaabe 8y ago
When we know the project is going to see a lot of end-users that'll need their own "profile" styled page and/or if we know we'll see a lot of database changes over time. Which hasn't been a lot of times yet, if I'm being honest. One example that I can share, that would have also been a good Django candidate is our system for handling employee absence. When it launched it only let you report the two types of paid vacation we have, but being the public sector of Denmark, we actually have around 80 different types of legal absence, with various rules attached, and we knew we'd want to add more over time. We also knew every employee would need their own profile to keep track of their accounts, and we knew some managers would want to outsource the responsibility to secretaries and such. So that's what would be an obvious Django project to us, but it was build in .NET because that's what we were most comfortable with at the time.
- closed 8y ago
  Thanks for your response--it's helpful to hear! I've mostly been using flask for simple APIs / dashboards, but have wondered lately whether a more "batteries included" approach like Django could be helpful once a db / more logic is added..
douglaswlance 8y ago
Django is great for "batteries-included" development. It has a lot of extra stuff included in the framework that you might not need for a smaller app, but if you don't care about that extra overhead (or you need to use it) then Django is a great choice. It also has a fantastic ecosystem of "apps" (what Django calls plugins or packages) that you can drop into your project which can save a substantial amount of time; which makes it great for consulting work.

bpicolo 8y ago

I've never had to write .NET as a day job, but Dotnet Core is tons of fun for me. I think it's a super productive environment. I did the opposite as you - started with a tremendous amount of python

Pxtl 8y ago

Having done both Python and .NET, Im surprised to hear somebody migrate in the opposite direction. Python may have a better history as an open language for web dev, but it feels like .NET has a far brighter future.