13 ms·

SvelteKit is amazing. I disagree about Skeleton though. Skeleton makes you feel productive and safe at first but it has a lot of foot-guns. It leads you down a

SvelteKit is amazing. I disagree about Skeleton though. Skeleton makes you feel productive and safe at first but it has a lot of foot-guns. It leads you down a happy path until you don't like something and then it's difficult to customize. You're much better off using DaisyUI or something headless like MeltUI when it's ready. Take a look at Skeleton's own site https://www.skeleton.dev/docs/get-started https://www.skeleton.dev/docs/get-started Press page down - no scrolling happens. Hover your mouse over the navbar - no scrolling. Print the page - the content is cropped to only what's shown on the screen. I've raised this with them and it hasn't been a huge priority yet tones of sites are using this pattern from the <AppShell> component. Skeleton thinks you can just take your dark theme, invert the colours and end up with a decent looking light theme which just isn't the case. With DaisyUI you get a more mature/performant/popular framework that takes accessibility seriously. It's amazing what they can achieve with just CSS animations and no JS. It solves the hard part (HTML, CSS) and let's you write the easy part (Svelte). You're also less locked into Svelte - you can much easily pull your DaisyUI html into a different framework.

Sammi 3y ago
My wife does UX. I showed her Skeleton and she launched into listing all their UX mistakes on their website...
roblh 3y ago
This is good to know! I’ll try out DaisyUI next! My favourite part about skeleton has been having mostly functional, pre-existing component classes. The svelte material ui (smui?) library left a lot to be desired there, and I like how easy it is the modify the skeleton ones, since they aren’t a horrible jumbled mess of tags like all of the Vuetify components are below the surface. My least favourite part of tailwind is needing a stock button and having to add 80 characters worth of class stuff just to get a generic looking button, which is what skeleton solves for me.
- DLA 3y ago
  Very happy DaisyUI user here. While I like tailwind, I have to agree that for simple things like buttons as mentioning above, it sure is verbose. One of the best aspects of DaisyUI is the wealth of ready-made elements that have very reasonable defaults which often need very little to no tweaking. Of course, you can adjust them as needed very easily. Since we’re on the topic let’s complete the stack: Using DaisyUI and a small GoFiber.io server running Go stdlib HTML templates, I’m able to crank out high performance web apps with minimal fuss. By using the embedding feature in the Go compiler you can ball everything up into a single deployable binary. For in-page interactivity, I like htmx and/or AlpineJS, depending on the use case. No NodeJS dependencies in sight!
hinkley 3y ago
I mean it’s called skeleton. If it weren’t anemic we’d be wondering what happened.

Sammi 3y ago

My wife does UX. I showed her Skeleton and she launched into listing all their UX mistakes on their website...

roblh 3y ago

This is good to know! I’ll try out DaisyUI next! My favourite part about skeleton has been having mostly functional, pre-existing component classes. The svelte material ui (smui?) library left a lot to be desired there, and I like how easy it is the modify the skeleton ones, since they aren’t a horrible jumbled mess of tags like all of the Vuetify components are below the surface. My least favourite part of tailwind is needing a stock button and having to add 80 characters worth of class stuff just to get a generic looking button, which is what skeleton solves for me.

DLA 3y ago
Very happy DaisyUI user here. While I like tailwind, I have to agree that for simple things like buttons as mentioning above, it sure is verbose. One of the best aspects of DaisyUI is the wealth of ready-made elements that have very reasonable defaults which often need very little to no tweaking. Of course, you can adjust them as needed very easily. Since we’re on the topic let’s complete the stack: Using DaisyUI and a small GoFiber.io server running Go stdlib HTML templates, I’m able to crank out high performance web apps with minimal fuss. By using the embedding feature in the Go compiler you can ball everything up into a single deployable binary. For in-page interactivity, I like htmx and/or AlpineJS, depending on the use case. No NodeJS dependencies in sight!

hinkley 3y ago

I mean it’s called skeleton. If it weren’t anemic we’d be wondering what happened.