p5.js
11–20 of 73 posts
Re: p5.js
#12Re: p5.js
#13This is a really pretty website! I'm surprised that they decided to take out the part in the About section mentioning that this is a continuation of the ideas from Processing - I guess maybe now P5.js is more popular than processing is/was?
Re: p5.js
#14Re: p5.js
#15Re: p5.js
#16I 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…
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/ [2]: https://p5js.org/reference/
Re: p5.js
#17I 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…
Re: p5.js
#18I 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…
* 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.
Re: p5.js
#19This is a really pretty website! I'm surprised that they decided to take out the part in the About section mentioning that this is a continuation of the ideas from Processing - I guess maybe now P5.js is more popular than processing is/was?
There was a schism between Ben Fry and the Processing Foundation, so I would reckon it's political. One of his chief complaints was how the p5.js project had taken over the Processing Foundation and minimized Processing development.
Re: p5.js
#20https://news.ycombinator.com/item?id=37760363
Knowing what I know now I regret supporting the work of Processing Foundation.