Wonder why they didn’t just keep everything on one site and only show stuff marked safe unless you toggle a switch? Maintaining two whole different sites that sync seems like more work for them
Wonder why they didn’t just keep everything on one site and only show stuff marked safe unless you toggle a switch? Maintaining two whole different sites that sync seems like more work for them
You’re probably getting downvotes because of the terrible title, but the article is interesting, and talks about putting this into practice:
https://civitai.com/articles/6792/flux-captioning-differences-training-diary
Is there a good tl;dr on what is new and interesting about flux? Does it use a different architecture, or is it just bigger?
What parent is likely referencing
TBH I wonder if the current Microsoft is capable of executing that here. I don’t believe in a “changed” MS, but Linux is eating the world, and MS doesn’t really care about Windows much anymore. Azure happily runs Linux VMs
The collect
’s in the middle aren’t necessary, neither is splitting by ": "
. Here’s a simpler version
fn main() {
let text = "seeds: 79 14 55 13\nwhatever";
let seeds: Vec<_> = text
.lines()
.next()
.unwrap()
.split_whitespace()
.skip(1)
.map(|x| x.parse::<u32>().unwrap())
.collect();
println!("seeds: {:?}", seeds);
}
It is simpler to bang out a [int(num) for num in text.splitlines()[0].split(' ')[1:]]
in Python, but that just shows the happy path with no error handling, and does a bunch of allocations that the Rust version doesn’t. You can also get slightly fancier in the Rust version by collecting into a Result
for more succinct error handling if you’d like.
EDIT: Here’s also a version using anyhow
for error handling, and the aforementioned Result
collecting:
use anyhow::{anyhow, Result};
fn main() -> Result<()> {
let text = "seeds: 79 14 55 13\nwhatever";
let seeds: Vec<u32> = text
.lines()
.next()
.ok_or(anyhow!("No first line!"))?
.split_whitespace()
.skip(1)
.map(str::parse)
.collect::<Result<_, _>>()?;
println!("seeds: {:?}", seeds);
Ok(())
}
Seconding as better for RSI. Plus they work anywhere, you don’t need specific surfaces for them
VPNs are great for avoiding the nastygrams that your ISP forwards to you from media companies. They get sent to some company that doesn’t care about US laws instead, and probably laughed at before being deleted
Everything’s visible for HTTP, and in fact some ISPs inject their own ads into HTTP content. HTTPS is harder for malicious actors, but your ISP can tell when you’re visiting pornhub.com, and will happily provide that to the government. With encrypted SNI it’s somewhat harder, but if you’re visiting an IP address of 1.2.3.4, and that IP address is solely used by pornhub.com, it’s not hard to guess what you’re up to.
Has some Paprika style vibes
I was thinking Zalgo, but that works too
There’s a whole series of these. Not sure where the trail ended, but here’s one of the iterations of this site:
Get pissed at NVIDIA. They’re the problem.
You probably wouldn’t be committing this, unless you’re backing up a heavily WIP branch. The issue is that if you’re developing locally and need to make a temporary change, you might comment something out, which then requires commenting another now-unused variable, which then requires commenting out yet another variable, and so on. Go isn’t helping you here, it’s wasting your time for no good reason. Just emit a warning and allow CI to be configured to reject warnings.
This is the best explanation I’ve ever seen of monads: https://www.adit.io/posts/2013-04-17-functors,_applicatives,_and_monads_in_pictures.html
For some reason, you’ll find a lot of really bad explanations of monads, like “programmable semi-colons”. Ignore those, and check out the link.
It’s not a half-arsed copy, it’s borrowing a limited subset of HKT for a language with very different goals. Haskell can afford a lot of luxuries that Rust can’t.
That’s 👏 what 👏 CI 👏 is 👏 for
Warn in dev, enforce stuff like this in CI and block PRs that don’t pass. Go is just being silly here, which is not surprising given that Rob Pike said
Syntax highlighting is juvenile. When I was a child, I was taught arithmetic using colored rods. I grew up and today I use monochromatic numerals.
The Go developers need to get over themselves.
That’s a big-ass sword. 7 or 8 feet tall?
Thanks! That’s the sort of thing I’m looking for
What is !steamdeck@lemmy.world doing over with the red dots 🤔