Surely it’s because they want to increase the amount they pay the musicians.

If you like to upload your own music (like Google music), iBroadcast is the tippy tops. You can still use bandcamp (with or without yt-dlp) for discovery, and then upload what you like to iBroadcast.

iBroadcast is what i use. That plus rutracker and you can sail the high seas like it’s 1699.

HTML is pretty straightforward so just understanding the very basic stuff is probably all you need. CSS is where html gets any challenge it might have.

CSS is weird because it’s very “easy” so “real developers” kind of object to learning it, but the truth is, if you gave any of them a layout design, they probably couldn’t build it. There are tools like tailwind to help, but, IMO, tailwind just helps you avoid learning css’s vocabulary, but you just replace it with having to learn tailwind’s vocabulary.

JavaScript on the other hand is a “real” programming language, though decidedly quick-n-dirtier than other languages. It lets you be a lot more sloppy. (Tbh it’s a lot more forgiving than css!). As a result, it lacks the elegance and control that “real developers” like – and, as most people’s first language, it lets newcomers get into bad habits. For these reasons, JavaScript is a bit derided – but, unlike CSS, most developers can’t avoid it.

There are a few key ideas in JavaScript that, once you understand them, things make a lot more sense. (I won’t get into them now, since it doesn’t sound like you’re at the point where that kind of clarity would help, but, when you are, come on back here and make a post!)

TLDR: HTML is definitely something you can just pick up along the way. JavaScript is a real language that will take a little while to feel comfortable with, and it will take a career to master. CSS will never be easy, so don’t let it hold you back.

Hi everyone, JP here. This person is making a reference to the Weird Al biopic, and if you haven’t seen it, you should.

Weird Al is an incredible person and has been through so much. I had no idea what a roller coaster his life has been! I always knew he was talented but i definitely didn’t know how strong he is.

His autobiography will go down in history as one of the most powerful and compelling and honest stories ever told. If you haven’t seen it, you really, really should.

ITT NO SPOILERS PLS

I dated a girl named Password for a while. She was a lot older than me, she was born in the year 1234.

Anyway, @op the exact same thing happened to me. I gotta get smarter about opsec.

Follow up question – I’m not OP but I’m another not-really-new developer (5 years professional xp) that has 0 experience working with others:

I have trouble understanding where to go on the spectrum of “light touch” and “doing a really good job”. (Tldr) How should a contributor gauge whether to make big changes to “do it right” or to do it a little hacky just to get the job done?

For example, I wanted to make a dark mode for a site i use, so i pulled the sites’s repo down and got into it.

The CSS was a mess. I’ve done dark modes for a bunch of my own projects, and I basically just assign variables (–foreground-color, --background-color), and then swap their assignments by the presence or absence of a “.dark-mode” class in the body tag.

But the site had like 30 shades of every color, like, imperceptibly different shades of red or green. My guess was the person used a color picker and just eyeballed it.

If the site was mine, I would normalize them all but there was such a range – some being more than 10-15% different from each other – so i tried to strike a balance in my normalization. I felt unsure whether this was done by someone who just doesn’t give a crap about color/CSS or if it was carefully considered color selection.

My PR wasn’t accepted (though the devs had said in discord that i could/should submit a PR for it). I don’t mind that it wasn’t accepted, but i just don’t know why. I don’t want to accidentally step on toes or to violate dev culture norms.

The 8gb ram MacBook works great for […] writing resumes…

Um I’m not sure where you heard that but ChatGPT requires a shit ton of memory

(Sorry, I’ll show myself out)

I still get block messages in Vivaldi, but not Firefox.

Copy designs you like, and keep a couple of CSS files +/- web components that you can carry along with you from project to project. Tweak then as you go.

Like everything else, getting good at making designs that you like will take time and effort, so if you want you get good at it, do it! I find it fun, and my designs aren’t to everyone’s taste (I too like black tshirts), but whatever.

Plus, getting good at making designs that i like has made me better at making designs clients/projects will like, so, win/win.

jQuery is a lot smaller and less nebulous than its competitors (looking at you,React literally every JavaScript framework).

Jquery was what was popular when i learned js. I’m kinda glad it was, honestly: jQuery is a little unique in that it doesn’t have magic to it the way js frameworks do. Everything you can do in jQuery, you can do in vanilla JavaScript pretty easily. With, say, React, how is a newcomer supposed to understand how a series of React components become HTML?

So jQuery kept it “real” for me. Fewer abstractions between me and the HTML meant it was easier for me to connect the dots as a self taught developer.

As for how it’s changed, it’s more any how vanilla JavaScript has changed. A lot of the things that made jQuery so much easier and cleaner than vanilla are now baked in, like document.querySelector(), element.classList, createElement(), addEventListener()… It had Ajax methods that, before jQuery, were a tremendous pain in the ass.

jQuery was great, but, you basically had to use it with something like PHP, because it had no back end. So when angular came out (and a few others that aren’t around anymore and I’ve forgotten), it allowed you to replace both PHP and jQuery, and developers rejoiced.

Why did they rejoice? I’m not actually sure there was reason to, objectively speaking. As developers, we like new tech, especially if that new tech requires us to think about code differently, even if, in retrospect, it’s a hard argument to make to say that, if we had just stuck with PHP and jQuery we would be somehow worse off than we are with React.

Of course, in tech, when a new system changes how we think, sometimes (not as often as we’d like) it helps us reconsider problems and find much more elegant solutions. So, would we have all the innovations we have today if all these js frameworks has never existed? Obviously we can’t really answer that – but it’s a toke of copium for when we get nostalgic for the PHP/jQuery days.

(Also, for you newer people reading this, you should probably be aware that the PHP/jQuery mini-stack is still very quietly used. You’ll definitely see it, especially in php-baaed COTS.)

arguably, that’s a good thing because it means project decisions are made uncorrupted by profit motive

Argue-er here, chiming in. This statement could be interpreted as considering only half of the central relationship of capitalism. (Capitalism isn’t just about deriving profit from the control of surplus, it’s about the relationship between surplus and scarcity. Surplus doesn’t mean shit if no one wants what you have.)

The decisions that volunteers make may not be motivated by the desire/ability to make profit, but they can be (and often are) motivated by the opposite; they have to account for the fact that their volunteer work is labor that isn’t contributing to their survival – aka, their day job. The demands placed on them by their other responsibilities will have to take precedence over the volunteer project.

In practice, this means they have to take shortcuts and/or do less than they would like to, because they don’t have time to devote to it. It’s not exactly the same end product as if it was profit-seeking, since that can tempt maintainers into using dark patterns etc, but they’re similar.

Ideally, they would have all the money they needed, didn’t have to have regular jobs, but also had families/friends/hobbies that would keep them from over-engineering ffmpeg.

To say this in a simpler/shorter way (TD;DR), their decisions can be motivated by the fact that they aren’t making money from it, don’t have enough time or resources to do everything they might want.

(Why is this so long?? I’m bored in the train, gotta kill the time somehow…why not say in 1000 words what I could have said in 100)

And I’m sure Microsoft would be happy to not have to do it anymore. And I personally would much prefer an actual typing system rather than a glorified linter.

Tho I wonder if it will end up being like jQuery, in the sense that, by the time core jQuery features got added to vanilla js, jQuery had developed new features that validated its continued existence. Maybe TS will go further than what gets absorbed into JS and keep it alive.

Imo they’ll add typing to vanilla js, which will kill ts.

For sure. Look, I hate Stack Overflow as much as the next guy but you gotta admit, for the big picture, long term, best practice for the future of software development, that’s the correct format: one question, focused discussion, end.

Discord’s failure to make its history available is really going to put a big hole in the middle of our cultural wisdom.

Mumble does that one thing just fine, but it doesn’t do all the things discord does.

And it’s not just the fact that discord does all those things that’s made it so dominant; it’s the fact that it does all those things in one place.

Even just the core features of voice chat, text chat, and the ability to set up a new server where you have extensive moderation control in one click – it’s what people wanted.

They don’t need a handful of different programs to glue together a shittier experience, they need a FOSS discord/slack.

??? I hope you don’t actually think this

There’s no reason to require everyone on earth to prioritize a better computer interfacing environment over their free time.

My time is worth way more to me than video game voice chat – but it’s not either/or. Thanks to other developers, I can have both.

Edit: tldr: I think I probably could’ve saved myself a lot of time by just saying that discord is like slack but for friends/fun.

I didn’t think people use it like lemmy/Reddit. People use it like IRC. That’s the analogous tech. IRC is better in almost every way, but not in the most important ways: ease of use, and voice chat.

I know only a handful of people who could set up a server for IRC, but in discord, it’s a one-button process. Sure, you can use a public IRC server, but then your channels are harder to organize and you don’t have as much moderation control. I dn’t think

I would vastly prefer IRC, but even if it was easy to set up, I would still need something for voice chat, and, sure, there are plenty of voice chat tools, but not ones that integrate with text chat so well.

I think a lot of people like the API and the bots built from it, tho personally that’s not something I use much.

I’m in probably ~50 servers: groups of friends, video game guilds, tech chat (eg HTMX, Lit, Svelte), random interests (eg mechanical keyboards), and community servers for video games (eg a couple of LFG servers, a couple servers where I can ask questions to tryhards, streamers’ communities, etc).

I would vastly prefer to use something FOSS, but there just isn’t something that does it so well and so easily – and even then, I’d probably have to use discord for a bunch of these things.

Tell me it was “Top 10 Steven Universe Betrayals” without telling me it was “Top 10 Steven Universe Betrayals”

This is the core issue with the traditional dead man’s “switch” – it doesn’t require death to go off, just letting go of it, and there are other reasons why that might happen. By extension, a switch that requires you to log into something periodically might be problematic if you’re predisposed. Personally I’d just set a longer timer, a month is probably fine and, unless your “exposure” is extremely time sensitive, a month won’t matter once you’re dead.