al4s

joined 4 months ago
[–] al4s 2 points 4 days ago

Bluesky also uses a federated protocol, AFAIK. But the feeds are generally better

[–] al4s 6 points 4 weeks ago

Irgendwie klingt der Artikel sehr beeindruckt, dass 24h nach dem Börsengang die U-Bahnen immer noch pünktlich fahren. Darauf zu basieren, dass man das in Deutschland ja auch so machen sollte finde ich abenteuerlich.

[–] al4s 10 points 1 month ago

ChatGPT is not a reliable source of information, I thought that was clear to everybody by now

[–] al4s 8 points 1 month ago

The processor architecture does not influence RAM usage. (At least not if both architectures are 64-bit)

[–] al4s 2 points 1 month ago (3 children)

I mean you'd still expect that critical security fixes would land in testing, no?

[–] al4s 2 points 1 month ago

Because you don't control third party libraries

[–] al4s 2 points 1 month ago (2 children)

A scope groups the initialization visually together, while adding the let app = app; feels like it just adds clutter - I'd probably just leave it mut in that case.

[–] al4s 2 points 1 month ago (2 children)

You can have setters that set private fields, there are also sometimes structs with mixed private and public fields

[–] al4s 6 points 1 month ago (4 children)

Yeah if you have the second option, use it, but if the struct has private fields it won't work.

[–] al4s 13 points 1 month ago (10 children)

If you're ever forced to do something the second way, you can also wrap it in braces, that way you end up with an immutable value again:

let app = {
  let mut app = ...
  ...
  app
};
[–] al4s 22 points 1 month ago

Definitely the second one.

  1. It avoids Mut
  2. It makes clear that the initialization is over at the end of of the statement. The first option invites people to change some more properties hundreds of lines down where you won't see them.
[–] al4s 6 points 2 months ago (6 children)
view more: next ›