processing VS website

reply

I disagree. There are so many creative tools that are now online that you can access from your browser that were not envisioned in the original web. It is obviously true that not EVERY website is about creation (but to expect that seems unreasonable?), but even Wikipedia is a collaborative project.

Examples include products from big vendors like Adobe's Photoshop, to smaller products like SketchUp, to more indy generative art tools like https://processing.org and Strudel (https://news.ycombinator.com/item?id=39924210).

Would processing[0] be a good fit? It's designed to be easy to use and learn but powerful enough for professional use. Very quick to get cool stuff moving on a screen and the syntax is Java with a streamlined editing environment.

[0] https://processing.org/

I would personally use the language Processing. It's the one I use the most. And it's relatively easy to start drawing text, squares, and do other kinds of things. (It's kind of like java, but without all the boilerplate code)

Processing (P5) had this: you can select any string of text in its IDE anl search for it in the docs, and if it's one of the built-in functions or constants it will open the associated static html page that came installed with the software, so no internet nor server required. And despite being offline you can still navigate the docs too. This feels a lost basic skill in static site generation these days.

It was the only creative coding framework that had complete, offline documentation like that at the time I might add. OpenFrameworks is still mostly autogenerated stubs for example.

IMO it was one of the things that gave Processing an edge in educational contexts over all alternatives. I was pretty sad to see p5.js not fully continue that tradition and require that you go online to read the docs, and that it's not a static website but that text is rendered with javascript when you open it (still complete and with examples though).

https://processing.org/

https://p5js.org/

Processing is very cool, especially if you like graphics.

https://processing.org/

Processing is a flexible software sketchbook and a language for learning how to code. Since 2001, Processing has promoted software literacy within the visual arts and visual literacy within technology. There are tens of thousands of students, artists, designers, researchers, and hobbyists who use Processing for learning and prototyping.

And it's not even their IDE. They just slapped some AVR compilers into Processing

https://processing.org/

This happened few years ago I don't remember the specifics, but I find funny to see the exact confusion still around whats supposed to be a basic functionality here with the k8 devs themselves acknowledging lack of correct docs but doing little.

Great to know! Since the kubernetes/website repo currently lacks the tr localisation, I'm pretty sure starting it there would be much appreciated by the relevant community. This guide and the #sig-docs-localizations channel in Kubernetes Slack are the best starting points for those who might be interested in it.

From the doc:

Better is probably subjective, but you have options. You can run the doc website locally (https://github.com/kubernetes/website) or search the API definitions directly (https://github.com/kubernetes/api). Good ol `git grep` I suppose.

No, I don't think so. Killercoda is one of the main options currently being considered for moving from Katacoda. You can find this discussion here.

Kubernetes*

I'm unable to find any references other than this link that confirms that the failure has to be consecutive. https://github.com/kubernetes/website/issues/37414

Discover the full power of this feature in the docs.