• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle




  • Our current ML Neural Networks work (simplified) like this: A neuron emits a number and the next neuron calculates a new number to emit based on all the values given to it by other neurons as inputs. Our brain can’t fire numbers in this way. So there’s a fundamental difference. Bridging this difference to create NNs that are more similar to our brains is the basis of the study of Spiking Neural Networks. Their performance so far isn’t great, but it’s an interesting topic of research.


  • I dont see why, tbh. This feature is only needed by users of tiling WMs with (super)ultrawide monitors. A niche in a niche. Normal floating WMs work fine with ultrawide monitors, you are constantly resizing and moving windows around anyway and simple snapping takes care of the rest. Windows 11 even lets you snap exactly into the setup described above.

    Also, there are good plugins for supporting tiling for GNOME (I know its in PopOS, not sure how to get it into the normal one) , KDE, and even Windows


  • One thing that has been stopping me from switching to Wayland is that I have a 32:9 screen and usually virtually divide into a 16:9 in the middle and then an 8:9 on each side. This works well enough on Xorg.

    I would love to see this implemented in Hyprland and I opened an issue for it a while back. The maintainer says that the workload seems too large and he is uninterested. I’ve racked up quite a few upvotes though and it seems like quite a lot of people would be interested in this.

    I’ve glanced over the code and I think it shouldn’t be extremely difficult to add a layer of indirection between workspaces and monitors as an initial PoC. Dont get me wrong, this will still take more than a week to get running which is why I sadly havent found the time to do this myself.

    If you could maybe look into it there may be possibilities to split up the work a bit. I dream of a world where you can dynamically add and remove virtual outputs and it’s all animated - very long way to go until then.




  • The issues here are largely with the EU which stops it from being sold in stores. For now, possession is legalised and you can have all previous arrests made because you were carrying up to 25g permanently removed from your record. It also legal to grow at home.

    In this sense, it is legal for personal use but not for commercial use. To get access to weed, they will be rolling out “cannabis social clubs” in summer in which you need to be a member to be allowed to buy weed. These clubs are not allowed to make a profit. There is a plan to later do some tests with commercial usage but its not clear where that is on the roadmap.

    It will be interesting to see if this will have any effects on the EU. I can imagine if more countries want to support the legalization that some hurdles can be removed there.


  • aDogCalledSpot@lemmy.ziptoProgrammer Humor@lemmy.mlcodeStyle
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    I think Rust actually is actually among the best in this regard for the simple reason that there is consistency given by the compiler. A simple cargo fmt and cargo build will fix or warn you about everything. I can read into Rust codebases so quickly. C++ was always really exhausting because most of the time you were just getting used to the code style.


  • I feel like there are too many exceptions to this rule. Maybe dont get the cheapest but you dont need to spend a lot to have a very good:

    • Cast iron pan
    • Carbon steel pan
    • Enameled cast iron pot (seriously, look it up, I see people saying how much they love their Le Creuset all the time but I got one from KitchenAid of all brands at 50 euros in my local supermarket)
    • Baking tray
    • Cooling rack
    • Baking bowls
    • Spatula of any kind
    • Peeler
    • Electric mixer
    • Kitchen scale

    I could go on but I believe Ive made my point.