corru

architect of https://corru.observer

to navigate my twisted maze of a page... you must utilize the pinned tags!!

.observer - all corru.observer stuff
.news - any WIP snippets or updates
.askserver - cohost Q&A's
.works - other creations

you can ask me stuff even if you don't have an account! i read everything I get, but I may not answer everything (I see you kind words posters)


my dimension: corru.observer
corru.observer/

Anonymous Guest asked:

I've looked through your sites, but was unsuccessful - have you ever done a little writeup of what you use for corru.observer? I would love to know if you basically handcode it, or if it is done in an engine and exported for browser? <3

hello mystery friend!! I have not written about it, but it is basically hand-coded! I use vanilla HTML, JS, and CSS for pretty much everything, however to actually generate the pages, I use Jekyll! all of the pages in the site start as markdown files with a bunch of custom inputs I set up (mostly controlling page lifecycle events), which are then converted to HTML when I do the site build.

is this crazy in the year of our lord 2023, where JS frameworks rule over all? maybe... idk... when I started working on this, I didn't know React or Svelte or anything like that - the kind of front-end work I do professionally is almost always vanilla just by virtue of the platforms I work on, so it's really familiar to me!

my interest at the start was in getting something made NOW with what I knew rather than spending more time learning a new engine or new process - I was really impatient, and honestly, it hasn't bitten me too bad yet. I'd still do it again! but I bet everything would run better if it were in Unity for Web or ThreeJS or something


in reply to @corru's post:

It might bite you someday if you end up wanting some complex 3d models but for everything corru does now native JS and CSS transforms like you've done this far are about the best and fastest thing to use for a webpage.

The thing is, it's not like webgl would magically unlock perf by letting you use the GPU, the browser will already use hardware acceleration if it thinks it needs it for a page or element. The web is fast, actually!

replies locked

this is true, it is really easy to write a lot of stuff that I do with just vanilla... honestly the only real snag has been that Chrome has this ~528mb (or something around there) visual memory limit regardless of specs, so I gotta be careful about the number, size and activity of graphics on screen or else things get mad flickery...

everyone has to go through optimization dilemmas no matter what they use, but it majorly sucks that it doesn't scale with computer specs!!

replies locked

Static site generation from Markdown is my favorite thing to do now. Takes off so much work from having to have Something Running In The Background just to host stuff (assuming you don't actually need it)

replies locked

Discard this post?

Are you sure you want to discard this post? This cannot be undone.