am I to infer that patenting (which discloses the method by which things are accomplished for future generations) is considered morally inferior to selling a black box
I mean either way you're trying to get money for your ideas
I hear certain things are intentionally not patented to keep the "secret sauce". Also, I guess it'd be pretty hard to prove someone used your patented idea in their software
Those tests were done with `mi 2021.06.15. The pre-filled pattern version doesn't work at all in `mi 2021.06.21`. I'm guessing that's because the `b` suffix does something different in the more recent version:
@Razetime i think such a project would have to involve at least one person who understands both graphics and k, like JohnEarnest or ktye. i could contribute only a little (probably no more than 1 hour/day), regardless of whether it's built on ngn/k or not
@Razetime @ngn you also need to agree on what you want to do. 3d gpu access, 2d bitmaps with events, 2d canvas with vector api or use a full gui toolkit? should it work standalone as an executable or for the web/wasm only?
My mid-term plan is a data-oriented (html/js) ui interface for the online version.
I was wondering if there is tooling that would make sense to share/make compatible with various k implementations (that said: not sure what that could be or look like)
@tosh when i started with k, i just wanted to right a "small lists/cheatsheet" with differences between the versions. i gave up quickly. i don't think a tool would work.
yeah makes sense, it might also not be desirable to have converging/compatible implementations and also tooling for ides does not seem that important for k
one half-baked idea I had was something like a data lake where you have stuff like taxi dataset, tick data, genome sequencing data and coding riddles like project euler and so on and an easy way to load data and select a runtime
then again a zip with files would probably also do the job
@Razetime is a web version ok? in my opinion it's more fun as you can share your games/animations and discuss with others. very few people would follow your "build instructions" for a native application/download examples and run them, vs clicking a link.
@Razetime you can decide for yourself after using iKe for a bit, but I think the main thing I would have done differently if I remade iKe from scratch would be to add a symbol to the beginning of each of the drawing tuple types which identify them (b for bitmap, p for polygon, something like that) since it would make the set of drawing operations more extensible
there's an elegance to just having two drawing operations but expanding it slightly might be nice; having a proper line type, for example, or perhaps a text rendering tuple
it would make programs slightly longer, but in the scheme of things it doesn't matter