Spotify pays artists based on how many listens their songs get, so if you can get a bunch of bots to stream your music over and over you can get a legitimate income stream.

In this case, they’re using their illegal income to pay people to use a botnet to stream their songs - which then means they have a nice legal income instead.

https://docs.netlify.com/configure-builds/overview/?#basic-build-settings

You just need to configure your build command and most likely your publish directory. Netlify honestly makes it really easy.

The build command is whatever you’d type in your terminal to compile your react app, and the publish directory is wherever your build command creates your static assets.

Those look like small cards. But why not just inspect the page and grab the CSS if you’re so focused in re-creating them? Why try to find and shoehorn a component from a UI library to look exactly like that when your browser will tell you exactly how it looks the way it does?

That’s a little pedantic, don’t you think?

I like to draw my pages out on graph paper, then just use position: absolute and tons of media queries to place everything with x and y coordinates. It’s the ultimate grid system.

I would absolutely consider shipping non-minified bootstrap doing something wrong

There’s nothing to stop an admin from hosting a static front end for their Lemmy instance if they’d rather, but it’s clear that SSR is a goal here - and I think the default UI for Lemmy really should include SSR for plenty of reasons. And, if you’re already hosting a Lemmy instance, you definitely already have a host that can support Rust (at the very least, in a container).

TypeScript is essentially the “measure twice, cut once” approach to JavaScript.

Yeah, anything can be anything in JS and the type declarations don’t make it into the compiled JS, but allowing anything to be anything starts to become fairly dangerous when the size of your projects starts to grow and especially when you’re working with a team.

Rather than writing functions and just hoping they always get called with a parameter that has the properties you expect to use, TypeScript helps you make sure that you always are calling that function with the right object in the arguments. You don’t need to debug some runtime error up and down 8 frames in the call stack because this week you named a property “maxValue” but last week you used “maxVal” or you forgot to parseInt some string because you thought it would be coerced - you just need to make sure your types match and eliminate that type of debugging altogether.

All in all, TS really just enforces a bit of sanity to the foot gun that is vanilla JS.

https://think-like-a-git.net/