As soon as you see those sections with bullet points you know.

You should’ve quoted the gpt part or mentioned it. That’s why people are upset, it seems misleading. I get why you did it though.

The bonus for vapes is you can wean off nicotine at a super precise rate. You can mix your nicotine juice with more and more non-nicotine juice to achieve greater and greater levels of dilution until the nicotine dose you’re taking is so low that it doesn’t matter to stop.

Different legislation in different places. My country banned flavours, but they still sell disposables somehow.

The first thing you described is literally what we used to have. God I miss the good old days of vaping.

YouTube music used to be good when it was Google music. But i think the app has been improving YouTube music is becoming better.

Oh yeah. Peak reddit years lol. Before the corporate enshittification.

Lemmy is good fun though, I definitely appreciate it.

Remember on reddit when we used to upvote an image with a completely unrelated word because we thought it’d be funny if the image popped up in a google search?

I understand what you’re saying and I mostly agree, but those few instances where a line of code is only slightly different and the comment is the same, can really be confusing.

I mean, boolean short circuit is a super idiomatic pattern in Javascript

Yeah. I advocate for self explanatory code, but I definitely don’t frown upon comments. Comments are super useful but soooo overused. I have coworkers that aren’t that great that would definitely comment on the most basic if statements. That’s why we have to push self explanatory code, because some beginners think they need to say:

//prints to the console
console.log("hello world");

I think by my logic, comments are kind of an advanced level concept, lol. Like you shouldn’t really start using comments often until you’re writing some pretty complex code, or using a giant codebase.

“Version numbers could be [dead]”

… Do they think version numbers don’t have a purpose, or that they’re just for marketing? It’s pretty helpful to know breaking changes vs non-breaking changes in a version number

Meh, it’s not like the data is monitored by people, it would probably just be like dropping a needle of bad data in a haystack of automated data.

Most of the stuff here can be avoided by using quotes for strings…

Yeah but Haskell is mostly used by mathematicians…

People hate hearing that they are bad coders 😂

You and the other guy are saying to focus on writing code with less indentation and using smaller methods, and you both got downvoted.

I fully agree, small methods all the way, and when that’s not possible it’s time to refactor into possibility!

But it’s not a markup language… It’s for data serialisation…

For me it just depends on what I expect. They’re all relatively the same thing. As long as the status code is appropriate (403), it doesn’t matter whether it’s JSON or plaintext. Ideally the API would respect and handle the request header, and return plaintext if you request plaintext.

I agree with your point, but our algorithms are not deterministic and I doubt they ever will be again. Perhaps they could use a set of tags to create a deterministic result for a certain “genre” of results.

I mean of course that would be nice, but that’s just not realistic. You can’t store that info in a link without it being monstrous.

Why do you say they couldn’t cache the results and instead of re-fetching everything just use the cache results?