Live data from Hacker News

Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

github.com

51–60 of 192 posts

Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

#51
post #40

Earlier quoted context omitted.

You are missing the forrest for the trees. When people refer to a language, most often they are using it as a synecdoche to refer to the whole language ecosystem and not just the the formal language definition. If you look at the Python ecosystem, it is most definitely interpreted.

Off topic, but thank you for introducing the word "synecdoche" to me.

Movie recommendation: Synecdoche New York

Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

#52
post #40

Earlier quoted context omitted.

You are missing the forrest for the trees. When people refer to a language, most often they are using it as a synecdoche to refer to the whole language ecosystem and not just the the formal language definition. If you look at the Python ecosystem, it is most definitely interpreted.

Off topic, but thank you for introducing the word "synecdoche" to me.

Now the question for non-native speakers is: How to pronounce that word? ;D

Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

#53

Good point! However, you bring in a common misconception I'm fighting with within my company for a long time. Python is not an interpreted language. There is no such thing as an "interpreted language", a language is just a set or rules and keywords. Everything you can fit into Backus–Naur form is already a language even if it doesn't have any implementation nor compiler neither interpreter. Just as a piece of evidenc…

You are missing the forrest for the trees. When people refer to a language, most often they are using it as a synecdoche to refer to the whole language ecosystem and not just the the formal language definition. If you look at the Python ecosystem, it is most definitely interpreted.

Personally, I often find myself saying things like "the ecosystem" to avoid this.

I think it is fair to have a discussion about terminology and arguing with the actual meaning of terms. When there is a technical difference, it would be good to acknowledge that difference between terms. It does not hurt anyone to do that. One can still say something like: "When we communicate I will use the word x for meaning y, because it is shorter and more convenient."

Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

#54
post #40

Earlier quoted context omitted.

Off topic, but thank you for introducing the word "synecdoche" to me.

Now the question for non-native speakers is: How to pronounce that word? ;D

Sin-eck-da-key

Or at least, that's how I'm hearing it from Google.

Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

#55
post #40

Earlier quoted context omitted.

You are missing the forrest for the trees. When people refer to a language, most often they are using it as a synecdoche to refer to the whole language ecosystem and not just the the formal language definition. If you look at the Python ecosystem, it is most definitely interpreted.

Off topic, but thank you for introducing the word "synecdoche" to me.

Did you look up how to pronounce it? I was mispronouncing it for like a year after seeing “Synecdoche New York” (it’s kinda pretentious, not for everyone). My coworker laughed at me when I said the name to him. I’d only ever seen it written, and did not look at a pronunciation chart. Wah wah.

Just in case anyone else is getting it wrong like I was …

https://youtube.com/watch?v=v-n1vGeVIXo

(But really, https://youtu.be/u8_LDxZReTc)

Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

#56
post #42

Earlier quoted context omitted.

Actually uWebSockets and uSockets will perform better than this (2x at least in my local tests), I need to do a lot of copying, instancing and crossing Python GIL. Yeah this test basically shows that Python backed by uWS is crazy fast, but is not an direct comparison to uWS to Go. This test is just an troughput test, with is very useful to measure raw performance. More tools like caching tools, a better database clie…

>"Python backed by uWS is crazy fast, but is not an direct comparison to uWS to Go." Correction. It shows that uWS is crazy fast. Sure if python us used as a thin glue between something like "select username from user" and uWS or send file over uWS then the result is fast. Do something meaningful in Python itself an it will be slow. This is not to diminish your work. Python is mostly glue anyways so in average the en…

I see your comment as positive <3 the whole purpose of this framework is to offer better glue, to Python for Web

Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

#57
sure it's faster.. but go gin and fiber are really slow. they are literally 90% slower than the fast go frameworks. Not that im a go fanboy, but to put things into context here, the actual context here is: python framework 5% faster than fiber and 85% slower than gnet/silverlining/gearbox.

Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

#59
post #57

sure it's faster.. but go gin and fiber are really slow. they are literally 90% slower than the fast go frameworks. Not that im a go fanboy, but to put things into context here, the actual context here is: python framework 5% faster than fiber and 85% slower than gnet/silverlining/gearbox.

For sure have room to improve but is very competitive, i will try to archive the 7 mi inthe future, this is a very young framework, i will work harder!

https://www.techempower.com/benchmarks/#section=test&runid=1...

Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3

#60
post #57

sure it's faster.. but go gin and fiber are really slow. they are literally 90% slower than the fast go frameworks. Not that im a go fanboy, but to put things into context here, the actual context here is: python framework 5% faster than fiber and 85% slower than gnet/silverlining/gearbox.

For sure have room to improve but is very competitive, i will try to archive the 7 mi inthe future, this is a very young framework, i will work harder! https://www.techempower.com/benchmarks/#section=test&runid=1...

huh? waw. strange. there are 2 fibers on the benchmarks. 1 slow and 1 really fast. Same for socketify. 1 fast, 1 slow. Why is this?
Post reply on HN