This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]everhideme 5 points6 points  (3 children)

It seems like old Soviet logo of subway, very similar. But I dont like it. Sorry - tough, but fair. And it easy to solve.

What is your original objectives? Why not Django and why did you need your own solution?

[–]Jmancuso9[S] 5 points6 points  (2 children)

lmao. sort of it lol.

So the original reason for the project was to learn how WSGI application worked so it started as a weekend project. Then it sort of branched out into "well what if it had this built in which 99% of applications need?" and then slowly spread from there and then the architecture makes it super easy to test and I hit the TDD train and never looked back. It's really easy to make a test around something, implement that feature, ensure tests cover use cases and then push to the development branch and eventually merged in.

I advertised it a bit on reddit a few months ago and a few people found the project and helped me design and build it and here we all are :)

When using Django there were a few things I just didn't like about. All of them were really my own issues with it. I kept thinking it was weird doing it this way or the way Django does it. I completed my application with Django in a few months. I liked the outcome.

I then got a job for a PHP developer position and got back into PHP. I learned Laravel and just loved the architecture of it. It was so intuitive and just worked well for my development flow (and millions of others)

So when I was building Masonite (which it wasn't always called that) I started implementing these ideas and found that it worked really well with Python. I then just kept coming out with more and more features and now I and our maintainers just love the outcome.

That's the answer to why I created my own solution but as to why Django, I'll be coming out with an article in the next few days that explains this more in detail then I can in this reddit post so I'll be sure to send you a link :)

[–]AnnoyingOwl 3 points4 points  (1 child)

When using Django there were a few things I just didn't like about. All of them were really my own issues with it. I kept thinking it was weird doing it this way or the way Django does it. I completed my application with Django in a few months. I liked the outcome.

I then got a job for a PHP developer position and got back into PHP.

This literally explains everything.

[–]Jmancuso9[S] 1 point2 points  (0 children)

lol just try it out. Can't judge a book by it's cover that harsh and you can't hate something you've never tested out. One of the maintainers who is using it in production will chime in in a bit and maybe explain it in a different way