![]() ![]() Don't switch to Ruby on Rails though-it is a small, dying community of enthusiasts.ĪSP.NET Core is a great backend framework, the community is large and you can always find answers however, according to the StackOverflow developer survey, it is not desirable for the majority of programmers. Unless you are willing to work on the community apps, Django may not be for you.Ĭompare the active community sizes of Django apps to Ruby on Rails apps and you'll see very active communities with Ruby on Rails and small Django communities. You can get done what you want with just about any modern framework and language.ĭjango is fast and easy to learn but as your website grows you will need more and more community apps whose release cycles do not keep up with Django. PS, I would recommend Vue over React also for a well organized front-end. Net so I can't give a comparison except of course, the obvious one, portability, as Python is platform-independent. With a React frontend, you would be using the Django REST Framework ( ) so you may find that you have to overwrite a lot of the methods here as the defaults are fairly basic CRUD operations which don't really support nested relationships very well. One hassle worth mentioning is the database migrations support which can sometimes mess up during development but there are workarounds. I have found it more stable with updates than other frameworks (particularly compared to the NPM world such as React which so often descends into dependency hell when a version of something is updated). If you are wanting to incorporate python-based data processing (or cython), it is relatively easy to write a backend plugin. It has a logical workflow and organized structure and it comes with a high level of security (if you import the appropriate backends). ![]() Having worked with many J2EE database applications in the past, I now turn to Django if I can and the project allows it as it is so quick to get up and running. the freelancing options are virtually non-existent (and I would expect them to stay limited, as rust is better for long-term software than prototypes) See more it's harder to learn (expect to put in years) it's super versatile (you can do high-perf system stuff, graphics, ffi, as well as your classic api server) it's got potential to grow big in the next year (also with better paying jobs) it's satisfying to work with (after the learning curve) Then, later, for back-end programming languages, Rust seems like your best bet. it's everywhere and not going away (well not yet) can also do back-end if needed (I would personally avoid specializing in this since there's better languages for the back-end part) more freelancing opportunities (starting to work short after a virus/crisis, that's gonna help) I would start focusing on Javascript because even working with Rust and Python, you're always going to encounter some Javascript for front-ends at least. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |