I've got my 3D glyph rendering system at glyph3d.dev, and use cases like this help accelerate layout and relationship development immensely. I greatly appreciate your sharing this!

Would you happen to have a trove of similar research or papers I could sponge off of you? Or maybe even a few minutes of your time in some chats / emails to discuss how these tools can be brought to a modern runtime?

This is a standard three.js implementation with just some fancy shaders and loading primitives. If you looked at the IDE demo, that's basically the test bed I use for rendering. The library is available in NPM (I can update to latest this evening if you'd like to pull it that way) and it's meant to be composable, as are the app tools and field abstractions.

My hope is that it means import as a dep, call into the bootstrap, and then you can place a "glyph field" node wherever ya want and stream text and buffer updates to it.

Well done creating A Cool Thing!

Are you truly curious as to how it might not be A Good Thing that those engaging in high-finance capitalistic money making programs would have access to forcefully engaging a human being's brain into activity, with or without their consent, to such an extent as to drive motivations and bias neuronal activation that leads to what they think is a choice?

Said another way: Are you really curious as to how allowing a company additional tools to bias human interactions may not be A Good Thing?

If you need an example as to how this is clearly not A Good Thing, and that at least a portion of the world population agrees with that characteristic, that there are currently companies that have tried to actively do this already, and attempts are being made at least to fine them for their behavior as an attempt to curb it. Whether or not it succeeds is a question of governance at the moment since the US is currently under plutocratic control.

However, I would really urge you to explore this topic and really engage with what's happening due to the plutocratic class' capabilities over technologic change and societally enforced or biased adoption, and how they, in many extreme cases that are continuing to become more extreme, are not A Good Thing.

Simplest, most readily available example: https://ground.news/article/meta-says-us-states-are-seeking-...

I built a truly glyph based instanced quad system to render millions of characters in space at once.

This is not a game of having done X good things in life and therefore being afforded the right to do Y bad things. You are making a choice to say, "I am allowing myself to treat this thing I believe is lesser than me in a way I willingly acknowledge is bad." That's your thesis. I wholeheartedly disagree with it.

Don't normalize being an asshole to anyone or anything, machine or not.

Comments URL: https://news.ycombinator.com/item?id=48295953

Points: 3

# Comments: 1

Thank you for being honest that talking to AI is tiring. I hope my human words, as angry as they are, afford a little more.. humanness in your life, should that be a thing ya actually still want.

Happy to chat whenever you'd like, I can stalk a contact for ya or vice versa!

Second: I would love to offer any assistance during your perusal. Happy to share ideas, what I tried, point out parts of the code that are rough and tumble, whatever helps. I'm in a place where any outside feedback and prodding is precious, so thanks very much for taking a look and keeping it in mind!

Second: Thanks for the confirmation! If you've got any thoughts or feedback, please be as direct as you'd like - I've already started cleaning up some of the more 'user friendly' notes I've been neglecting in an effort to stick to the internals.

Second up: I'd love some input as to what didn't work! Did a shader fail to load? Desktop or mobile? Did you load a repository that was too large and OOM'd out in the browser? Did it cause your monitor to spin 360 degrees and speak tongues? Do tell!

For you: You're probably right about "not seeming useful", but I do wanna gently nudge you toward what this is a proof of concept about again. Most folks look at this like it's a bigger, flatter emacs/vim/Sublime/VSCode or whatever. I do support editing in my current workbranch, as well as command-based selection, but most of the work spins out because the tool is half "adopt what tools are useful to an interactive development environment of today" and "allow the display of the canvas to overlap with the spatial relationships of directories, files, and colocation to help generate mental mappings of a code space".

These things have often been in conflict, and years (decades) of prior art show this. This is my attempt at it, and since it's my 3rd attempt in twice as many years to make it work in a new environment, you're hitting this particular instance's walls. Would love more feedback or questions!

For you: The 'tab' layout is pretty atrocious even as a one-shot run through of fitting most of the control areas to mobile and desktop screens. It's not easy, and a lot of 'feature' bloat makes it worse. Knowing what your first-time drop in was like and how you found that link is incredibly useful insight, and I'll be updating the layouts more to accompany first timers and instructions like the original source material I'm rebuilding from on the Apple side.