kmod

16 ms·

1. 151.▲
   You Quit. I Quit. We All Quit. and It’s Not a Coincidence(nytimes.com)

   2 points by kmod 5y ago|1 comments
2. 152.▲
   Pre-compiled packages now available for Pyston(blog.pyston.org)

   3 points by kmod 5y ago|0 comments
3. 153.▲
   Roadmap for the Pyston Python Implementation(blog.pyston.org)

   4 points by kmod 5y ago|0 comments
4. 154.▲
   by kmod 5y ago

   First, I strongly recommend using a tiling window manager. There aren't many logistical things you can do to improve your programming output but this is one. I used XMonad for many years and finally had to give up and switch to i3, so
5. 155.▲
   Pyston Team Joins Anaconda(blog.pyston.org)

   6 points by kmod 5y ago|0 comments
6. 156.▲
   by kmod 5y ago

   I've been a user of Flow Club for a while now and I highly recommend it even though that's probably not in my personal interest. I often find that I am >2x as productive during these hours, which I find remarkable, and sometime
7. 157.▲
   Pentagon Cancels $10B Jedi Cloud-Computing Contract(nytimes.com)

   15 points by kmod 5y ago|1 comments
8. 158.▲
   by kmod 5y ago

   We run the numpy testsuite as part of our testsuite so to our knowledge it works well.
9. 159.▲
   by kmod 5y ago

   Imports are faster! Maybe not as much as you're hoping but we did optimize them a bit.
10. 160.▲
    by kmod 5y ago

    https://github.com/pyston/pyston/wiki/Semantic-changes
11. 161.▲
    by kmod 5y ago

    Good question, we talked about it a tiny bit in our previous blog post and are planning on doing more in-depth blog posts in the future. I added a very brief summary to the github readme: - A very-low-overhead JIT using DynASM - Quickening
12. 162.▲
    by kmod 5y ago

    We use completely separate benchmarks, where our Pyston benchmarks are quite a bit "harder" and PyPy is only 12% faster on them while using 4x the memory.
13. 163.▲
    by kmod 5y ago

    I'm still learning about Cinder, but my initial impression is that there are many similar techniques used, and maybe one interesting difference is that with Pyston we've focused more on out-of-the-box performance while Cinder has
14. 164.▲
    Pyston v2.2: faster and open source(blog.pyston.org)

    20 points by kmod 5y ago|2 comments
15. 165.▲
    by kmod 6y ago

    My 2 cents as an implementer of an alternate Python implementation -- I am skeptical about this approach. We tried the "provide a limited API" approach in the past and found the following things: - People actually use the "h
16. 166.▲
    by kmod 6y ago

    Right now there are only two sellers
17. 167.▲
    by kmod 6y ago

    My review included the picture of the card, they just didn't reattach it to my rejection email
18. 168.▲
    Amazon disallows pointing out paid reviews(blog.kevmod.com)

    1086 points by kmod 6y ago|479 comments
19. 169.▲
    by kmod 6y ago

    I updated the repo in the middle of this comment thread; it used to show the v1 code, but since that was confusing people now it's just a stub that redirects you to the blog.
20. 170.▲
    by kmod 6y ago

    This is just a comment on my personal use of Python for competitive programming: I've never used numpy for competitive programming or thought that it would be a good tool for that. PyPy seems like a great solution for the highly-numer
21. 171.▲
    by kmod 6y ago

    We started with an LLVM-based JIT in Pyston v1. Our experience with the two jits is that it's very nice that DynASM is ~2 orders of magnitude faster, and also that we have not been able to extract enough high-level knowledge to make a
22. 172.▲
    by kmod 6y ago

    All my CodeJam solutions are in Python :) While we could certainly go in this direction, we're not planning to, because in our experience optimizations for different workloads are largely distinct, and this use case is already handled
23. 173.▲
    by kmod 6y ago

    I would say there's a small minority of our changes that we can upstream, and eventually we'd like to upstream them. For the rest, I would say the different set of priorities for the two projects means they probably will stay sep
24. 174.▲
    by kmod 6y ago

    Whoops, I forgot we had that up, I took it down until we can post an up-to-date image
25. 175.▲
    Pyston v2: Faster Python(blog.pyston.org)

    262 points by kmod 6y ago|206 comments
26. 176.▲
    by kmod 6y ago

    From my experience in this area: - There are companies which would be willing to pay large amounts of money (more than he's asking for) for the speedups he's promising - There are other similar efforts underway (such as ours) whic
27. 177.▲
    by kmod 6y ago

    I'll add my experience as a counterpoint -- I've been running my own wordpress blog for several years now, and the amount of effort involved has been surprisingly high. I've had to tune apache numerous times (seriously, who
28. 178.▲
    by kmod 6y ago

    This is a common view but I've never heard it from someone who has tried to optimize Python. Personally I think that Python is as much more dynamic than JavaScript as JavaScript is than C. (I can't talk for the other languages.)
29. 179.▲
    by kmod 6y ago

    I don't know how to interpret the results of --trace-opt, but when I increase the iteration bounds 10x the running time increases 10x, so I don't think the code is being eliminated. This is with node v12.13.0
30. 180.▲
    by kmod 6y ago

    It used to be this way, but at some point they added a faster calling convention and moved a number of things to it. Calling type objects still falls back to the old convention though.