Mastodon Feed: Posts

Mastodon Feed

Gargron ("Eugen Rochko") wrote:

Waiting for a train.

📷 Pentax KX
🎞️ Fuji Superia X-tra 400
🔭 Pentax M 50mm/1.7
👤 Wife
⚗️ Come Through Lab

#BelieveInFilm #FilmPhotography #AnalogPhotography #35mm

Attachments:

Mastodon Feed

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

So I was at the library with the kiddo where some other parents left their 8 and 10 yo children to watch over their 1 to 5 yo siblings[1], and while taking doodle requests from the younger kids[2] I realized that the 4 to 5 yo bracket is a great source of gossip about other families. If that's your kind of thing.

[1] I get it. It's tough being a parent, and we all need breaks.
[2] Kid: "I want a guy." Me: "What kind of guy?" Kid: "A guy that goes like this" [starts posing with flexed arms].

Mastodon Feed

Gargron ("Eugen Rochko") wrote:

Aug 10, 10 sign-ups from #Brazil. Aug 28, 152 sign-ups from Brazil. Today, 4.2k sign-ups from Brazil. Portuguese (Brazil) has already entered the list of top 8 active languages for the last 30 days.

Mastodon Feed

Gargron ("Eugen Rochko") wrote:

Going to be watching the new episode of #BloodOnTheClocktower from #NoRollsBarred ☺️

https://www.youtube.com/watch?v=dRwWet03obM

Mastodon Feed

Reblogged by collinsworth@hachyderm.io ("Josh Collinsworth"):

davidgerard@circumstances.run ("David Gerard") wrote:

Attachments:

Mastodon Feed

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):

lina@vt.social ("Asahi Lina (朝日リナ) // nullptr::live") wrote:

I think people really don't appreciate just how incomplete Linux kernel API docs are, and how Rust solves part of the problem.

I wrote a pile of Rust abstractions for various subsystems. For practically every single one, I had to read the C source code to understand how to use its API.

Simply reading the function signature and associated doc comment (if any) or explicit docs (if you're lucky and they exist) almost never fully tells you how to safely use the API. Do you need to hold a lock? Does a ref counted arg transfer the ref or does it take its own ref?

When a callback is called are any locks held or do you need to acquire your own? What about free callbacks, are they special? What's the intended locking order? Are there special cases where some operations might take locks in some cases but not others?

Is a NULL argument allowed and valid usage, or not? What happens to reference counts in the error case? Is a returned ref counted pointer already incremented, or is it an implied borrow from a reference owned by a passed argument?

Is the return value always a valid pointer? Can it be NULL? Or maybe it's an ERR_PTR? Maybe both? What about pointers returned via indirect arguments, are those cleared to NULL on error or left alone? Is it valid to pass a NULL ** if you don't need that return pointer?

Mastodon Feed

slightlyoff@toot.cafe ("Alex Russell") wrote:

A small contemporary frontend discourse glossary:

"full-stack": junior, not trusted to independently operate any section of the stack

"state management": state propagation, but only for a tiny sliver of the presentation layer, and with no sync or vector clock

"performant": slow, both in isolation and in composition. Also, a word that indicates the speaker is unfamiliar with modern CPU, storage, and networking performance

"scales": requires extra work to use at scale

Mastodon Feed

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

seemed to fit the day:

https://music.apple.com/us/album/hot-rocks-1964-1971/1440764786

Mastodon Feed

Reblogged by isagalaev ("Ivan Sagalaev :flag_wbw:"):

RichardH@mas.to wrote:

Attachments:

Mastodon Feed

Reblogged by kornel ("Kornel"):

lina@vt.social ("Asahi Lina (朝日リナ) // nullptr::live") wrote:

But the end result of all this is that you CAN, in fact, just look a the Rust API and know how to use it correctly for the most part. You never have to worry about reference counts, about NULL pointers, about forgetting to check results, about dropping refs in error cases.

You never have to worry about holding the right locks, about accidentally forgetting to take a ref or dropping it twice. You never have to wonder how error returns are encoded.

Because if you make a mistake with these things, your code won't compile.

Of course you can still misuse APIs, but the worst that will happen is that you'll get an error return, or maybe a deadlock (deadlocks are easy to debug with lockdep and I wrote a really neat Arc<> integration to catch potential drop/decref related locking errors).

Even with APIs that mostly are fairly rigorously documented (OpenFirmware/Device Tree comes to mind), following all the rules in C is often tedious and error prone. Look at some random OF code in a driver and there's a good chance it leaks references.

(This doesn't really matter for most systems since they don't compile kernels with OF_DYNAMIC so ref counts are ignored, so this never gets noticed and fixed.)

But with my OF Rust abstractions? They do ref counting for you. You can just forget about it.

Mastodon Feed

pzmyers@octodon.social ("pzmyers 🦑") wrote:

I might have to include this illustration in my lab courses.

https://freethoughtblogs.com/pharyngula/2024/08/31/why-is-it-a-good-idea-to-have-your-graph-axes-include-0/

Attachments:

Mastodon Feed

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

Trust is a serious issue

Attachments:

Mastodon Feed

lloydmeta ("Lloyd") wrote:

Sad day for nerds...

https://arstechnica.com/gadgets/2024/08/anandtech-mainstay-of-computer-hardware-reviews-closes-after-27-years/

Mastodon Feed

Reblogged by collinsworth@hachyderm.io ("Josh Collinsworth"):

starraven@mastodon.scot ("Starraven") wrote:

"Bees don't waste time telling flies that honey tastes better than crap."

It's a phrase I've seen often in response to science denialism, but it's even more fitting when you realize bees work to benefit their communities while flies just create hordes of diseased offspring to become a problem to the world.

Be a bee, not a fly.

#ScienceDenialism #science #COVID19 #Covid #CovidIsNotOver #antivaxx

Mastodon Feed

pzmyers@octodon.social ("pzmyers 🦑") wrote:

The press continues its silly habit of exaggerating the danger of spiders, even as it's praising restoration efforts.

https://freethoughtblogs.com/pharyngula/2024/08/31/theyre-not-really-that-big/

Attachments:

Mastodon Feed

fribbledom ("muesli") wrote:

Inspired by the replies to one of my recent posts, I decided to hack together a little tool that parses my YouTube watch history.

Shockingly insightful statistics:

Watched a total of 71767 videos on 13082 channels, at a current rate of 35 videos per day.

More than 5% of my watched videos have since disappeared from YouTube!

Here's just a little teaser 🙈

Attachments:

Mastodon Feed

Reblogged by collinsworth@hachyderm.io ("Josh Collinsworth"):

touk@smores.town ("Touk") wrote:

Charli XCX is short for Charles Xavier Charles Xavier

Mastodon Feed

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

dirge

https://music.apple.com/us/album/evolution-and-flashback/1621357715?i=1621358591

Mastodon Feed

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

ahhhhhhhh

https://music.apple.com/us/album/brother/1621357715?i=1621357925

Mastodon Feed

Gargron ("Eugen Rochko") wrote:

I have been asked this, and yes, sign-ups and overall traffic from #Brazil are picking up today, following the #X ban. Bem-vindos ao Mastodon!

Attachments:

Mastodon Feed

pzmyers@octodon.social ("pzmyers 🦑") wrote:

It's me, in 1960!

https://freethoughtblogs.com/pharyngula/2024/08/30/if-you-want-to-know-what-i-looked-like-when-i-was-4/

https://www.youtube.com/watch?v=F7AKvcgFsh4

Mastodon Feed

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Then again, maybe I'm interpreting these messages wrong. Maybe these are modern prayer messages to the gods of shipment and bullshit as a service. Like wards against evil or something. 🤔

Mastodon Feed

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Having just received a package with this message, it occurs to me that writing "Please do not drop" on a package has the same energy as commanding "do not hallucinate" to an LLM.

Mastodon Feed

fromjason ("fromjason.xyz 🖤") wrote:

Being a "joyful warrior" is a public relations tactic, not a vehicle for change

Mastodon Feed

Reblogged by fromjason ("fromjason.xyz 🖤"):

fromjason ("fromjason.xyz 🖤") wrote:

Sometimes you gotta post that one draft that shouldn't see that light of day

#openweb #smallweb

https://fromjason.xyz/p/notebook/raw-dog-the-open-web/

Mastodon Feed

pzmyers@octodon.social ("pzmyers 🦑") wrote:

My grandfather's life story, a tragic morality tale about the dangers of alcohol and tobacco.

https://freethoughtblogs.com/pharyngula/2024/08/30/paul-clarence-westad-1917-1989/

Attachments:

Mastodon Feed

fribbledom ("muesli") wrote:

Oh, what's this? Grouping notifications? I dig it! 😍

Attachments:

Mastodon Feed

Gargron ("Eugen Rochko") wrote:

New #Leprous album, Melodies of Atonement, is out today!

Mastodon Feed

collinsworth@hachyderm.io ("Josh Collinsworth") wrote:

Don't fight with me about Breath of the Wild and/or Tears of the Kingdom, please. They're both great. I've put like 200 hours into both of them combined.

They're both also just Nintendo copying everything every other company had already been doing for ages with open-world games, stuffed with barely coherent plots that nobody would tolerate from any other series.

Mastodon Feed

collinsworth@hachyderm.io ("Josh Collinsworth") wrote:

A lot of game publications have given every major Zelda game in the last 30 years a perfect 10/10 review, even the obviously flawed ones.

Skyward Sword was especially mediocre, and yet, 10/10, cuz Zelda. Both modern open-world Zeldas are indisputably great, but both plagiarize other open-world games, and both have awful plots and voice acting. But 10/10, cuz Zelda.

Anyway...it'll be interesting to see whether the halo effect continues once the series gets its first title starring a woman.