3 ms·

Flask & Sinatra were great at stripping down the "uber" web frameworks like Django/Rails. 10/10, would recommend. Bring your own templating engine, ORM.

by mslate 5y ago

readonthegoapp 5y ago
i been messing with Laravel lately, and it's ass. and/or the entire modern stack is ass. i actually had this app built for me, and i asked the dev to try to strip out as much shit as possible, including, obviously, tailwind. dev did a good job, but it's still a disaster. flask looks like a dream comparatively. but. is there a middle ground? i was a product manager-type on a (python) pylons pyramid project -- https://trypyramid.com/ https://trypyramid.com/ -- "the start small, finish big, stay finished framework" -- the message sounds good. seemed fine, but i wasn't a dev on it, and we still had plenty of moving parts for what was a relatively simple e-commerce cms (that, admittedly, had a lot of functionality). what i really want is a straightjacket -- some framework that says, 'oh, you want to plug in a different templating engine? how about fuck you? will fuck you work for you?' but i guess that doesn't earn many github stars. if i had to pick one or recommend one with no other qualifiers, i'd pick sinatra. that way i could do it my way.
- skydhash 5y ago
  The fact is, a framework can be good in a team where you have junior developers. When I started with PHP, Laravel seems a god send. You don't even have to learn PHP that deeply, as they provide a quite consistent playground to add your business logic. It's when you got experienced, you begin to notice the bloat. I don't know how it impacts performance, but I've seen many juniors shoot themselves in the foot where there's too little constraint. Nowadays, I think real hard about bringing any frameworks or libraries into my projects.

3 ms·

Flask & Sinatra were great at stripping down the "uber" web frameworks like Django/Rails. 10/10, would recommend. Bring your own templating engine, ORM.

by mslate 5y ago

Flask & Sinatra were great at stripping down the "uber" web frameworks like Django/Rails. 10/10, would recommend. Bring your own templating engine, ORM.

readonthegoapp 5y ago
i been messing with Laravel lately, and it's ass. and/or the entire modern stack is ass. i actually had this app built for me, and i asked the dev to try to strip out as much shit as possible, including, obviously, tailwind. dev did a good job, but it's still a disaster. flask looks like a dream comparatively. but. is there a middle ground? i was a product manager-type on a (python) pylons pyramid project -- https://trypyramid.com/ https://trypyramid.com/ -- "the start small, finish big, stay finished framework" -- the message sounds good. seemed fine, but i wasn't a dev on it, and we still had plenty of moving parts for what was a relatively simple e-commerce cms (that, admittedly, had a lot of functionality). what i really want is a straightjacket -- some framework that says, 'oh, you want to plug in a different templating engine? how about fuck you? will fuck you work for you?' but i guess that doesn't earn many github stars. if i had to pick one or recommend one with no other qualifiers, i'd pick sinatra. that way i could do it my way.
- skydhash 5y ago
  The fact is, a framework can be good in a team where you have junior developers. When I started with PHP, Laravel seems a god send. You don't even have to learn PHP that deeply, as they provide a quite consistent playground to add your business logic. It's when you got experienced, you begin to notice the bloat. I don't know how it impacts performance, but I've seen many juniors shoot themselves in the foot where there's too little constraint. Nowadays, I think real hard about bringing any frameworks or libraries into my projects.