No. This is by design. I do not like it. It's a tactic often deployed by libraries that want to retain some control over scanned assets. To be fair, normally they are funded by tax payers.
The problem is that a lot of those old ISA drivers were peeking and poking card registers as fast as the bus would allow, which was over 1 MHz (less than 1 microsecond per transaction), not DMAing data to RAM (though some did that too).
With a modern 4 GHz CPU, that means your budget is only 4000 clocks per interrupt. The context save alone can make it hard to hit 1MHz, and you really want to have your interrupt code pinned to the L1 cache because a few memory reads will blow your entire budget.
As nice as USB4 is, I’ve never heard anyone claim it has single-digit microsecond latency, to say nothing of sub-microsecond latency. The typically-quoted ~20 usec latency of USB4 limits it to around 50 kHz for an emulated ISA card.
Often people confuse latency vs throughput/bandwidth. With streaming and batching USB4 will shuffle a lot data through on average per second. But it will never hit reliable microsecond level or even submicrosecond latencies.
At the same time ISA card will never reach 40Gbps throughout with CPU clocking at tens of MHz only or often less.
Mr Rossman will literally tell you to use an ad-blocker to watch his videos and refuses to take sponsorships, actively does not want money from making YouTube videos and just wants to get the word out. I'd agree with you if it was literally any other creator.
Two things can be true at once, especially when talking about people’s behaviour. I don’t know this guy from atom, but if he’s a YouTuber then my instinct is to not trust him.
Louis Rossman does not take sponsorships, and turns off ads for his videos as much as YouTube allows. His videos are for his opinions, not making money.
This is on one (or two) particular domain(s) where setting up wildcard DNS should be relatively trivial, if they actually cared enough about the UX of this product to make a special case in their code.
I don't understand how people can launch stuff like this.
"A US embassy staffer accused of possessing indecent images of children, was detained at his south London flat and flown out of the UK in August, without being first questioned by British police."
Sure, I get the overall mechanics. "was... flown" - any brits here to help? What exactly does this mean in BBC English? It implies something, doesn't it?
I assume he was taken to a US airbase and flown from there.
Americans can recall diplomats back to their home country at any time. He was recalled somewhat more hastily than most.
I imagine they said something to the effect of “you will be deported and stand trial in the US; the only question is whether you’re prosecuted in the UK as well”. I imagine that, plus promises to keep his name out of the media, were convincing.
The BBC article goes on with "He was flown back to the United States on a commercial flight, but their investigations are ongoing in conjunction with UK authorities." though.
That's good when the sex offense is for something truly evil.
The problem is the US is a Puritan asylum, so things that'd never register as offenses in sane countries, sexual or otherwise, can get people's names in that registry, destroying their lives.
And several States are weaponizing this by expanding what's legally labeled as sexually offensive so it covers harmless behaviors of minorities, so now there are people under risk of getting included in the registry due basically to existing.
I worked with a few people (tech) that Spotify later hired. Sweden is kind of small.
The calibre went from extremely high to surprisingly average within a decade. Not bad, to be clear, but kinda mid. I think they scaled too quickly and hit the 'bozo effect'.
What's funny about having to rely on unauthorized clones to provide a fast native UX was that Spotify's original client back in 2008 started out as beautifully light, custom rendered native client.
Few Apps ever had that wow factor the first time I used it, it was so much lighter and more responsive than anything else of the day. I remember being perplexed at how I could search and skip to any part of a song quicker than iTunes could looking at a local library. Everything was latency-free and instantaneous.
We were building a Music Startup at the time, so we investigated how it worked. We we’re very surprised we couldn’t find any evidence of an established UI toolkit. It looked as though they had built their own custom UI renderer and optimized TCP protocol which sent back its metadata in XML. Their traffic looked like it was initially seeded from their own (or CDN) servers (for best latency) and then overtime we would see some P2P traffic on the wire.
Our QT/C++ client had decent performance but was noticeably heavier than Spotify's. I was disappointed to see their native client eventually be abandoned and succumb to become yet another Chromium wrapper. I expect it fell to the pressures of a growing startup adding 100s of developers (without the skill of their original CTO/devs) where a native UI couldn't be updated and re-iterated as fast as a Web App. I wish they maintained 2 desktop clients, and left their native client alone to just be an audio player and push all their new social features to their new flagship CEF app.
It's unfortunate the skill and desire of building fast native UIs are being lost to Electron and CEF wrappers. Seems the larger the organization the more likely they are to build new Web rendered Desktop Apps and we have to rely on unauthorized Indie efforts like this for fast, responsive native UIs.
(The comment is from a 2021 post about another Rust-based Spotify client.)
The answer is weaponized scraping.
reply