shovel knight

jobibu's portal

if you have any comments or feedback, send it over to my email

also please check out the wiki

and merely a test in development

note: active for

todos

all shovel knight pictures and media: yacht club games's creative commons 4.0

moving on from react

to say the least, a bit conflicted here.

i started learning webdev for... well not exactly webdev. more of being able to decorate simple sites with aesthetics like if i was sketching multitudes of storyboards.

so i started with simple html and css to then try out 11ty and most recently (which took me most of my time), test out js then react. and this put me on two crossroads:

the thing is, i love how clean my beginner-react thought process was. building components and being able to specify what and how aspects of my site is to look. but, and maybe because i haven't delved into js functionality or reactivity, but the idea of building much more complex webapps (which react is meant for) kind of leans towards more of the backend. more application logic which strays away from my simple goal of building art on sites.

and this article kind of encapsulates that. react and other js frameworks (and tools) have grown beyond sprinkling js on websites. they were now an all-or-nothing approach. full stack. and maybe it's a skill issue right now but i'm not sure if that's what i want to do. i don't know if i want to worry about worrying and working on the backend when it's the frontend that i want to do.

not sure if this rant makes sense but i'll come back to rewrite this. working on understanding on how react work took me out of commission on writing on this site and i feel like my writing has suffered a bit as a result.