Buttons

joined 1 year ago
[–] Buttons@programming.dev 8 points 1 week ago

You don't have to flip a trick coin to call the outcome.

[–] Buttons@programming.dev 5 points 1 week ago

Heros put themselves in front of bullets to protect others.

Trump puts others in front of bullets to protect himself.

[–] Buttons@programming.dev 20 points 1 week ago

Jesse Waters knows a lot about affairs.

He cheated on his wife, they divorced, he married the woman he was cheating with.

[–] Buttons@programming.dev 3 points 1 week ago* (last edited 1 week ago)

Deno looks interesting.

But Bun choosing Zig makes me think their priorities are not my priorities. As of now, you choose Zig (a not-yet-stable language) because you want to learn Zig and make a neat side-project. Those are not my priorities. Zig offers no unique advantages other than neat new syntax.

Deno chose Rust, which, like Zig, is new, but Rust has reached 1.0 and offers a unique advantage with its safety features. I'm not saying anything about the greatness of Rust here, only that Rust does offer unique advantages, and Rust could be chosen because of general priorities.

Bun chose Zig and then worked backwards and formed their priorities around Zig. Deno formed their priorities and their priorities lead them to Rust.

That's how I feel anyway.

[–] Buttons@programming.dev 19 points 1 week ago (7 children)

Were just waiting on WASM to be able to access the DOM APIs directly, and then all languages will be first class citizens on the web, and then RIP JavaScript.

[–] Buttons@programming.dev 5 points 2 weeks ago (1 children)

Nothing wrong with changing the constitution, as long as people do what's required.

[–] Buttons@programming.dev 15 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

The journalists and the culture at the newspaper wanted to endorse Harris, but the billionaire owner swooped in and overrode all of that. This is obvious.

I realized there's another layer to how messed up this is though. A newspaper changed it's journalistic practices to benefit an aerospace company (Blue Origin). Why is a newspaper connected to an aerospace company?

More and more companies are being owned by fewer and fewer people. The American dream is dead, the free market is a myth at this point.

[–] Buttons@programming.dev 1 points 2 weeks ago

Throttling everyone equally during times of congestion is also fair in its own way. I'd be okay with that.

[–] Buttons@programming.dev 1 points 2 weeks ago* (last edited 2 weeks ago)

I like this term, "billionaire media", because right-wing media likes to use "mainstream media" as a slur to dismiss any other media source that disagrees with them. It's a term that shuts down thinking and gets people to automatically dismiss any claim from "mainstream media".

"Billionaire media" doesn't really work this way, because if Fox News starts criticizing "billionaire media", eventually some viewers are going to wake up and realize, "wait, isn't Fox News owned by a billionaire too?"

[–] Buttons@programming.dev 2 points 2 weeks ago (1 children)

People, especially Republicans, love to talk about the "mainstream media". That term needs to die.

There is only "billionaire media" and "independent media".

You're billionaire media if your owned or funded by a billionaire; I don't care if you're only on YouTube, if you're getting hundreds of thousands of dollars from sponsors, you're part of the billionaire media.

If you're funded by a bunch of small donations or have no funding at all, then you are independent media.

Today my trust for billionaire media sank even lower.

[–] Buttons@programming.dev 4 points 3 weeks ago (3 children)

When limiting is required, because many people are using the same network, limiting those who have already used the most seems fair.

[–] Buttons@programming.dev 3 points 3 weeks ago* (last edited 3 weeks ago)

Your comment might cause me to do something. You're responsible. I don't care what the legal definitions say.

If we don't care about legal definitions, then how do we know you didn't cause all this?

 

Git repos have lots of write protected files in the .git directory, sometimes hundreds, and the default rm my_project_managed_by_git will prompt before deleting each write protected file. So, to actually delete my project I have to do rm -rf my_project_managed_by_git.

Using rm -rf scares me. Is there a reasonable way to delete git repos without it?

 

My first experience with Lemmy was thinking that the UI was beautiful, and lemmy.ml (the first instance I looked at) was asking people not to join because they already had 1500 users and were struggling to scale.

1500 users just doesn't seem like much, it seems like the type of load you could handle with a Raspberry Pi in a dusty corner.

Are the Lemmy servers struggling to scale because of the federation process / protocols?

Maybe I underestimate how much compute goes into hosting user generated content? Users generate very little text, but uploading pictures takes more space. Users are generating millions of bytes of content and it's overloading computers that can handle billions of bytes with ease, what happened? Am I missing something here?

Or maybe the code is just inefficient?

Which brings me to the title's question: Does Lemmy benefit from using Rust? None of the problems I can imagine are related to code execution speed.

If the federation process and protocols are inefficient, then everything is being built on sand. Popular protocols are hard to change. How often does the HTTP protocol change? Never. The language used for the code doesn't matter in this case.

If the code is just inefficient, well, inefficient Rust is probably slower than efficient Python or JavaScript. Could the complexity of Rust have pushed the devs towards a simpler but less efficient solution that ends up being slower than garbage collected languages? I'm sure this has happened before, but I don't know anything about the Lemmy code.

Or, again, maybe I'm just underestimating the amount of compute required to support 1500 users sharing a little bit of text and a few images?

view more: next ›