Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S
Posts
1
Comments
57
Joined
2 yr. ago

  • I assume you mean AVIF? Because AV1 is not an image (file) format but a video compression format (that needs to be wrapped in container file formats to be storable).

  • Stapler sein wie:

  • The std::offload project is kinda cool. Hadn't heard about that before.

    It'll be interesting to see where that leads.

  • Die Fahrbahnmarkierungen sehen leider sehr europäisch aus

  • I was under the impression that the compiler already optimizes out a lot of clones where the clone is primarily used to satisfy the borrow checker. Is that not the case?

  • Interesting, GPG has been working just fine for me so far.

    My main issue with it remains that barely anyone else uses GPG.

  • Cryptmaster

    Looks a little grim but is quite funny. There's a demo available to test out.

    I like that there is a vast amount of voice lines available for the game's characters to respond to whatever you typed in. It seems like the devs thought of nearly everything.

  • How much is the fish?

  • Are the common-controls determined per user?

    If yes, that would be awesome.

  • Not as far as I'm aware of. You can kinda fake it with references like you would in C++.

    With all the missing context it would also be possible that the author is trying to track invalid whatevers and the invalid flag is actually wanted state.

  • We are missing a lot of context but strong type systems give you the superpower to make unwanted state unrepresentable:

    Here we can see the class member invalid being used as a flag to express that this method didn't work out as expected. It is very easy for someone else down the line to ignore/forget (/never even knew about it) to check that invalid flag and just use the result regardless, which will likely lead to more failures later on.

    Instead the author should directly return something that indicates invalidness. This could be as simple as returning a boolean or especially if this is a constructor it would be better to throw an error.

    That way the invalid class never even gets instantiated and is therefore impossible to misuse. All validated by the type system.

  • crates.io: Malicious crates faster_log and async_println | Rust Blog

    Jump
  • As long as people are using Rust, it will necessarily attract this kind of action. This won't be the last attack we will see.

    I think the team has handled it quite well.

  • Like you already hinted at batteries are DC systems and can only be charged using DC. Many EVs have at least a small AC to DC converter on board. When you plug it into an AC source the charging speed is limited by the size of that converter.

    DC charging stations bring their own converters which are oftentimes much more powerful and therefore heavier than what your car carries along.

    Whether you use an external 19kW converter or your cars internal converter doesn't make a difference. In both cases the cars charging circuitry will monitor for dangerous situations such as overheating and throttle the charger down if need be.

    The important question is how large your cars converter actually is. Sure the L2 charger provides 19kW AC but can your car's converter actually use all of that?

    If it can only do 10-15-ish kW then it'll charge slower and therefore won't tax the battery as much as a DC charger with 19kW would.

    I don't know what car this is and how PHEVs play into this but existing BEVs have been charging with much higher speeds for more than 100,000 miles and generally don't end up with broken batteries.

    Depends a lot on the make and model of course, as I'm sure there are some horrible examples out there. But the public fast chargers wouldn't be under such demand if it was that damaging to the cars.

  • The post text doesn't seem to get displayed on some clients (Voyager) so I'll attach it here as well:

    asciinema (aka asciinema CLI or asciinema recorder) is a command-line tool for recording and live streaming terminal sessions.

    This is a complete rewrite of asciinema in Rust, upgrading the recording file format, introducing terminal live streaming, and bringing numerous improvements across the board.

  • Rust @programming.dev

    The release of asciinema CLI 3.0!

    blog.asciinema.org /post/three-point-o/
  • Not just on the web. I've previously used it to embed a short clip in a presentation.

    The nice thing is that it doesn't do a massive screencap but only captures the text. This way the replay will be freshly rendered at native resolution.

  • Stuffing batteries into the cardan tunnel was a stupid idea. If you want your EV to have any range you need to design the chassis from the ground up for that purpose. You know just like they did for the Golf with an ICE engine.

    I'm not against a refreshed EV Golf but that earlier concept wasn't the best implementation.

  • There are even little interactive tools for it like: cargo-wizard

  • Good move. Especially for incremental builds linking tends to take up quite a large percentage of the compile time.

    I've mostly switched to mold for that reason but having a fast default linker is nice.