Responder: A familiar HTTP Service Framework
python-responder.org
Responder: A familiar HTTP Service Framework
1–10 of 116 posts
Re: Responder: A familiar HTTP Service Framework
#2Pretty cool, but I can't shake the feeling that the first example looks an awful lot like javascript...
Perhaps... Maybe ... its because I have been "cheating" on Python with JS. I mean, it is a pain in the booty to code up a web app in python without JS. Try to code a mobile app with Python and Kivy... not all that fun (not practical). In less than a week with React, I have done both. So... why not just skip Python all together? I have been asking myself that question.
Bottom line: The authors of this "service framework" states the Python world doesn't need another web framework, I agree.
It needs some serious love in GUI land.
Re: Responder: A familiar HTTP Service Framework
#3Great, another issue tracker for Kenneth and his followers^H^H^H^H^H^H^H^H^H maintainers to belittle contributors, delete unfavorable comments and generally create a hostile environment for users.
No thanks!
Re: Responder: A familiar HTTP Service Framework
#4Pretty cool, but I can't shake the feeling that the first example looks an awful lot like javascript... Perhaps... Maybe ... its because I have been "cheating" on Python with JS. I mean, it is a pain in the booty to code up a web app in python without JS. Try to code a mobile app with Python and Kivy... not all that fun (not practical). In less than a week with React, I have done both. So... why not just skip Python…
I'd argue that python needs an async django, which will hopefully be django in a few releases.
Re: Responder: A familiar HTTP Service Framework
#5Great, another issue tracker for Kenneth and his followers^H^H^H^H^H^H^H^H^H maintainers to belittle contributors, delete unfavorable comments and generally create a hostile environment for users. No thanks!
I’ve got plenty of criticism for pipenv, but comments like these don’t endear me towards Kenneth’s critics.
Re: Responder: A familiar HTTP Service Framework
#6Great, another issue tracker for Kenneth and his followers^H^H^H^H^H^H^H^H^H maintainers to belittle contributors, delete unfavorable comments and generally create a hostile environment for users. No thanks!
I still remember when kenneth closed every single open ticket on his envoy project without any fixes. Problems? What problems? Serves me right for taking the time to write a detailed bug report. I won't make that mistake again.
Re: Responder: A familiar HTTP Service Framework
#7Maybe I’ll accept non-monospace fonts for code. You get the right ligatures, decent kerning, the softer touch of sans-serif... it has some possibility
But psuedo-cursive strings? This font that looks like a retro emulator using a vectorizing filter?
This is too much. I’m not happy about this development at all.
Re: Responder: A familiar HTTP Service Framework
#8Call me old fashioned, but I like functions that return something. Hard pass.
Re: Responder: A familiar HTTP Service Framework
#9The amount of negative feedback this post is getting is excessive.
Re: Responder: A familiar HTTP Service Framework
#10Maybe I’ll accept non-monospace fonts for code. You get the right ligatures, decent kerning, the softer touch of sans-serif... it has some possibility But psuedo-cursive strings? This font that looks like a retro emulator using a vectorizing filter? This is too much. I’m not happy about this development at all.
Yeah, using it even on the API documentation page [1] is a bit much. This does look like a cool framework, though.