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/)E

Err(()).unwrap()

@ rtxn @lemmy.world

Posts
9
Comments
472
Joined
3 yr. ago

Partisanship is a cancer. Inaction is a choice.

Singular they. Or whatever you like, I won't take offence.Proud member of the Banned By Tesseract Club.

  • I checked ip neighbour (it also shows the ARP table, so I assume they're identical), and it showed REACHABLE and STALE for addresses I could ping, but FAILED for the remote VM's address. I will check arp -a when I get the chance, though.

  • I'll give it a try tomorrow, thanks.

    Although I'd still prefer to know why the VMs won't talk over simple Ethernet.

  • Considering how many websites were temporarily obliterated by the left-pad fiasco, being an npmjs maintainer might be an even higher power-to-effort ratio (by virtue of a near-zero denominator) than being a billionaire CEO.

  • It gets fast-paced and exciting when the boss has An Idea on a Friday afternoon that must be completed before the end of the week.

  • I'd take a confessional booth over an open office floor.

  • Realistically, is that a factor for a Microsoft-sized company, though? I'd be shocked if they only had a single layer of redundancy. Whatever they store is probably replicated between high-availability hosts and datacenters several times, to the point where losing an entire RAID array (or whatever media redundancy scheme they use) is just a small inconvenience.

  • This is not meant for human beings. A creature that needs over 140 TB of storage in a single device can definitely afford to run them in some distributed redundancy scheme with hot swaps and just shred failed units. We know they're not worried about being wasteful.

  • I've had good experiences with Rustdesk. The client is open-source and the no-cost server components (ID and Relay servers) are self-hostable. The remote server works on X11 and Windows. I use this script to run XFCE+Rustdesk in a headless session:

     bash
        
    export SERVERNUM=69
    export SCREEN_SIZE='-screen 0 2560x1440x24'
    export DISPLAY=":${SERVERNUM}"
    export XDG_SESSION_TYPE=x11
    
    xvfb-run --server-num="${SERVERNUM}" --server-args "${SCREEN_SIZE}" startxfce4 & disown
    sleep 1
    flatpak run com.rustdesk.RustDesk & disown
    
      

    Sunshine + Moonlight is also a good choice. I have Sunshine installed on a box at home and use Tailscale to connect to it from the Moonlight client. At 1440p 60 FPS it has no visible compression artifacts and responsive enough for gaming.

  • The most useful is probably cat /proc/meminfo. The first couple of lines tell you everything you need to know.

    • MemTotal is the total useful memory.
    • MemFree is how much memory is not used by anything.
    • Cached is memory used by various caches, e.g. ZFS. This memory can be reallocated.
    • MemAvailable is how much memory can be allocated, i.e. MemFree + Cached.
  • "It's just one goto, what's the worst that could happen?"

  • Exactly which flavours of Markdown are targeted/required by this specification?

  • let you build faster like Python

    I have to write so much boilerplate code to make sure my objects are of the correct type and have the required attributes! Every time I write an extension for Blender that uses context access, I have to make sure that the context is correct, that the context has the proper accessor attributes (which may not be present in some contexts), that the active datablock is not None, that the active datablock's data type (with respect to Blender, not Python) is correct, that the active datablock's data is not None... either all that or let the exception fall through the stack and catch it at the last moment with a bare except and a generic error message.

    I used to think that static typing was an obstacle. Now I'm burning in the isinstance/hasattr/getattr/setattr hell.

  • @Mods, please don't delete this. It's a valuable lesson.

  • This isn't about some feature of the language being good or bad. It's about Rust being ugly or not. The things I mentioned will always look ugly in the source code.

  • Enums and nested blocks. I understand the importance of Option and Result, but it's fucking infuriating when I have to check and destructure the result of every function call and either bubble the result up the stack from six levels of nested if let blocks or risk Cloudflaring my program by using .unwrap(). And while I like being able to extract a return value from an if...else expression, the structure gets really convoluted when multiple if and match blocks are nested (of course each one returning a value), and it gets completely fucked once closures are introduced.

    I like Rust, but calling it pretty is delusional.

  • Network Chuck's earlier videos are pretty good, especially the You Suck At... series.

    Unfortunately he's been pushing AI shit lately.

  • 15000 rows. 120 columns. One sheet. Creation date: 2011. A dedicated computer. Working at a multinational company is bad for mental health.