Parts of “Rift of the Necrodancer”
Parts of “Rift of the Necrodancer”
And the only thing even worse than SCRUM is literally every other option
“Discord said users will be able to turn off the ads in their settings.”
If they ask the SAME question and you score still goes DOWN I’m gonna go ahead and call that “a bad sign”.
What this shows is how terrible raw JS is, when all of this crap is required to fix all of the edge cases and make things actually work the way it’s supposed to.
And as soon as they have any competitors we might consider it
This is the entire point of PowerShell
These are not “mistakes”, these are willfully evil acts.
I’m just going to quote another comment here:
Billet Labs sent their best prototype (as in, the only one they had) to LMG for review. Linus proceeded to strap it to a video card where it didn’t fit, so bad that there was a 1mm gap (which might as well be a million miles when you’re talking about cooling). Of course the performance sucked due to it being strapped to a card it wasn’t designed to fit, linus trashed the block and the company. And here’s the part that just fucks me off. Billet Labs SENT THEM THE CORRECT CARD WITH THE BLOCK! There is literally no valid excuse for putting it on the wrong card, Billet Labs sent them the correct one!!!
Combine that with the image in the OP, and there’s just no excuse. These are not the actions of someone that “intends no malice”. This is not an “accident”. This is not a “learning opportunity”. This is not a “mistake”. This is a person doing everything in their power to selfishly extract every dime they can from both their viewers and this startup.
They intentionally lied to the viewers because trashing a product gets more views. They intentionally lied to the startup because they got more money from selling the prototype.
They do not deserve any sympathy.
Works for me
The only way to change someone’s core values is to show them the error of their ways WITHIN their own current value system.
If you can manage to find some purchase there you might have a chance, but it’s more likely that you will not find it.
The Alignment Problem by Brian Christian should be required reading for this community
I don’t think that last part is entirely accurate. The reason the weak gravity causes tides is actually because it’s acting over the entire ocean all at once.
It turns out that the ocean is a bit heavy… when you add up the entire mass of all of the water, this imparts quite a substantial bit of potential energy. This can be seen as a “bulge” outward in the moon’s direction, making the planet look a little “squished”.
If the planet were perfectly smooth, this probably would be fairly stable as the bulge wrapped around the planet… however, because we have continents and the sea floor, this movement of water crashes into the land and causes ripple effects with a huge amount of kinetic energy.
I don’t think it would take more that a few years for this process to ramp up to our current level of tides, if there were some way of doing such a ramp up in a controlled way.
You could try Morning Brew
I only use the Subscriptions feed, and use an extension that blocks recommendations and shorts.
Additionally, before watching any video I’ll check the channel page to see if YouTube is hiding any of that person’s videos from me (which they do even on the Subscriptions feed sometimes).
Fuck the algorithm.
This is what Temtem and Nexomon are for.
weakly typed languages
Well, looks like we found the problem right there
These languages only exist because JS is so dumb in the first place
How is this different from just searching for posts on the original “seed instance”? Presumably you’re crawling through everything on all of the instances that it’s aware of, as opposed to the Lemmy built-in search which would only search communities that have a subscriber?
Transferring is theoretically technically possible (Mastodon does it), but Lemmy hasn’t implemented the option yet. There’s an issue for it on their GitHub.
If you’re branching logic due to the existence or non-existence of a field rather than the value of a field (or treating undefined different from null), I’m going to say you’re the one doing something wrong, not the Java dev.
These two things SHOULD be treated the same by anybody in most cases, with the possible exception of rejecting the later due to schema mismatch (i.e. when a “name” field should never be defined, regardless of the value).