So the joys of life have yet again taken over and not given me nearly enough time to really focus on anything. I’ve been able to slowly figure out what I want to use as the full stack, which is not what I originally had thought of. Many reasons come into play in this decision, including:
- History – While using something like MongoDB, CouchDB, or anything similar to that has become the newer thing to use, I have decided to pick a SQL based one. Now honestly it will be up to the end user to decide which they would rather have, but I will be using MySQL. However, using SQLAlchemy will offer the ability to use any of these dialects, Firebird, Microsoft SQL Server, MySQL, Oracle, PostgreSQL, SQLite, Sybase. I want to make sure that I am able to offer the ability for people to use which database they perfer.
- Future Proof – So after messing with NodeJS for back-end, and other little utilities, I have come to realize that I like using it, but hate trying to do back-end with it for some reason. I believe part of my problem is the super fast changing world of Node and NPM that causes me to actually be put off by it. Since I started we have already had a new SQL library come into play called Knex that offers great features, but yet again isn’t even Version 1.0 yet. These are the ever changing area of Node/NPM that causes me to not want to use it as much.
- Data data everywhere – I have a fondness for Data, including Big Data, and recently a big look at the world of Fintech. This has brought me the decision to use Python, and more importantly, Python 3.6.1. While I know not everyone has this, I feel that in the end it won’t be a bad decision. Python has some of the best libraries to deal with data and data crunching, as being one that is currently helping with an ERP system conversion, Data is King. Seeing all the Data and what some areas are doing with that data to manipulate it is very impressive.
- Ease of use – Python also offers huge amounts of ease of use. While some of the documentation for Python Libraries isn’t always the best, I feel that I can deal with it and learn when I need to. Being able to write fewer lines also means that I can get a MVP/Prototype of the Login/Dashboard/Plugin System to work the way I want.
Those are just some of the reasons why I am going towards Python/SQL based for the back-end of the system now. This still brings up the front end. This is always where I get so confused lately on what to use, React, Angular, Vue or something totally different. This, like Node/NPM, has turned my thoughts way too many times on what to use and to find an answer will not be easy.
This system in the end will offer the initial Login/Dashboard/Plugin System. This will then be extended by how the end user will want to use it. Maybe a user wants to just use it as a CRM, they can, or Inventory tracking/POS, they can. This is the dream of mine and feel it should be something that can be done. My initial work will be done with Inventory Management/POS system. This is what my wife has been wanting to see to track items in the home, at least the Inventory Management.
All this will be a lot of work as I’m not the most experienced in Python yet, but want to learn as much as possible. With this, I am going to go into Pyramid. While I’ve never used it, from reading everything that their site shows, it is exactly what I need. Something to allow the beginning to be easier but allow for the expand-ability that is needed. Everything they say fits what I want, so mine as well bite the bullet and try it. Well that is a slight update on what I’ve been thinking of.
And just as a reminder, I am not a writer so these thoughts are just thrown out there and put into this. Most times, I honestly don’t even reread what I write 🙂 but that’s OK to me. This has been more of a prototype blog setup, to allow me to just throw thoughts and ideas down on something. Once I begin doing the programming, I may end up making an additional spot to be able to put better posts that have had time and thought more put into them.
Now the last part is, the name, for now I will keep EDEN as the code name, however in the end I may figure out something new. Been thinking of that along with the fact that I have the newer logo to use.
EDIT: Well here is a prime example of why I’m staying away from Typescript/Node for right now, https://blogs.msdn.microsoft.com/typescript/2017/06/27/announcing-typescript-2-4/ another new version of typescript, too hard to keep up with it, Python is pretty stable and slower to update major things. Sure Typescript has great features and I agree with them a lot, but it just is changing too much.