The important metrics is peak requests per second. 14M / day sounds impressive, but it’s only a sustained 160 per second which literally any language and framework can handle on the lowest end hardware.
Sure, peaks are much higher. But a good part of it is reverse proxying with in-memory caching and locking, which I've implemented in several stacks over the years, and many struggle with it (I have been paid to do comprehensive benchmarks on the topic). On the BEAM it's a non-event.
Even pre ai you could toss together a decent cache in about a minute using ets or similar, and faster with a solution like cachex (which was basically what you'd build yourself but packaged into a neat little bundle)
Sure, that's why I highlighted peaks as a more important metric than average. Even an order of magnitude higher peaks over the average is still fairly trivial, compared to where BEAM shines. Maintaining hundreds of thousands of concurrent long-lived connections per server is what it excels at, but also not something that's relevant to 99% of web apps out there.
Gotta love that Github has decided that hiding largest diffs by default was a good idea. It's not like the amount of changes has any correlation to importance, right? And to top off the joke that they are, it's still amazingly slow, even when you skip the bulk of the code.
At this point I don't know if anyone at github does code reviews. They hide large diffs as you said, but navigation is also broken, I have to click several times on a filename for the UI to scroll to it.
They also decided that comments should not be visible instead you have to hunt for a tiny avatar of the person who left them. Very puzzling
At least they finally fixed the sidebar to use anchor tags instead of divs, so right-click can open the file in a new tab. It's still a bit wonky, since the a tag is only the size of the filename, with zero padding. It was broken since they introduced their new UI sometime last year.
Maybe by the end of 2027 clicking a filename actually takes you to it.
I heard that's why Washington state was chosen. Close to tech talent (Microsoft was there) and fewer people living there than other tech-heavy states such as California, so the US tax-exempt market was larger from Washington state.
It’s been years since anything Tether minted was plausibly 100% backed by real assets. Both times they’ve been forced to show the books, they only had fractional backing. And they’ve minted tens of billions of tokens since.
And yet people like the parent and those with billions invested in Tether seem to believe that it's all backed and fully solvent and minting new money from thin air is completely reasonable.
It's remarkable to me how long this scam has lasted and how much confidence people have in it, in spite of the very shady characters involved and the likelihood of fraud.
Personally I'm skeptical of Tether. But you don't need to trust them to believe that if they permanently freeze Z USDT and then mint Z USDT then their ratio of reserves to USDT is unchanged.
Well I think you do need to trust them: you are taking at face value their statements and assuming they do what they say they will. What if they mint coins without collateral (they have been caught doing this before), what if they unfreeze coins later (they have done this before)?
These stablecoins are just a database owned by untrustworthy people and backed by nothing but their promises, they're just one step up from NFTs.
Unless you're actually CPU-bound, there's never been a better time to use it. A lot of the benefits of Rails apply as much to LLMs as humans.
It's battle-tested, there are millions of lines of existing code using common patterns and libraries. It's still the gold standard for testability, with RSpec and factory_bot you'll have the nicest test setup with concise, human-friendly specs (especially if you're in the camp of verifying LLM work). Solid queue, cache, Active Storage with Turbo Frames give you all the benefits of single-page interactivity without the JS slop. Code size is a fraction of an equivalent JS setup, which is always nice for LLMs, went from close to 80k lines of JS to ~10k of Rails just recently on an internal project.
Historically, the main complaint was always "it's hard to hire for Rails" or "I don't know Ruby". But looking at the last 10 years of JS, I'm not sure the vast majority of JS slingers knew anything about Javascript either. And since everybody's vibing now anyway, why venture to the minefield that is the JS ecosystem.
> It's not possible to steal numerous paper-based elections in a row
Why not? Estonia had paper ballot voting for the entire soviet occupation of about half a century, didn't have any effect on the amount of rigging though. Same with Russia today, they use paper ballots, but results still don't matter.
Paper vs electronic voting is just a small component in election fairness and there are upsides and downsides to both.
Because there's no theoretical room for fraud if you design the paper ballot system correctly so that the process is observed by independent and opposing parties and everyone is doing their job.
The key point being "everyone is doing their job". You need to make the system so transparent and involve so many observers/auditors that there's nowhere for corruption to hide.
If you threaten the opposition with prison (or worse) if they tell anyone about your fraud then you don't have a democracy to begin with. The only way to preserve any semblance of legitimacy is if you manage to keep thousands to tens of thousands of people quiet on all of this.
In the GDR the 1989 voting was an important trigger for the revolution. The citizens counted the votes too and could thus published election results independent of the official ones. So in effect it does stop that the rigging can be hidden.
reply