Earlier quoted context omitted.
This is false. Making a new implementation is a practical purpose. Any new implementation will have to work with the spec, instead of idiosyncracies of other implementations. Ergo there are practical purposes which go by how the language is defined in its specification. Some languages have more of a proper spec than others, of course. If we look at for example Scheme dialects, then they often change their implementat…
> Making a new implementation is a practical purpose. Not yet it isn't. At least not for Python. I mean there are plenty of alternative implementations of Python but they aren't practical because they don't work with CPython modules (as far as I know anyway) so approximately nobody uses them. The de facto spec is "what CPython does".
Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
71–80 of 192 posts
Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
#72Earlier quoted context omitted.
It does not say that Python is faster than Go it clearly says "Python framework". > It only proves that wrapping C code in Python is fast. Yes, it proves that for this specific use case Python is faster.
Technically, it is C that’s faster.
Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
#73I'm feeling old. I went back to Flask recently and keep finding everything I know is deprecated, or not best practice any more. Then I read every week that some new framework is out that is better. I'm tired of it. I end up spending more time learning new things than I do building new things! Maybe I should get off hn for a while
Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
#74The “src/“ directory[0] contains compiled .so files. Is this even open source? [0] https://github.com/cirospaciari/socketify.py/tree/main/src/s...
Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
#75I'm feeling old. I went back to Flask recently and keep finding everything I know is deprecated, or not best practice any more. Then I read every week that some new framework is out that is better. I'm tired of it. I end up spending more time learning new things than I do building new things! Maybe I should get off hn for a while
Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
#76Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
#77Earlier quoted context omitted.
It does not say that Python is faster than Go it clearly says "Python framework". > It only proves that wrapping C code in Python is fast. Yes, it proves that for this specific use case Python is faster.
Technically, it is C that’s faster.
And if you are not making reference to a specific implementation then the comparison does not make any sense.
Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
#78I'm feeling old. I went back to Flask recently and keep finding everything I know is deprecated, or not best practice any more. Then I read every week that some new framework is out that is better. I'm tired of it. I end up spending more time learning new things than I do building new things! Maybe I should get off hn for a while
Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
#79The “src/“ directory[0] contains compiled .so files. Is this even open source? [0] https://github.com/cirospaciari/socketify.py/tree/main/src/s...
Re: Show HN: Socketify.py: Http/Https and WebSockets servers for PyPy3 and Python3
#80I'm feeling old. I went back to Flask recently and keep finding everything I know is deprecated, or not best practice any more. Then I read every week that some new framework is out that is better. I'm tired of it. I end up spending more time learning new things than I do building new things! Maybe I should get off hn for a while
The secret is stop using frameworks and use just libraries (even the latter with parsimony)