[–] 4 points 5 months ago

I'm worried about this creating a bunch of confusion in the future, but hopefully at some point they mark the old ranges as deprecated.

Ranges directly being iterators confused me so much at first because no other standard iterable types really work that way, then combined with them being !Copy they just felt wrong. The new ranges look so much easier to use and understand.

  • source
  • parent
  • context
  • [–] 3 points 5 months ago

    I'd venture a guess that 100% of people don't need to worry. Based on the complexity and requirements to execute this attack, I'd almost argue it's just a bug report framed as a vulnerability.

    Maybe it's possible to exploit this somewhere in the wild, but it requires pulling from a custom registry that the attacker controls and voluntarily authenticating to it, from what I can tell anyway.

  • source
  • parent
  • context
  • [–] 3 points 5 months ago (1 child)

    The severity of the vulnerability is low, due to the extremely niche requirements needed to achieve the attack.

    Mitigations

    Rust 1.96, to be released on May 28th, 2026

    Ok, so it'll get fixed soon enough and 99% of people don't need to worry 👍

  • source
  • [–] 5 points 5 months ago* (last edited 5 months ago)

    I've never done something similar in Wayland but judging by how Waybar is setting up it's window I guess it should be doable with backend-winit-wayland
    https://docs.rs/winit/latest/winit/#building-windows

    EDIT: actually, you might be a bit too early for using winit for that. But from the surrounding discussions it seems that even so, that should still be doable by interacting with wlr-layer-shell directly

    EDIT2: hold on, I actually have done something similar in Wayland. Just in C++ and GTK. So if instead of using slint you could use GTK4, I guess https://github.com/wmww/gtk4-layer-shell would be the way to get it working

  • source
  • [–] 1 point 6 months ago

    I already have mine written quite a while ago. Why not obsidian? AsciiDoc and few other things Obs will miss. Works with SQLite and PostgreSQL. For pure native UI (not WebUI) miss only AsciiDoc grammar I’m working on.

    For you… sql knowledge requirement depends on your likings: you can build very small or unoptimised app and be fine, you can make very nice, and complex one and have very complex SQL queries.

    I discourage to use MySQL (and clones) due some… peculiarities.

  • source
  • [–] 1 point 6 months ago

    The usual handling in Rust afterwards is in most cases log one error or return to upstream “there was an error”. In some rare cases all errors returned as a single case.

    Both of these first are bad for i18n and finding what’s really happened in the middle.

  • source
  • parent
  • context
  • [–] 2 points 6 months ago

    The argument is, fuck Nvidia's monopoly on GPU compute. AMD keeps quietly funding projects to simply translate CUDA, then backing off when that funding is discovered. That's how scared they are of a court battle. And that was before the AI bubble's infinite money glitch.

  • source
  • parent
  • context
  • [–] 1 point 6 months ago* (1 child)

    is it illegal to write abstraction APIs on top of CUDA? I have heard this argument for half of this decade and i think something that abstracts the CUDA stuff into a thin HAL that can also call other GPU Progamming interfaces would avoid vendor lock-in.

    although, I guess the main challenge is the ever-changing surface of the CUDA api?

    Edit: Ok so if the argument is we should be able to use NVIDIA GPUs without CUDA that any amount of abstraction is a moot point.

  • source
  • parent
  • context
  • [–] 3 points 6 months ago

    lol, I know that sprite pack in the thumbnail from other tutorials 🤣

    It's a great one to start with. Helps avoid that, "It looks shit" demotivation when learning.

  • source
  • [–] 1 point 6 months ago

    Plausible? Absolutely. The questions are what and why?

    For notes, it seems like most people have settled on one of three things: org-mode, markdown, or free form plain text. There are some closed source tools that use a proprietary format, but fuck them.

    So then the question becomes what does the backend do? Provide a way to query notes for links, topics, and todos? Keep a versioning system? Synchonization? Something else? Answer those questions and you have a project.

    For references, take a look at nb, Joplin, Logseq, org-mode, anytype.

  • source
  • [–] 1 point 6 months ago

    Depending on what you do, it will probably only be a few lines of rust. Most of the complexity would be in the DB setup and SQL queries. Since you'll probably use an HTTP server crate that will handle all of that for you.

    So, yes, it should be possible.

    Even if you don't intend to make it a UI project. You should still do a shitty UI. Otherwise you will spend more time testing it than actually developing it.

  • source
  • [–] 3 points 6 months ago

    Title is a little bit misleading, but it's still cool to see that Rust is able to run on such exotic hardware. The price of the device is mostly going to consist of its materials and manufacturing costs, though (if it went to mass-production, which I doubt will happen).

  • source
  • [–] [S] 1 point 6 months ago

    Don't really care if anyone would use it at the moment. My main goal right now is to improve my rust skills. And I guess there are limitations to how much ui you can change in obsidian.

    Also there are other contexts where a note taking like function would be needed. For example I was actually trying to make a note taking app for cosmic desktop which I can access from the Taskbar

  • source
  • parent
  • context
  • [–] 4 points 6 months ago* (last edited 6 months ago) (1 child)

    are you asking if someone would use it? probably not. sounds like a lot of work when someone can just use obsidian with plugins to get the ui they wanted

  • source
  • view more: ‹ prev next ›