Skip Navigation

Posts
407
Comments
271
Joined
3 yr. ago

  • Men någon måste stå för kostnaden när flaskan måste bytas. Nu kostar en flaska inte så mycket och håller länge, så avskrivningskostnaden per år blir rätt liten. Således kan de som tillhandahåller gasen lägga det på gas priset så att du som kund inte märker det. Ett Tesla batteri kostar ca 100000, det blir svårt att dölja i laddningspriset, så då blir det mycket billigare att bara ladda hemma. Men för att detta ska fungera måste någon stå för kostnaden att byta batteri när det är slut. Så, varför skulle laddstationer ta den risken, när de inte är garanterade kostnads täckning. Och om jag ska stå för kostnaden vill jag inte riskera byta in ett fräsht batteri och få Svarte Petter.

  • Tesla hade väl försök med batteribyte, men kunderna ville inte ha det. Vilket är förståeligt, då batteriet kostar en ansenlig summa, så om man på något sätt är ansvarig för batteriet vill man inte riskera att man byter in sitt nya fina batteri och får ett taskigt batteri tillbaka som riskerar sluta fungera på så sätt att man måste stå för det. Så för att kunder ska vilja detta, måste stationen stå för alla risker med batteriet. Tveksamt om de vill det.

  • Well, if the only thing you need from reflection is the name of a type, so then yes. But I wouldn't really call this reflection since it is very limited.

  • Jag antar att Stureplan blir en visitationszon , då det nog är rätt mycket droger där en lördagskväll.

  • It starts by presenting it self as an Comedy AI, that implies more than deep fake.

  • Librsvg did the rewrite incrementally, so you can choose to only use rust for new code in an existing codebase.

  • I say that you should find some interesting project, possibly something related to some desktop environment like Gnome, KDE, sway, cosmic and so on. There are multiple fun/interesting projects around them. Then pick a small and manageable task, use that to learn the language that project uses.

    I find Cosmic to be a very interesting desktop project, and they use Rust if that would be of interest.

  • This was in 1985, on a ABC80, a Swedish computer with a 3 MHz CPU. So, in theory it would be much faster, but I assume there were many performance losses (slow basic interpretor and thing like that) so that for loop got close enough to a second for us to use.

    https://en.m.wikipedia.org/wiki/ABC_80

  • On my first programming lesson, we were taught that 1 second sleep was for i = 1 to 1000 😀, computers was not that fast back then...

  • If you avoid Nvidia, it have been ready for many years. And to be honset, not sure X11 was really stable with Nvidia either. My main issue with Wayland, is that X doesn't have multi dpi support... and for that I really cannot blame Wayland. Also, Skype doesn't have screensharing, well, they actually had for a while, but then removed it... still, hard to blame on Wayland.

    But as a general rule, if you have Nvidia, then you are not allowed to complain about anything... that was your choice, and with Nvidia under Linux, all bets are off. I thought that was clear a long time a go, especially after Linus not so subtle outburst.

  • Also, it was easier to support X11, since there is no security. You wanted to read other applications key events, no problem. Want to read the screen, without without anyone knowing? No, problem, just read it. With Wayland you must use APIs for stuff, and you are not allowed to do everything.

  • Are they really? Didn't you press a button that said "Buy"? Just because they want things to be something else, doesn't mean that the meaning of the words changed.

  • Well, I have avoided Nvidia for 20 years due to driver issues on Linux, so I would be surprised if you had fixed them all :) But, it sound really promising, looking forward to try it out!

  • I'm really looking forward to the alpha release. I hope someone package it for Fedora also, so I can test it without to much hassle... if not, I guess it will be PopOS in a VM. @mmstick@lemmy.world what is the general state of it as of today? Are the developers at S76 able to use it as their daily driver (By that I mean, being able to use it since they can over look bugs and such, since they are the developers. Obviously a different bar than end users), or is that expected after the alpha?

  • The borrow checker handles more than just freeing allocated memory, it will also prevent data races and invalid concurrent access aso. I personally don't have any issues with using garbage collected languages, but the fearless concurrency is nothing I'm willing to give up.

  • They explain a bit more about what that means here: https://kagifeedback.org/d/2808-reconsider-your-partnership-with-brave/75

    TL;DR They use multiple sources for search results besides their own indexer, the most obvious one is Google. To lessen dependence on one single search provider they have been adding other sources, one of them is now Brave. That is the whole thing.

    On Dec 26, Kagi started including search results from Brave search index, after we previously added Mojeek and Yandex earlier in the year. Brave has a public search api and we currently implemented it for about 10% of queries as a first test (same as any other API we use, there is no mutual development or anything of the sorts). This was announced in our Dec 28 public changelog. Approximately a week later on Jan 5 after several posts on social media about ‘Brave partnership’ the situation escalated.]

    So, if you do not like to use Google in the first place, I don't really understand why lessening the dependence on google would be a bad thing?

  • You have understood that there doesn't exist any country that meets you utopian communist view, yet you have not stopped to think about why that is.

  • Ahhh... the communist countries are where all the unicorn lives... got it!

  • Well the argument "People in capitalist economies do not contribute out of free will" is something you just pull out of your ass, to define your side as the ones that will "contribute out of free will" (hence, the good side). This is the same logic you see in religious cults, where they define that themselves are moral and right, and the outside immoral. It really doesn't deserve any serous response since there is no response that will be able to penetrate that kind of brainwash.

  • Rust @programming.dev

    Rust Toolchain Upgrade Submitted For Linux 6.8 - Phoronix

    www.phoronix.com /news/Rust-Upgrade-For-Linux-6.8
  • Rust @programming.dev

    This Week in Rust 528 · This Week in Rust

    this-week-in-rust.org /blog/2024/01/03/this-week-in-rust-528/
  • Rust @programming.dev

    Securing the Web: Rustls on track to outperform OpenSSL - Prossimo

    www.memorysafety.org /blog/rustls-performance/
  • Rust @programming.dev

    What I'd like to see for Async Rust in 2024 🎄 · baby steps

    smallcultfollowing.com /babysteps/blog/2024/01/03/async-rust-2024/
  • Rust @programming.dev

    Index out of bounds? Not always! - A Rusty Surprise | Serhii Potapov (greyblake)

    www.greyblake.com /blog/index-out-of-bounds-not-always-a-rust-surprise/
  • Rust @programming.dev

    This Development-cycle in Cargo: 1.76 | Inside Rust Blog

    blog.rust-lang.org /inside-rust/2024/01/03/this-development-cycle-in-cargo-1-76.html
  • Rust @programming.dev

    Arc vs String, is Arc really faster?

    blocklisted.github.io /blog/arc_str_vs_string_is_it_really_faster/
  • Neovim @sopuli.xyz

    Release Nvim 0.9.5

    github.com /neovim/neovim/releases/tag/v0.9.5
  • Rust @programming.dev

    Rust9x update: Rust 1.76.0-beta

    seri.tools /blog/rust9x-1-76/
  • Rust @programming.dev

    Announcing Rust 1.75.0

    blog.rust-lang.org /2023/12/28/Rust-1.75.0.html
  • Rust @programming.dev

    Rust Analyzer Changelog #213

    rust-analyzer.github.io /thisweek/2023/12/25/changelog-213.html
  • Rust @programming.dev

    Rustc Trait System Refactor Initiative Update: A call for testing

    blog.rust-lang.org /inside-rust/2023/12/22/trait-system-refactor-initiative.html
  • Rust @programming.dev

    How I Have Fun With Rust - Matheus Richard

    thoughtbot.com /blog/how-i-have-fun-with-rust
  • Rust @programming.dev

    Improving Supply Chain Security for Rust Through Artifact Signing

    foundation.rust-lang.org /news/2023-12-21-improving-supply-chain-security/
  • Rust @programming.dev

    Continuous Memory Profiling for Rust

    www.polarsignals.com /blog/posts/2023/12/20/rust-memory-profiling
  • Rust @programming.dev

    This Week in Rust 526 · This Week in Rust

    this-week-in-rust.org /blog/2023/12/20/this-week-in-rust-526/
  • Rust @programming.dev

    The Most Common Rust Compiler Errors as Encountered in RustRover: Part 2

    blog.jetbrains.com /rust/2023/12/20/the-most-common-rust-compiler-errors-as-encountered-in-rustrover-part-2/
  • Rust @programming.dev

    Rust is growing

    flawless.dev /essays/rust-is-growing/
  • Rust @programming.dev

    Rust Analyzer Changelog #212

    rust-analyzer.github.io /thisweek/2023/12/18/changelog-212.html
  • Rust @programming.dev

    The First Rust-Written Network PHY Driver Set To Land In Linux 6.8 - Phoronix

    www.phoronix.com /news/Linux-6.8-Rust-PHY-Driver