Hi everyone! The last week, I've been talking with Matti about ways in which PyPy could be friendlier to new users, and what to do about that. One of the examples I raised in which PyPy is, in my opinion, giving newbies a hard time, is the download page. In my opinion it's way too complicated and not geared for people who want to use PyPy but are less knowledgeable, or less interested in putting in time to understand the subtleties of JIT vs no-JIT vs STM, etc. We discussed that maybe I should make that change and open a PR for it. I said I'm willing to do that, (and learn some Mercurial and Nikita on the way) if I know there's general support in this list to that direction of change; I expect a code review, but I want to know before I start that this change is wanted. Here are a few of the changes I'd like to make: 1. Push the list of binaries to the top. 2. Put Python 3 above Python 2. 3. Move the instructions for building to a separate page. The intersection of the set "people who are interested in build instructions" with the set "people who have a hard time pressing an additional link to get to the build instruction" is very small indeed. 4. I might also put icons of Windows, Mac and Linux near their respective binaries. 5. Ideally I would have auto-detection that gives you the binary to your OS, but I'm not sure I want to work that hard. You get the general idea: Treating PyPy more like a finished product and less like a C library. What do you think? Thanks, Ram.
On Sun, Jun 28, 2020 at 3:36 PM Ram Rachum <ram@rachum.com> wrote:
Hi everyone!
The last week, I've been talking with Matti about ways in which PyPy could be friendlier to new users, and what to do about that. One of the examples I raised in which PyPy is, in my opinion, giving newbies a hard time, is the download page.
In my opinion it's way too complicated and not geared for people who want to use PyPy but are less knowledgeable, or less interested in putting in time to understand the subtleties of JIT vs no-JIT vs STM, etc.
We discussed that maybe I should make that change and open a PR for it. I said I'm willing to do that, (and learn some Mercurial and Nikita on the way) if I know there's general support in this list to that direction of change; I expect a code review, but I want to know before I start that this change is wanted.
Here are a few of the changes I'd like to make:
Push the list of binaries to the top. Put Python 3 above Python 2. Move the instructions for building to a separate page. The intersection of the set "people who are interested in build instructions" with the set "people who have a hard time pressing an additional link to get to the build instruction" is very small indeed. I might also put icons of Windows, Mac and Linux near their respective binaries. Ideally I would have auto-detection that gives you the binary to your OS, but I'm not sure I want to work that hard.
You get the general idea: Treating PyPy more like a finished product and less like a C library.
What do you think?
+1 - David
Awesome. Thanks for the support guys. I've put this on my todo list. On Mon, Jun 29, 2020 at 4:00 PM David Edelsohn <dje.gcc@gmail.com> wrote:
On Sun, Jun 28, 2020 at 3:36 PM Ram Rachum <ram@rachum.com> wrote:
Hi everyone!
The last week, I've been talking with Matti about ways in which PyPy
could be friendlier to new users, and what to do about that. One of the examples I raised in which PyPy is, in my opinion, giving newbies a hard time, is the download page.
In my opinion it's way too complicated and not geared for people who
want to use PyPy but are less knowledgeable, or less interested in putting in time to understand the subtleties of JIT vs no-JIT vs STM, etc.
We discussed that maybe I should make that change and open a PR for it.
I said I'm willing to do that, (and learn some Mercurial and Nikita on the way) if I know there's general support in this list to that direction of change; I expect a code review, but I want to know before I start that this change is wanted.
Here are a few of the changes I'd like to make:
Push the list of binaries to the top. Put Python 3 above Python 2. Move the instructions for building to a separate page. The intersection
of the set "people who are interested in build instructions" with the set "people who have a hard time pressing an additional link to get to the build instruction" is very small indeed.
I might also put icons of Windows, Mac and Linux near their respective binaries. Ideally I would have auto-detection that gives you the binary to your OS, but I'm not sure I want to work that hard.
You get the general idea: Treating PyPy more like a finished product and less like a C library.
What do you think?
+1
- David
Hi everyone, Just a follow-up on this thread: Matti and I overhauled the PyPy download experience. This includes the download button on the main page: https://www.pypy.org/ and the new short-and-to-the-point download page. Thanks, Ram. On Mon, Jun 29, 2020, 16:01 Ram Rachum <ram@rachum.com> wrote:
Awesome. Thanks for the support guys. I've put this on my todo list.
On Mon, Jun 29, 2020 at 4:00 PM David Edelsohn <dje.gcc@gmail.com> wrote:
On Sun, Jun 28, 2020 at 3:36 PM Ram Rachum <ram@rachum.com> wrote:
Hi everyone!
The last week, I've been talking with Matti about ways in which PyPy
could be friendlier to new users, and what to do about that. One of the examples I raised in which PyPy is, in my opinion, giving newbies a hard time, is the download page.
In my opinion it's way too complicated and not geared for people who
want to use PyPy but are less knowledgeable, or less interested in putting in time to understand the subtleties of JIT vs no-JIT vs STM, etc.
We discussed that maybe I should make that change and open a PR for it.
I said I'm willing to do that, (and learn some Mercurial and Nikita on the way) if I know there's general support in this list to that direction of change; I expect a code review, but I want to know before I start that this change is wanted.
Here are a few of the changes I'd like to make:
Push the list of binaries to the top. Put Python 3 above Python 2. Move the instructions for building to a separate page. The intersection
of the set "people who are interested in build instructions" with the set "people who have a hard time pressing an additional link to get to the build instruction" is very small indeed.
I might also put icons of Windows, Mac and Linux near their respective binaries. Ideally I would have auto-detection that gives you the binary to your OS, but I'm not sure I want to work that hard.
You get the general idea: Treating PyPy more like a finished product and less like a C library.
What do you think?
+1
- David
the image is out of place , on 4k laptop. [image: image.png] On Sun, Aug 30, 2020 at 7:31 PM Ram Rachum <ram@rachum.com> wrote:
Hi everyone,
Just a follow-up on this thread: Matti and I overhauled the PyPy download experience.
This includes the download button on the main page: https://www.pypy.org/ and the new short-and-to-the-point download page.
Thanks, Ram.
On Mon, Jun 29, 2020, 16:01 Ram Rachum <ram@rachum.com> wrote:
Awesome. Thanks for the support guys. I've put this on my todo list.
On Mon, Jun 29, 2020 at 4:00 PM David Edelsohn <dje.gcc@gmail.com> wrote:
On Sun, Jun 28, 2020 at 3:36 PM Ram Rachum <ram@rachum.com> wrote:
Hi everyone!
The last week, I've been talking with Matti about ways in which PyPy
could be friendlier to new users, and what to do about that. One of the examples I raised in which PyPy is, in my opinion, giving newbies a hard time, is the download page.
In my opinion it's way too complicated and not geared for people who
want to use PyPy but are less knowledgeable, or less interested in putting in time to understand the subtleties of JIT vs no-JIT vs STM, etc.
We discussed that maybe I should make that change and open a PR for
it. I said I'm willing to do that, (and learn some Mercurial and Nikita on the way) if I know there's general support in this list to that direction of change; I expect a code review, but I want to know before I start that this change is wanted.
Here are a few of the changes I'd like to make:
Push the list of binaries to the top. Put Python 3 above Python 2. Move the instructions for building to a separate page. The
intersection of the set "people who are interested in build instructions" with the set "people who have a hard time pressing an additional link to get to the build instruction" is very small indeed.
I might also put icons of Windows, Mac and Linux near their respective binaries. Ideally I would have auto-detection that gives you the binary to your OS, but I'm not sure I want to work that hard.
You get the general idea: Treating PyPy more like a finished product and less like a C library.
What do you think?
+1
- David
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
That is true and I've seen it on my computer too. However, it's not related to our change. Open a ticket. On Wed, Sep 23, 2020 at 6:22 PM Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:
the image is out of place , on 4k laptop.
[image: image.png]
On Sun, Aug 30, 2020 at 7:31 PM Ram Rachum <ram@rachum.com> wrote:
Hi everyone,
Just a follow-up on this thread: Matti and I overhauled the PyPy download experience.
This includes the download button on the main page: https://www.pypy.org/ and the new short-and-to-the-point download page.
Thanks, Ram.
On Mon, Jun 29, 2020, 16:01 Ram Rachum <ram@rachum.com> wrote:
Awesome. Thanks for the support guys. I've put this on my todo list.
On Mon, Jun 29, 2020 at 4:00 PM David Edelsohn <dje.gcc@gmail.com> wrote:
On Sun, Jun 28, 2020 at 3:36 PM Ram Rachum <ram@rachum.com> wrote:
Hi everyone!
The last week, I've been talking with Matti about ways in which PyPy
could be friendlier to new users, and what to do about that. One of the examples I raised in which PyPy is, in my opinion, giving newbies a hard time, is the download page.
In my opinion it's way too complicated and not geared for people who
want to use PyPy but are less knowledgeable, or less interested in putting in time to understand the subtleties of JIT vs no-JIT vs STM, etc.
We discussed that maybe I should make that change and open a PR for
it. I said I'm willing to do that, (and learn some Mercurial and Nikita on the way) if I know there's general support in this list to that direction of change; I expect a code review, but I want to know before I start that this change is wanted.
Here are a few of the changes I'd like to make:
Push the list of binaries to the top. Put Python 3 above Python 2. Move the instructions for building to a separate page. The
intersection of the set "people who are interested in build instructions" with the set "people who have a hard time pressing an additional link to get to the build instruction" is very small indeed.
I might also put icons of Windows, Mac and Linux near their respective binaries. Ideally I would have auto-detection that gives you the binary to your OS, but I'm not sure I want to work that hard.
You get the general idea: Treating PyPy more like a finished product and less like a C library.
What do you think?
+1
- David
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
On Wed, Sep 23, 2020 at 6:22 PM Phyo Arkar <phyo.arkarlwin@gmail.com <mailto:phyo.arkarlwin@gmail.com>> wrote: the image is out of place , on 4k laptop. ... Thanks for the heads up. How about if we rearrange the pieces on the page so that the image is %100 wide and not in a column since it is too big? I will try it the next time I rebuild the site, which will be for the upcoming release. I am not really a UX designer, so please keep the comments and suggestions coming. Matti
participants (6)
-
Armin Rigo -
Carl Friedrich Bolz-Tereick -
David Edelsohn -
Matti Picus -
Phyo Arkar -
Ram Rachum