153·
5 months agoBuy a keyboard and monitor
- 0 Posts
- 37 Comments
Joined 1 year ago
Cake day: June 26th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
43·5 months agoNGL, this looks kinda terrible
And the only thing even worse than SCRUM is literally every other option
14·7 months ago“Discord said users will be able to turn off the ads in their settings.”
Remote Desktop
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.
If you’re using assembly, then you’ve already given up on the easy ways.
1·1 year agoVivaldi will never have it
And as soon as they have any competitors we might consider it
1·1 year agoThis is the entire point of PowerShell
9·1 year agoSemantic versioning. Moving from v2.3 to v2.4 shouldn’t require major changes, but moving to v3.0 can.
Or just get the old booster now and then by the time they release the update you’ll be ready for your next booster anyway…
It’s the API that ALLOWED the misuse in the first place, so the developers are the ones to hold accountable.
No need, GUIs are better for most tasks.
I’ve heard that enabling CloudFlare DDoS protection on Lemmy breaks federation due to the amount of ActivityPub traffic.
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
You need to get a cert from Let’s Encrypt (using certbot), then look up directions for configuring nginx to use the cert files generated by certbot.
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).