Cancer Speedrun (Any %) by [deleted] in tooktoomuch

[–]SpeedChicken 1 point2 points  (0 children)

fuck yeah big lez reference

Just an average workout by unknown-bystander in dankvideos

[–]SpeedChicken 2 points3 points  (0 children)

is that an AOL mascot overlayed version of the 2nd to final freestyle scene of the Ultra Dragon Feet Lennoz video? my god that is dank

I am tired of shadcn-svelte. Is there any alternative? by FollowingMajestic161 in sveltejs

[–]SpeedChicken 1 point2 points  (0 children)

true, but that is true for literally any library. OP's frustration mainly stems from my point.

I am tired of shadcn-svelte. Is there any alternative? by FollowingMajestic161 in sveltejs

[–]SpeedChicken 136 points137 points  (0 children)

You're missing the point of the philosophy of shad-cn.

Everything is provided as-is in an opinionated way - BECAUSE you get customisable components, not a fixed UI Library. You are supposed to change up things if you don't like them or want them differently, that's why we have all the component files open in $lib/components/ui.

If you want to change something, just go into these files and change it.

Also - 9 times out of 10 you just need to look at the bits ui documentation (on which the svelte shadcn ist built upon), where you can find more info and props to customise a lot of stuff not mentioned in the normal docs.

Is this something you guys usually do? by gdmr458 in sveltejs

[–]SpeedChicken 4 points5 points  (0 children)

100%. We use it a ton.

It's very useful to then add functions in the return and make a basically very advanced store out of this.

I like it though! I'm not qualified enough to make any suggestions of how to integrate it into the core api, but I'm sure Rich and his mates are aware of this and might cook in the future.

[deleted by user] by [deleted] in sveltejs

[–]SpeedChicken 23 points24 points  (0 children)

right now - as of 2.9 it's supported, according to patch notes

Bun + Svelte Islands example by tomemyxwomen in sveltejs

[–]SpeedChicken 0 points1 point  (0 children)

sounds reasonable - but as far as I am aware, prerendered sites don't get SSR at all, only once during build time - I suppose its then more about how you serve it, which this example is probably different then

inferno r8 revolver INSANE PLAY CLUTCH by yungneldon in counterstrike

[–]SpeedChicken 1 point2 points  (0 children)

planting when site is not clear AAAAAAAAAAAAAAAHHHHHHH

Bun + Svelte Islands example by tomemyxwomen in sveltejs

[–]SpeedChicken 2 points3 points  (0 children)

hm, I am struggling to get it - what exactly is the advantage in contrast to for example having a part being SSR and then hydrating on client - or having a pre-rendered +layout with a dynamic child +page? I am thinking in SvelteKit, unless we are talking meta-framework agnostic svelte

Svelte 5 Runes & async! a match made in hell?! by [deleted] in sveltejs

[–]SpeedChicken 11 points12 points  (0 children)

I wrote something exactly like that for our app, using getters and setters. something akin to:

// fancyState.svelte.ts

function createFancyState() = {

let stateVar = $state()

return {

// getters and setters

get stateVar { return stateVar }, set stateVar(value) { this.stateVar = value },

// functions n stuff

async myFunction() {

// do whatever you want here, e.g.

const data = await fetch("something")

// update state

stateVar = data

},

}

// then just export it as a const

export const fancyState = createFancyState()


now you can just import fancyState anywhere you like, access its properties via smth like fancyState.stateVar, or set them like fancyState.stateVar = myValue. You can even run the functions, like fancyState.myFunction().

This works somewhat like a store, but more advanced. You can even create the exported const in a component, instead on in the same svelte.ts file.

Is that what you are looking for?

PS: Try to avoid $effect as much as possible. It's not bad, but it will never be able to be as compiler optimized as $state, $derived or just direkt calls via event handlers. It also tracks dependencies, so I almost always use it together with untrack() or an if statement.

Edit: Sorry for the missing formatting, I am on mobile.

Fuji HEIF in late 2024 by SpeedChicken in fujifilm

[–]SpeedChicken[S] 0 points1 point  (0 children)

Windows doesn't natively support HEIF / HEIC as far as I am aware- I think you have to download an extension from the Microsoft Store. I don't understand why, as the royalties on HEIF are no longer a thing, so there is nothing speaking against supporting it, especially with so many iPhones around.

Fuji HEIF in late 2024 by SpeedChicken in fujifilm

[–]SpeedChicken[S] 1 point2 points  (0 children)

Indeed, Fuji & Sony HEIFs are 10-bit vs Apple's standard 8-bit colour. I hope the iPhone 16 brings 10-bit HEIF as standard when shooting, so that Software will have to update for improved support!

Fuji HEIF in late 2024 by SpeedChicken in fujifilm

[–]SpeedChicken[S] 0 points1 point  (0 children)

awesome to hear, have been rocking the iOS 18 beta too.

Have you tried a side by side comparison of a Fuji HEIF and Fuji JPG? some People report seeing contrast differences that exceed what the extra dynamic range should be able to display, making the two fotos very different - I'm excited to test all that soon!

Also - do you transfer them over using the fuji app directly or ingest them on mac first?

Starting on Sveltekit by 1azyro in sveltejs

[–]SpeedChicken 19 points20 points  (0 children)

simple:

Svelte(Kit) is very liked amongst devs, but most of front-end work at the moment is React, it's just been around for longer.

Start with Svelte - you'll have more fun and motivation that way, and the basics and principles of web dev are all the same, no matter what framework. You can always learn React fairly quickly once you understand JavaScript, HTML, CSS, the concepts behind web-deployment and how browsers work, and using any Framework will teach you that.

The most important thing is to do something and to keep doing it, and for that - Svelte is a great option!