Skip Navigation

帖子
2
评论
378
加入于
2 yr. ago

  • Amplifier at the bottom, when it's the only thing that generates significant heat? Plainly not an audiophile set-up. Should be on top, and the turntable should be off to one side on one of those vibration isolation decks. Kids these days, eh?

  • We live in the suburbs (UK), and our place is lousy with foxes - might be the most common animal you see. On the plus side, the cubs are incredibly cute; but on the downside, "fox romance" is not what you want to be listening to at three in the morning, and our cats go crazy chasing them out of our garden. Could do without them getting into a scrap and causing me some crazy vet's bills.

  • 980 m/s muzzle velocity on that thing, so that's at least 4 seconds of gravity and wind interference accounted for in the aim. Bordering on the supernatural.

  • Happy Mullvad user here. In an ideal world we'd have both - GUI is great for my phone, laptop and desktop, but my home server needs CLI.

    And Mullvad lets you have five 'things' on each account, which since their naming convention is a bit crazy, allows me to recreate the connection for one thing before I have to go through them all and note down which is which.

  • Low-level bridge play requires quite a lot of intuition, but high-level play is very much the opposite. Top players have basically a phone book of what every bid, every play means, and expect their partners to follow it exactly. The only communication allowed is through numbers and cards, and they must precisely follow what you have. In competition play, if anyone makes a strange bid or plays a 'weird' card, you may stop play to ask their partner what they understand by that, and they must answer correctly or risk having points deducted by the adjudicator if they were perceived to have mislead. It's very mathematical.

    Ironically, I quite enjoy playing with low-level players when it's a laugh, but high-level players tend to start with OCD and build on top of that.

  • Seeking a technical solution to a non-technical problem. Rather than having one set of company-hosted servers that they then struggle to police, just let everyone host their own, and they can be responsible for banning anyone that doesn't follow the community rules.

  • Actually makes it easier to write aimbots and triggerbots, since you'll have the video feed and can respond with the right inputs. Skips the step where you've got to film the monitor on the machine that's 'playing' the game, which is protected by the HDCP between the PC and the screen.

  • 已删除

    Permanently Deleted

    跳过
  • That's why I like make basic grammatical mistakes, speling erors, and include a few fucks in my internet writing. Nobody's not gona mistake me for no got dagned robot.

  • Strange, it has the 'autoplay more like this' option on the web player (which does basically the same) but not the explicit 'artist radio' option. Huh.

  • "Go to Radio" on the app. Hmm...

  • SIMD is pretty simple really, but it's been 30 years since it's been a standard-ish feature in CPUs, and modern compilers are "just about able to sometimes" use SIMD if you've got a very simple loop with fixed endpoints that might use it. It's one thing that you might fall back to writing assembly to use - the FFmpeg developers had an article not too long ago about getting a 10% speed improvement by writing all the SIMD by hand.

    Using an NPU means recognising algorithms that can be broken down into parallelizable, networkable steps with information passing between cells. Basically, you're playing a game of TIS-100 with your code. It's fragile and difficult, and there's no chance that your compiler will do that automatically.

    Best thing to hope for is that some standard libraries can implement it, and then we can all benefit. It's an okay tool for 'jobs that can be broken down into separate cells that interact', so some kinds of image processing, maybe things like liquid flow simulations. There's a very small overlap between 'things that are just algorithms that the main CPU would do better' and 'things that can be broken down into many many simple steps that a GPU would do better' where an NPU really makes sense, tho.

  • Aww. We buried our old cat's ashes at the spot in the garden where he loved to sit and watch the world - a shady spot under the rhubarb. It's where new cat loves to sit as well.

  • I'm not sure that they're even going to be useful for gamers. Datacenter GPUs require a substantial external cooling solution to stop them from just melting. Believe NVidia's new stuff is liquid-only, so even if you've got an HVAC next to your l33t gaming PC, that won't be sufficient.

  • They have the human made ones, they have the "artist radio" function that plays songs similar to a band you like, they have a weekly top 30 based on stuff you've been listening to. The headline 'albums of the week' are based on what they like, which I don't think is unfair - I've really enjoyed some of them.

    I listen to a lot of metal and electronic, and I've always found the descriptions excellent - usually several paragraphs even for the most obscure of bands. Was well impressed that they had Lambrini Girls as one of their 'albums of the week', and their album at studio quality. Not that that's essential for punk. Admittedly I don't listen to a lot of indy, but they've always had what I've wanted to listen to.

    My main complaint about the UX is that it's nearly identical to Spotify, but I suppose there's not much else you can do. Something particular about it that you dislike?

  • Yeah, the web client works just fine on Linux. A good native client would be better, of course, but I'd rather use the web one than a half-assed native one.

  • Just saying; cancelling Spotify and changing to Qobuz takes five minutes. Sound quality is amazingly better, the curated recommendations are done by human beings that love music, and 'just works' with everything that Spotify does. (For us, anyway.) It's French, rather than Norwegian-American like Tidal is, if you're trying to stop spending money on everything US at the moment, too.

  • Yeah, we have that with our customers sometimes. To me, an app should either be running full whack - maxing out bandwidth on CPU, disk, memory or network - or completely idle. Chuntering along at 2% is a bug. For the ones that put 'monitoring tools' that raise errors when we reach 100% on something, we set a Linux CGroup to throttle the offending resource. Takes longer, obviously, but not worth arguing with their network deployment teams 🤷 .

  • Number one! Number one! Woo!