News for hackers. Stuff that matters.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by BuckRogers on Thursday October 29, 2015 @02:34PM (#10473237)
The good news never stops with these guys. PyPy is so good that I've stopped considering myself a "Python programmer" to a "PyPy programmer" over the last few years. Best of every world. I get my preferred language and eliminate CPU performance worries.

For me, targeting development on PyPy has taken the place of migrating to Python3. Which just moves too fast in effort to pull people over, Python is too big for that strategy. At this point, people want speed with a great language, they want PyPy! The PyPy team has pretty much enabled the perfect development stack. I use PyPy+Django+gunicorn+Nginx and no problems.

Keep up the great work.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Thursday October 29, 2015 @04:24PM (#10474010)
I'll go one step further and advocate for the PyPy developers please not to port to Python 3. Here we have a project which has clearly become the go to for 2.x people who would like Python to move forward in a way which makes a real difference to them, and there is an ideal opportunity here for this to become the de-facto continuation of the 2.x line, with a real future, as an alternative to the 3.x forcefeed.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by rudolf0 on Thursday October 29, 2015 @05:18PM (#10474378)
What would be the point of this? Are you suggesting PyPy forks the Python language itself? PyPy hasn't implemented new core language features, and I don't see them doing so in the future. Python 3 is actively developed, fixing many warts in the language and adding great new features.

As annoying as the transition to Python 3 is, it's the future of the language. I was actually one of the curmudgeons who stuck with 2.7 and grumbled about not wanting to switch until a few months ago. I've accepted that I need to, at the very least, start new projects in Python 3 wherever possible. The vast majority of popular third party libraries have been ported over at this point. Python 2's death is inevitable, even if it will take many more years.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Thursday October 29, 2015 @05:23PM (#10474414)
That is exactly what I am suggesting. There is no urgent necessity to add any new core language features to 2.7. That's what you 3 guys just don't get. I certainly don't need asyncio as much as I need vectorised numerics, and if I needed asyncio, I had at least 5 libraries already. I most definitely will never be type annotating Python. Cloud cuckoo land.

Let me warn you. If you persist with your propaganda on Python3, then GOLANG will be the future of Python. Does that register with you guys?

Nobody who uses Python 2.7 all day every day thinks it has any of these imaginary "worts" you 3.x guys like to pitch incessantly.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by dang on Thursday October 29, 2015 @09:54PM (#10475712)
> you 3 guys ... Cloud cuckoo land ... your propaganda ... Does that register with you guys?

Your comments have been crossing into incivility. Please don't do that; it breaks the site rules and leads to tedious flamewars. I'm sure you can make your argument civilly and substantively if you try.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Friday October 30, 2015 @03:16PM (#10479901)
I was overly aggressive. It's regrettable. But every point I made has been seriously contemplated, and is in my opinion worthy of consideration. The extent to which the 2.7 community and its arguments, are treated with derision by the 3.x people, makes some form of vigorous defence sometimes necessary. I'll add that unlike a large silent group of Python people who basically agree with me, I am not afraid to spend karma points speaking up against the received wisdom unambiguously and forcefully.

Now that I have made all my points, it's bye-bye.py. I won't comment on Python again.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by dang on Friday October 30, 2015 @06:55PM (#10481044)
> It's regrettable.

That makes it sound like you had no control.

Being rude is not "speaking up against the received wisdom", it's just being rude, and it's against the rules here. In the future, please post civilly and substantively or not at all.

https://news.ycombinator.com/newsguidelines.html

https://news.ycombinator.com/newswelcome.html

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by oberstein on Thursday October 29, 2015 @06:18PM (#10474776)
> Let me warn you. If you persist with your propaganda on Python3, then GOLANG will be the future of Python. Does that register with you guys?

This abstract future of Python has already been ceded to something that is not Python, just as once the abstract future of Perl was Python. Ruby once tried to take the mantle but failed. Go is now taking a lot of mindshare (from 2 or 3 more I wonder?) and I agree the Python 3 crowd just makes Go more likely to succeed, which is terrifying since it's probably the worst possible choice. My message is simply despair and accept the inevitable: Python will fade -- by all means keep using it, people still use Perl, scientist will be using it for a long time -- but the rest of the software world will pass you by. If you care about what the rest of the world is doing at all, you can help make sure the future passes to better general purpose high level languages like Nim or Clojure or OCaml, and for specific niches like scientific computing goes to the likes of Julia eventually. Anything but Go.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Thursday October 29, 2015 @06:40PM (#10474909)
I'm currently registered on the Ocaml mooc ;-) Very intrigued by Nim too.

Yes I find Golang to be dry and uninspiring, but as per one of my other comments, I get 20x the performance, and the concurrency model beats Asyncio hands down. Honestly I needed to get 360 gigabytes of JSON into Cassandra and Python was going to take 6 days (there is some light conditionality on each datapoint preventing a raw dump). I took 1.5 of those days to learn how to do it in Golang, started it at midday today, and estimate it'll be done when I get into work tomorrow morning. Sometimes I just need to get stuff done.

EDIT: Just re-read your post and cannot help but agree that Python's demise is already telegraphed. History. Perl->Python->(?) is a nice analogy. Python won't die for sure, but it will not flourish like it did in the past decade. And yes I think it's good advice to look to more ambitious languages than Go, even if Go solves many "today" problems quite well. Personally wish Clojure would come off the JVM but am looking into Ocaml, Elixir, and when I need imperative, good ol' C wrapped up in Nim. All good candidates, though I really wish something would come up and go "fully vectorized" for the brave new world of GPUs. Personally need a REPL which is why Ocaml wins for now though Spark looks to me to be the "new R" for data science so I shouldn't exclude Scala (JVM notwithstanding). Decisions decisions...

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by oberstein on Thursday October 29, 2015 @10:00PM (#10475733)
It will be interesting to see what the final winner of GPU programming looks like. There's also the possibility of FPGAs making their way into consumer hardware, and right now the pure-Python library MyHDL is a great choice for those. There are a few attempts at abstracting over OpenCL like https://github.com/eholk/harlan, and some intriguing domain specific attempts like http://halide-lang.org/ but I think it will be a while yet before something takes over. I also don't think whatever it is can succeed without corporate backing.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by Nrpf on Sunday November 01, 2015 @12:30AM (#10485414)
Python Numba compiler (fast as julia) has a fair amount of Cuda and AMD HSA capability.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by CuriouslyC on Friday October 30, 2015 @11:48AM (#10478523)
You're looking at this from the SV startup echo-chamber perspective.

People use Python because the language gets out of the way fairly quickly to let you get things done fairly quickly. Sure, it isn't a rigorous engineering language, but the ratio of small projects that just need something good enough and easy to work with to large/complex projects requiring careful engineering is staggeringly large. While Python is definitely cooling off; people have been working with it for long enough to want something better - unfortunately there just isn't anything on the radar that is significantly enough better to overcome Python's third party library momentum at the moment.

Believe me, I'd love a language with a really flexible/optional functional type system, better metaprogramming facilities, a better concurrency design, slightly more consistent syntax, etc - just as long as it is still easy to think in and convenient to use like Python.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by dragonwriter on Friday October 30, 2015 @11:59AM (#10478590)
> Believe me, I'd love a language with a really flexible/optional functional type system, better metaprogramming facilities, a better concurrency design, slightly more consistent syntax, etc - just as long as it is still easy to think in and convenient to use like Python.

As someone who, among dynamic languages, dismissed Perl quite a while back as not as useful as Python and Ruby, I'm starting to think Perl 6 may be the language that hits that spot.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by Nrpf on Sunday November 01, 2015 @12:33AM (#10485422)
No please! Julia Julia Julia fills all those, but with beatiful python like syntax, lisp like macros when you wnat them, go like channels, distributed capabilities and leading class numerical stuff. Also webserver with a front end that you can build with polymer in Pure Julia.

http://escher-jl.org/

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by tadlan on Saturday October 31, 2015 @10:31PM (#10485202)
Julia!!!!! The answer to all these problems, both for general and science programming.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by brachi on Thursday October 29, 2015 @07:30PM (#10475214)
I wonder how much faster pypy would be in parsing 360 GB of data.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by meowface on Thursday October 29, 2015 @07:51PM (#10475320)
I use Python 2.7 all day every day and I definitely still notice the warts and find them irritating. They are minor warts, and almost never affect my productivity, but they're definitely things that should have been, and are, fixed. super(what do I pass here again?), old vs. new style classes, integer division, input, print, exception bubbling/chaining, nonsense compares between different types, True/False/None as regular variables, no "nonlocal"... Then there are the features I can't use, like extended unpacking and merging, better yielding, function annotations, and lots of improvements to the standard library in terms of their API and functionality.

I'm not a fan of asyncio, but the other stuff is quite awesome. It's not compelling enough to port some of my older Python 2.7 projects, and isn't a revolution of the language or anything, but they're good improvements. And even if they weren't good improvements, Python 3 is the future, and Python 2.7 simply won't be a viable option for a lot longer.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by andrepd on Thursday October 29, 2015 @06:22PM (#10474804)
I would suggest toning down the arrogance. Just because you don't personally need some features does not mean that people who want the language to progress and not stagnate are idiots.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Friday October 30, 2015 @02:50AM (#10476445)
That's rich when it is the 2.7 users like myself who are constantly bombarded with arrogance and condescension. Nobody wants Python to stagnate. The argument is which direction it should take.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by gvalkov on Thursday October 29, 2015 @08:10PM (#10475404)
You contribute the same borderline FUD in every thread that is related to Python. It's unfortunate that Python is not the language you want it to be, but consider just how dismissive you are of the needs of others - frankly, it comes across as arrogant.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Friday October 30, 2015 @02:27PM (#10479592)
FUD? I have >100k lines of highly sophisticated numerical analysis Numpy/Python code in fixed income which has cost literally millions of dollars. I'm not going to let that investment get toyed with by the webified 3.x crew without vigorously stating my point.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by gvalkov on Friday October 30, 2015 @05:58PM (#10480771)
Could Python 3 host the features you want? If it did, would you consider migrating your code-base to it? I'm positive that if your ideas have merit and you share them on the python-ideas mailing list, you'll get a good discussion out of it at the very least.
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by orf on Thursday October 29, 2015 @05:28PM (#10474446)
> Nobody who uses Python 2.7 all day every day thinks it has any of these imaginary "worts" you 3.x guys like to pitch all day.

Maybe people who use 2.7 all day don't see the warts as much as someone who has been rid of them?

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Thursday October 29, 2015 @05:34PM (#10474503)
It took me a week struggling with Asyncio to wrap my mind around it. It took me 12 hours to do the same with Golang channels.

I got 20 000 inserts per second from a 360 gig JSON file into Cassandra using 30 goroutines. I was maxing out at 900 in Python 3. Golang was parsing the JSON at a frankly RIDICULOUS 2 million lines per second. Python 3 was around 50 thousand.

Python 3 is adding features that other languages do better. Python smashes other languages in numerics, and approachability. Nobody needs 3 for numerics, and 3 goes backwards in approachability. If you're using 3 for its back-end tools, you're using the wrong tool.

I would never move to golang for numerics because pandas/numpy/scipy/theano stomp all over it, but its only for numerics that I'll stay with Python. Everything else I'm moving away (mostly Golang, looking at Elixir) and talking to the numeric stack over zeroMQ/msgpack.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by orf on Thursday October 29, 2015 @06:59PM (#10475024)
> 20 000 inserts per second from a 360 gig JSON file into Cassandra using 30 goroutines. I was maxing out at 900 in Python 3. Golang was parsing the JSON at a frankly RIDICULOUS 2 million lines per second. Python 3 was around 50 thousand.

Newsflash, Go is fast. I'm sure those numbers will be worse in Py2 than Py3 as well, but aside from that what's your point? Python is slow so... don't switch to Python 3?

> Python 3 is adding features that other languages do better. Python smashes other languages in numerics, and approachability. Nobody needs 3 for numerics, and 3 goes backwards in approachability. If you're using 3 for its back-end tools, you're using the wrong tool.

Sure, people using it for numerical stuff might like Py2, but is that the only use case of Python? Should I not switch because you do numerical stuff? Django is great for backend stuff, as is the whole ecosystem (twisted, flask, DRF, asyncio).

Python 3 is also far more approachable than Python 2. Try explaining to someone why their program exploded after typing an umlaut into it, the magical "from __future__ import division" incantation or even the silly super() syntax.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Thursday October 29, 2015 @07:53PM (#10475335)
Newsflash. Python 3's main pragmatic selling points are Unicode and Async. Golang is Unicode by default, its concurrency model is much easier to reason about, and it's 20x faster. Why on earth would you use Python 3 (or 2) for your backend? You like buying 20 server boxes when 1 golang box will do? If you think Python will survive as a production language on servers, you're dreaming. It's done, defeated, history on the server outside of legacy code. Django? gimmeabreak.

So what's left that Python does better than any other language? Numerics. That's the only place where you still have a sticky user base that is not likely to dump Python. So don't be so quick do dismiss it. It's the only leg Python is left standing on that other languages cannot easily devour.

Approachability. Not much in it. For every 3/2 = 1 you cite I give you unintuitive lazy ranges, the complete idiocy that 01 != 1, and the unnecessary print functionization which removes one of Python's greatest first-line simplicity selling points. But I will give you that Python 3 remains approachable as a first language. However on that front, inroads every day from JS, where a new coder can get "wow" results in the browser much more quickly than the boring ol' VT100 terminal.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by Nrpf on Sunday November 01, 2015 @11:56AM (#10487032)
Julia has multithreading and channels. Better syntax than go, more like python. Better for numerics...why use anything else?
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by BuckRogers on Thursday October 29, 2015 @05:09PM (#10474310)
Not a bad idea. It would certainly elevate the project to unforeseen heights and probably turn them (http://www.baroquesoftware.com/) into very wealthy men while offering a very desired and needed service for many businesses. While harming no one who didn't already harm themselves. More relevant than CPython3 overnight, which is of significant stature.

If prestige and money are desirable things, absolute no brainer if they have a business bone in their bodies. It would also secure the future of the stack for everyone concerned with Python3 threatening to cut off Python2. It could also enable a bigger return on those of us who have invested financially into PyPy development. It would certainly snowball even more financial investment.

It would then be the CPython3 project's move. Abandon and integrate all the non-breaking Python3 features into 2.7? Or just move forward with a significantly weaker and less relevant project, working against their past selves? I don't think most would really care and it's best they just move away with their own project.

Could be on the way judging from the favorable naming convention, PyPy4? Has a nice ring to it.

"the Python2.7 compatible release — PyPy 4.0.0 — (`what's new in PyPy4.0.0?`_)"

"the Python3.2.5 compatible release — PyPy3 2.4.0 — (what's new in PyPy3 2.4.0?)."

The PyPy gods are in an enviable position for sure. If they seize the opportunity it's the chance of a lifetime.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by orf on Thursday October 29, 2015 @05:25PM (#10474428)
Yeah, the best thing they could possibly do right now is to fork Python and make yet another flavour. We already have this 2/3 mess so let's throw another version into the mix just as Py2 seems to be dying.

I don't get this hate for Python 3. Yeah some things changed, yeah having a big codebase in Py2 sucks if you don't have the time/resources to switch, but starting new projects in Py3 by default is awesome. Asyncio and async/await are fantastic and worth the switch alone.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Thursday October 29, 2015 @06:14PM (#10474753)
Yes, I agree that Python 3 is not that bad to start a new project in. But that's not the problem. The problem is that many of us have a huge investment in Python, and the project is meandering around, borderline-insulting its historic users who still like 2.7, while simultaneously failing to deliver on REAL needs such as performance and GPU support. Instead we get these little tweaks here and there, downright embarrassing PEPs like type annotations, and all this frankly distasteful pressure to move to 3.x using threats of the end-of-the-line for 2....

Basically 3 gives us lots of headaches, very marginal improvements, an ivory-tower sense of "we know best" (message to Guido - no you don't), and a real concern that the powers that be have no clue what's going on at Golang Towers, Fort Javascript, not to mention Clojure, Julia, or even Elixir.

Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by maxerickson on Thursday October 29, 2015 @05:32PM (#10474485)
They are already willing to take money to work on Python 2.7 stuff, how does refusing to take money for Python 3 stuff lead to them making more money?
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by vegabook on Thursday October 29, 2015 @05:45PM (#10474583)
It would show leadership. Leadership which is demonstrably lacking in the 3.x line. Thus they could take a (risky but calculated) bet to take over Python completely.
[dead]
Re:PyPy 4.0.0 Released – A Jit with SIMD Vectorization and More by BuckRogers on Thursday October 29, 2015 @05:48PM (#10474595)
I think your ideas are relatively safe here, just don't go to reddit expecting your freethinking Python2 heathenism to be accepted. ;) I'm afraid some of those folks are making there way over here though.

I know you're not suggesting use the name Python4 but it would be interesting to know the possible trademark issues. I'd expect Guido and the core devs to get nasty if they called it Python4. It would probably be too close to war. Announcing PyPy an official fork of Python probably already has them hesitating from backlash. In the end, the gain is bigger than any vocal Python3 folks could muster. I think both sides want PyPy pretty bad but currently in reality it's a 2.x advantage.

They already have a great name, the implementation and language could be PyPy(4+).