At first, I thought this was a screenshot from Lemmy and thought what the hell. Then I saw that it's Reddit and all my questions got answered. ¯\_(ツ)_/¯
Ephera
That Lemmy guide uses mdBook: https://rust-lang.github.io/mdBook/
It originates from the Rust ecosystem, but it's basically language agnostic.
You basically provide it Markdown files in a certain file structure and then it does the rest. Really easy to use.
Maybe because political left vs. right?
I don't know a thing about cats, but I would've expected there to be more diseases in the city, with all the humans, car exhaust, trash etc..
At first I thought, they're releasing this news now to drown out the Concord news, but 30 year anniversary, maybe they did have this planned a little longer. 🙃
I guess, it depends on what we're referring to as "it". If we're talking about the LLM-based ChatGPT, that's true pretty much by definition. But if we're talking about "AI", which is a word that has been used for everything from calculators to Skynet, then yeah, at some point AI will be AGI.
Well, if humanity doesn't obliterate itself in the coming decades, which isn't looking too good.
Well, apparently that's only 5.8% of trips:
About 47% of the trips replaced a public transit, carpool, walking or cycling trip. An additional 5.8% of trips represented “induced travel,” meaning the person would not have made the trip were an Uber or Lyft unavailable.
I guess, maybe the remaining 47.2% are taxi rides which got replaced by Uber/Lyft?
I tried something like that once. Basically, I was trying to create an API with which sysadmins could script deployments. That involves lots of strings, so I was hoping I could avoid the String
vs. &str
split by making everything &'static str
.
And yeah, the problem is that this only really works within one function. If you need to pass a parameter into a function, that function either accepts a &'static
reference which makes it impossible to call this function with an owned type or non-static reference, or you make it accept any reference, but then everything below that function has normal borrowing semantics again.
I guess, with the former you could Box::leak()
to pass an owned type or non-static reference, with the downside of all your APIs being weird.
Or maybe your prototyping just happens at the top and you're fine with making individual functions accept non-static references. I guess, you'll still have to try it.
Since you're already at the bargaining stage of ~~grief~~ programming, maybe you're aware, but Rc
and Arc
are the closest you can get to a GC-like feel. These do reference counting, so unlike GC, they can't easily deal with cyclic references, but aside from that, same thing.
Unfortunately, they do still have the same problem with passing them as parameters...
Blocking a community is possible from the context menu in the community overview page (tap on the community name):
Blocking an instance (which is a whole server with multiple communities) is possible via the web interface, but I don't think, it's possible in Jernoa yet.
Yeah, vibraphones is where it's at!
Yeah, I don't think that can happen without splitting the whole ecosystem in half. Garbage collection requires a runtime, and tons of the code semantics are also just different between the two, particularly with asynchronous code.
I also imagine that many people wouldn't just leave their particular program in the GC version, but never even bother to learn the ownership/borrowing semantics, even though those largely stop being painful after a few months.
But yeah, I actually don't think it's too bad to have individual parts of the ecosystem using their own memory management strategies.
The two examples that I can think of are ECS for gamedev and signals/reactivity for UI frameworks. Which is what is used in C++ or JavaScript, Kotlin, too. You'd probably still want to use these strategies, even if you've got garbage collection available...
Hmm, I think, you can download one of the .tar.gz files from here: https://github.com/rust-lang/mdBook/releases
Unpack it and then just run the executable that's inside.
And yes, images are absolutely possible.
You can just place the image file in the file structure and then in your Markdown file, you can use this syntax:
I usually create an "images" sub-folder next to the Markdown file, then it's just: