3 ms·

I think the key reason why this link has been posted to HN now is because p5js has a new website? Back in 2023 the Sovereign Tech Fund gave the p5js folks a €45

I think the key reason why this link has been posted to HN now is because p5js has a new website? Back in 2023 the Sovereign Tech Fund gave the p5js folks a €450k grant[1] "to enhance p5.js Documentation organization & accessibility" and this seems to be some of the results of that investment. In my view, it seems to be paying off - the site feels a lot easier to navigate and search, with more useful information. For example, compare the old[2] and new[3][4] versions of how to use p5js editor/canvases with a screen reader. [1] - STF announcement/progress - https://p5js.org/events/stf-2024/ https://p5js.org/events/stf-2024/ [2] - Using p5 with a screen reader (old version) - https://archive.p5js.org/learn/p5-screen-reader.html https://archive.p5js.org/learn/p5-screen-reader.html [3] - How to Use the p5.js Web Editor with a Screen Reader (new) - https://p5js.org/tutorials/p5js-with-screen-reader/ https://p5js.org/tutorials/p5js-with-screen-reader/ [4] - Writing Accessible Canvas Descriptions (new) - https://p5js.org/tutorials/writing-accessible-canvas-descriptions/ https://p5js.org/tutorials/writing-accessible-canvas-descrip...

kapep 2y ago
It's nice that they keep the old site available as https://archive.p5js.org/ https://archive.p5js.org/ I'm not a fan of the layout on large screens though. The linked tutorial [1] is fixed width left-aligned paragraphs, which makes right half of my display empty. On the other hand, other elements like on the reference overview [2] are stretched in four columns across the whole display which looks ok when the browser window is half my displays width but is hard to read when the window is maximized. [1]: https://p5js.org/tutorials/p5js-with-screen-reader/ https://p5js.org/tutorials/p5js-with-screen-reader/ [2]: https://p5js.org/reference/ https://p5js.org/reference/
petercooper 2y ago
We also featured it quite prominently in yesterday's JavaScript Weekly. With ~175k subscribers, things we include often make it to HN front page hours later. It's next to impossible to actually prove the connection.. but it's just part of the fun of how links spread around the ecosystem for me :-)
- slorber 2y ago
  Impossible yet it often happens the same old link gets featured everywhere at the same time :)
larodi 2y ago
Recently did a digital ad entirely in processing and then ported it to p5js. In my experience with it… * processing is still much easier to work, even though p5js seems to catch-up. I did work with it like 10 years ago and it was already very easy * it was very easy to spot bugs or missing implementation in p5js * While an almost identical port was possible, it’s not 1:1 and takes learning some APIs * p5js is not even close to d3 or three.js in terms of performance * tbh it seems to me lot easier to animate in web with modern css3 and some helper libs, than use p5js. In fact I would see a very straight pipeline from free vector apps into css with very little shading without p5js. Which makes me wonder how is p5js relevant in 2024, apart from educational tool. * For things which involve pixel level compute there is no easy way to use the GPU efficiently For me this whole 450k funding is quite bizarre, and in particular the fact it got directed to a not so popular framework.
- zyklonix 2y ago
  These are some great insights! Thanks for summarizing them. It will save me a lot of time in the future. I would love to see this digital ad! Is it public?
  - larodi 2y ago
    perhaps this link works https://t.me/dubec/300 https://t.me/dubec/300 * the images are generated with midjourney * the transition in this particular one is the export of processing * the track is from Babe Roots' incredible Sufferation Time - https://baberoots.bandcamp.com/track/sufferation-time-babe-roots-rmx https://baberoots.bandcamp.com/track/sufferation-time-babe-r... the p5js part was more challenging, as I had to only draw every 5th pixel every frame, in order to get some decent performance. but since this is a transition, you can't mention it. the whole loop is not much, but took a good 6 hours to get together. then another 4-5 go rewrite it for web. repo https://github.com/stelf/dubsinth https://github.com/stelf/dubsinth
- ralusek 2y ago
  Regarding performance, I once had an experience that I never bothered to look into. I made a cool little interactive simulation in the p5js sandbox; ran flawlessly. I then copy pasted it into a codesandbox, and it was choppy and abysmal. I checked the version numbers and how it was being included and couldn’t see anything obvious. Maybe codesandbox has some isolation that is taxing? Like I said, never looked into it.
j45 2y ago
The old site was decent and already mobile responsive. The new site is more mobile optimized and makes it possible to read more on the higher density screens. Discovery of p5.js is well deserved, as are the related coding train videos.

kapep 2y ago

It's nice that they keep the old site available as https://archive.p5js.org/ https://archive.p5js.org/ I'm not a fan of the layout on large screens though. The linked tutorial [1] is fixed width left-aligned paragraphs, which makes right half of my display empty. On the other hand, other elements like on the reference overview [2] are stretched in four columns across the whole display which looks ok when the browser window is half my displays width but is hard to read when the window is maximized. [1]: https://p5js.org/tutorials/p5js-with-screen-reader/ https://p5js.org/tutorials/p5js-with-screen-reader/ [2]: https://p5js.org/reference/ https://p5js.org/reference/

petercooper 2y ago

We also featured it quite prominently in yesterday's JavaScript Weekly. With ~175k subscribers, things we include often make it to HN front page hours later. It's next to impossible to actually prove the connection.. but it's just part of the fun of how links spread around the ecosystem for me :-)

slorber 2y ago
Impossible yet it often happens the same old link gets featured everywhere at the same time :)

larodi 2y ago

Recently did a digital ad entirely in processing and then ported it to p5js. In my experience with it… * processing is still much easier to work, even though p5js seems to catch-up. I did work with it like 10 years ago and it was already very easy * it was very easy to spot bugs or missing implementation in p5js * While an almost identical port was possible, it’s not 1:1 and takes learning some APIs * p5js is not even close to d3 or three.js in terms of performance * tbh it seems to me lot easier to animate in web with modern css3 and some helper libs, than use p5js. In fact I would see a very straight pipeline from free vector apps into css with very little shading without p5js. Which makes me wonder how is p5js relevant in 2024, apart from educational tool. * For things which involve pixel level compute there is no easy way to use the GPU efficiently For me this whole 450k funding is quite bizarre, and in particular the fact it got directed to a not so popular framework.

zyklonix 2y ago
These are some great insights! Thanks for summarizing them. It will save me a lot of time in the future. I would love to see this digital ad! Is it public?
- larodi 2y ago
  perhaps this link works https://t.me/dubec/300 https://t.me/dubec/300 * the images are generated with midjourney * the transition in this particular one is the export of processing * the track is from Babe Roots' incredible Sufferation Time - https://baberoots.bandcamp.com/track/sufferation-time-babe-roots-rmx https://baberoots.bandcamp.com/track/sufferation-time-babe-r... the p5js part was more challenging, as I had to only draw every 5th pixel every frame, in order to get some decent performance. but since this is a transition, you can't mention it. the whole loop is not much, but took a good 6 hours to get together. then another 4-5 go rewrite it for web. repo https://github.com/stelf/dubsinth https://github.com/stelf/dubsinth
ralusek 2y ago
Regarding performance, I once had an experience that I never bothered to look into. I made a cool little interactive simulation in the p5js sandbox; ran flawlessly. I then copy pasted it into a codesandbox, and it was choppy and abysmal. I checked the version numbers and how it was being included and couldn’t see anything obvious. Maybe codesandbox has some isolation that is taxing? Like I said, never looked into it.

j45 2y ago

The old site was decent and already mobile responsive. The new site is more mobile optimized and makes it possible to read more on the higher density screens. Discovery of p5.js is well deserved, as are the related coding train videos.