51–59 of 59 posts
I thought this was a great post, some amazing code, and humbling since this is WAY beyond my current - and future - ability. Even more impressive - it looks like the author is a freshman in college! https://www.linkedin.com/in/benkurtovic Nice work, Ben!
Earlier quoted context omitted.
- Fast CPU performance. The PyPy implementation in my tests (JSON processing) was faster than Go and CPython (module used was a C library) - Compiles to standalone binaries, C++ using Nuitka and other methods such as PyInstaller - Fast speed of development - Syntax: matter of personal taste. But overall Python is very terse - Large community, ~20 year vast resources for use and learning - IronPython for .Net librarie…
Citing "fast CPU performance" alongside "large community" and "already installed" sounds a bit disingenuous. The version that is fast has a smaller community and is unlikely to be already installed while the one that is already installed and has a large community is not fast. Like it or not, "Python" means CPython to most people, inducing most library authors, and you run into problems using PyPy if you assume it's "…
Python is a language. Languages don't have speed. Implementations do.
Earlier quoted context omitted.
Citing "fast CPU performance" alongside "large community" and "already installed" sounds a bit disingenuous. The version that is fast has a smaller community and is unlikely to be already installed while the one that is already installed and has a large community is not fast. Like it or not, "Python" means CPython to most people, inducing most library authors, and you run into problems using PyPy if you assume it's "…
It wasn't stated alongside. "Most people" aren't ones I want to be around or work with. I come here to associate with those who do their homework. CPython and PyPy are the same Python community as PyPy runs Python code unmodified. PyPy also interfaces just as well with C, inform yourself. Python is a language. Languages don't have speed. Implementations do.
I am not sure what you mean here in the context of what I said. My was simply that most users of Python don't use PyPy, so most library authors don't test against it.
>CPython and PyPy are the same Python community as PyPy runs Python code unmodified.
Not all of it, as https://bitbucket.org/pypy/compatibility/wiki/Home will confirm.
>PyPy also interfaces just as well with C, inform yourself.
Sorry, this is where I did not make my point very clear. I meant to point out that the way in which PyPy interfaces with C is different from the one used by CPython, so libraries that rely on it don't work in PyPy without an extra porting effort.
Earlier quoted context omitted.
It wasn't stated alongside. "Most people" aren't ones I want to be around or work with. I come here to associate with those who do their homework. CPython and PyPy are the same Python community as PyPy runs Python code unmodified. PyPy also interfaces just as well with C, inform yourself. Python is a language. Languages don't have speed. Implementations do.
>"Most people" aren't ones I want to be around or work with. I come here to associate with those who do their homework. I am not sure what you mean here in the context of what I said. My was simply that most users of Python don't use PyPy, so most library authors don't test against it. >CPython and PyPy are the same Python community as PyPy runs Python code unmodified. Not all of it, as https://bitbucket.org/pypy/com…
Either way, while you attempt to discredit PyPy the fact remains that Python code is and can be very fast for CPU heavy work. There's no way around that other than trying to poke holes.
Earlier quoted context omitted.
- Cutting and pasting code may change its functionality. Especially from a non-source medium like web pages. - I find myself fighting my editor's indentation a lot more as a result. Hitting return at the start of a line in the middle of an existing chunk of code indents to the previous line's indentation not the current line's indentation. - It's asymmetrical: code drifts off to the right as you go down. Together wit…
Those are valid complaints, but they are kind of on the same level as saying "I have to type 'int' to declare an int, what a drag!"
I thought this was a great post, some amazing code, and humbling since this is WAY beyond my current - and future - ability. Even more impressive - it looks like the author is a freshman in college! https://www.linkedin.com/in/benkurtovic Nice work, Ben!
Damn. If I was a freshman in his CS class I would hate his guts.
Earlier quoted context omitted.
Yeah, I also don't get that. My Python code even has the same indentation as my Java code in university had. I just don't have to spell out the ; and the {}. But in the beginning it was really tough, especially because my eyes were trained to structuring code by {}. I think it's mostly a question about if you want to put in the effort to retrain your instincts or not.
I prefer having to add the {}'s and ;'s, even if the spacing is the same, because they provide a clear and definite bound on scoping, which (unfortunately) often gets messed up in Python.