(saying something more realistic like “2015” or whatever your inexperience or AI told you to)
User input is probably the big one where this API is gonna get stress-tested…
(saying something more realistic like “2015” or whatever your inexperience or AI told you to)
User input is probably the big one where this API is gonna get stress-tested…
Hmm, I can believe that it was based on java.util.Date
, but I don’t remember that being as unpredictable. I guess, a different API to begin with, would have avoided a lot of problems, though…
For testing new speakers, this song: http://dig.ccmixter.org/files/Robbero/59698
I’ll let the hivemind know that we’re supposed to have only one opinion.
On a definitely related note, I’ve recently been thinking it’s wild how we build foot paths out of rocks and then put on rubber socks for actually walking on them.
In other words, asphalt is a scam by Big Foot to sell more shoes.
I imagine, they can still get inflamed gums or similar, if something gets stuck in there…
I believe, you have to take turns pushing down individual teeth. By random chance, it will close the mouth when you do that. So, you lose when you get bitten.
I’m always amazed how badly companies understand the concept of human interaction. Showing appreciation requires putting in some amount of effort. If you just type some words into a box and an image comes out, that’s not anything. Might as well use the first clipart that comes up in image search…
The devs have access to the source code. Why would they put something like this two layers deep into the documentation? It’s like those people that think Mozilla is evil, because Mozilla openly talks about what they’re doing. If they wanted to be evil, you would know jackshit about it.
I feel like it’s just capitalism doing a capitalism. People are self-conscious about their skin, so you can sell them all kinds of crap.
Even a basic washcloth does a decent job with exfoliating, if you use it regularly. Rub your face dry with a scruffy towel, if you need more than that.
But of course, there’s hardly any money to be made with reasonably priced products, so you won’t see TV ads for them.
Should be noted that Ctrl+[Shift+]Tab behaves as you describe by default, but there’s a checkbox in the settings to make it go through tabs left-to-right, so it’s possible OP changed that behaviour…
Yeah, Lemmy is actually a decent software for this use-case…
In German, we also call the Netherlands “the low countries” (“die Niederlande”). 🙃
Apparently, “deutsch” originated from Medieval Latin “theodiscus”, which meant “belonging to the own people”.
German source: https://www.dwds.de/wb/Deutschland
900m. I live at the edge of town…
I agree that the default isn’t great, but from the link that @tal@lemmy.today had posted, there is actually a way to move the inventory button to where you want:
https://samsinventory.docs.luanti.org/files/videos/touchscreen-editor.mp4
So, they go into the menu, then press the “Exit” button.
Unfortunately, that video is already out of date again, as there’s now a general “Settings” button where the “Touchscreen Layout” button was. But in those settings, you can select the “Touchscreen” category and then that button is near the top.
Then it works like in the video again, by pressing “Add button” and so on.
Fun fact, it’s called “garlic” because it’s basically a gar-leek.
At first I thought, this was the same beats, just with staggered emphasis, but no, that’s 30 eighths in the timespan of 14 eighths.
So, it’s like the bassoons are playing sixteenth notes, except that they’re decidedly not in sync with everyone else.
At first it’ll sound like they’re too early. Then their offbeat sixteenth will sync up with the on-beat for everyone else. Then their offbeat will sound like it’s too early compared to the on-beat, until they sync up properly again. Well, and then you do that cycle a second time, because they have to fit two extra notes in there.
Yeah, that does seem quite impossible to conduct, but even if you set up two metronomes, that’ll throw even good orchestras quite easily…
lol and behold
I enjoy that as an expression. 🙃
It’s mainly horrid, because it means you have to code extremely defensively (or I guess, use a different API).
You can’t rely on
new Date("not a date")
aborting execution of your function by throwing an error. Instead, you have to know that it can produce anInvalid Date
object and check for that. Otherwise a randomNaN
shows up during execution, which is gonna be extremely fun to try to find the source of.I understand that it’s implemented like that partially for historical reasons, partially because it’s often better to display “NaN” rather than nothing, but it’s still the sort of behavior that puts me in a cold sweat, because I should be memorizing all kinds of Best Practices™ before trying to code JavaScript.