wow i love making interfaces i sure hope i never have to connect it to any logic 
Replying to @kopper@not-brain.d.on-t.work
alternate caption: "when you see it you will want to fuck it - stewie "jobs" wonder, inventor of fruity gal aero"
Replying to @kopper@not-brain.d.on-t.work
ok let me clarify if this happens it's gonna replace outpost-fe.w.on-t.work i'm still no longer doing a backend
Replying to @kopper@not-brain.d.on-t.work
throwing the code at git.gay/kopper/outpost-fe-2 so i can later steal the tricks for other things i will also subsequently abandon
Replying to @kopper@not-brain.d.on-t.work
worried i may have made my buttons too bouncy
Replying to @kopper@not-brain.d.on-t.work
pl-api is the largest dependency on the bundle so far and i dont want to rewrite it its so much busywork i wish it wasnt a single massive un-tree-shakable class
Replying to @kopper@not-brain.d.on-t.work
do i reaaally need the code to call the pleroma admin api?
Replying to @kopper@not-brain.d.on-t.work
i love microoptimizing things that will not matter
git.gay/kopper/outpost-fe-2/commit/064d5234cdf0efa0ad4a9615fea70026eceb1051
git.gay/kopper/outpost-fe-2/commit/064d5234cdf0efa0ad4a9615fea70026eceb1051
Replying to @kopper@not-brain.d.on-t.work
ok i think im gonna roll back the data loading system i tried to make and instead Just Not Care About Having One Source Of Truth For What A Post Says because it turns out svelte is only really made for sveltekit and doesn't let you do anything cool by yourself like having a derived that returns a reference counted value that doesn't want to make you hate yourself when using or literally anything involving async that isn't Just A Fetch
you would think that you can call a function in a component and have that function do everything the component itself can do. you would think that wouldnt you. yeah you would.
you would think that you can call a function in a component and have that function do everything the component itself can do. you would think that wouldnt you. yeah you would.
Replying to @kopper@not-brain.d.on-t.work
the current state of things will live here once git.gay accepts my push so if anyone wants to take on the challenge they can: git.gay/kopper/outpost-fe-2/src/branch/experiment/single-source-of-truth
Replying to @kopper@not-brain.d.on-t.work
slowly coming up to the conclusion that it's impossible to have a coherent mental model of svelte. reactivity broke? Randomly Throw Closures Until It Works. context doesnt work here? Move The Set Above The Async? you need the async value in the context? You Would Think You Can't Because Of The Previous -- But You Can If You Pass It To Another Component That Wraps All Your Other Components. got an error message? This Is All You're Getting. Good Luck
Replying to @kopper@not-brain.d.on-t.work
there's like 10 different contexts your code can be in at any given time and they all hate each other and all of them can be in the same exact file and even scope
Replying to @kopper@not-brain.d.on-t.work
want to use the "legacy" stores because they let you replace $effect for your reference counting? you gotta declare them in the top level script. you have a recursive reply tree of them? FUCK YOU SUCK MY DICK GOT 10 ASLDKJILLION DOLLAR INVESTMENT FROM VERCEL
Replying to @kopper@not-brain.d.on-t.work
@kopper sometimes i really want to rewrite svelte to my own image, no compiler, just signals and jsx transpiler
Replying to @eater@cijber.social
@eater so... solid?
Replying to @kopper@not-brain.d.on-t.work
@kopper i dont think so
in my little perfect world it would use a user defined Observable objects and collections which allow for a way better way to update cycles, without the abuse of proxies or deepobject diffing
i mean i assume there's a reason both, Windows XAML and JavaFX highly rely on observer pattern
Replying to @eater@cijber.social
@kopper current nerd sniping levels: I've implemented a generational arena in typescript
Replying to @eater@cijber.social
@kopper return to Java Observable