I thought the same, too. Generally some small amount of inflation is preferable to encourage spending, rather than deflation which discourages it.
If you know a $100 item will probably cost $102 later then you're more likely to buy it now. But if that item will cost $98 in a deflationary environment, then maybe you'll wait to buy it later. Wages also tend to fall in deflation, which makes it harder to pay back debt, so lending slows down - people won't buy houses or cars, etc. Businesses hold back on capital spending. The economy slows to a standstill: if no one is spending money, how can anyone make money?
Which translations would you recommend for Crime and Punishment or Dostoyevsky in general?
When I'm starting to read a non-English novel, the process of deciding which translation to use is half the fun. The Kent and Berbera (revised Garnett) version of Anna Karenina was mesmerizing.
There's a lot of low-density sprawl in San Diego county which makes effective transit difficult, and because you have to drive everywhere, sentiment trends anti-bicycle. The previous CEO of SANDAG tried to push a mobility-centric vision but left because of intense pushback from folks who wanted more funding for roads and freeways, rather than transit and bike paths.
> I believe with x402 and USDC you can pay as low as $0.000001 per HTTP request with no fees.
On-chain transactions are still not free. x402 isn't settled in batches or rolled up anywhere AFAIK, so large volumes of tiny payments are still not cost-effective. Facilitators such as Coinbase only subsidize transactions up to a point: https://docs.cdp.coinbase.com/x402/core-concepts/facilitator
The accepted norm is, increasingly, full disk access, regardless of how bad of an idea it is. At a minimum, agents typically will have a way of obtaining new access tokens.
Refresh tokens don't solve anything in this case; they just shuffle the problem around, and introduce other complications of their own.
What you want are capability scoped credentials that are enforced on the backend. That is agnostic to credential issuance mechanism, although passkeys are the best.
Using these credentials effectively still presupposes hygiene that might not exist in a typical developer environment, eg no root credentials (or access to such) sitting anywhere. There's probably a good product and market for whoever can solve this in a low-friction way.
With SQLite, you're basically funneled towards a single-writer / single-process design anyway ... in which case why not use a more traditional condvar + mutex rather than polling?
This describes my team to a T ... are we working at the same place?!?
We actually talk more now which helps, but it is still hard to keep up when everyone is barreling ahead doing their own thing. In addition to more talking, there needs to be a semblance of strategy that everyone is aligned on and understands their role in.
A high-agency, high-functioning team has always been a superpower, but mastering this capability is what will make or break organizations that are trying to run lean with AI. It's a "people problem" at its core, and no amount of technology can fix that.
This is where curation matters, eg in a newsroom or gallery. Provenance is their job, and if done well, can connect people in a way that an unfiltered social media firehose can't.
That just moves the bytecode compilation to the server -- so you're back to my original point of generating the code statically. In fact it'd probably be worse, since there is no reason to compile MyScript.rb to bytecode more than once. It's like generating a dynamic page with Rails when all you really need is static, cacheable HTML.
I might be missing something here, but this implicates a few things:
You won't be writing code in the browser anymore. Otherwise you'd have fragmentation where the user doesn't have the proper interpreter installed, and a never ending stream of "language downloads" which might be cool to devs but horribly impractical for end users.
Because we're not writing in the browser anymore, we'd be back to offline compilation and static code generation. I suppose it'd be possible to JIT the bytecode (assuming that current Javascript optimizers work on the IR; I don't know enough to qualify this any further). From my casual browsing of LtU, it seems that tracing JITs in particular may offer optimizations dificult to achieve with static bytecode compilation, particularly in identifying hot spots. But the more I think of it, that's a non-issue because you're still compiling to bytecode and JITing from there.
This feels very Java-ish to me. If you really want to script the browser in another language, compiling to Javascript (a'la GWT) would essentially do the same thing.
If you know a $100 item will probably cost $102 later then you're more likely to buy it now. But if that item will cost $98 in a deflationary environment, then maybe you'll wait to buy it later. Wages also tend to fall in deflation, which makes it harder to pay back debt, so lending slows down - people won't buy houses or cars, etc. Businesses hold back on capital spending. The economy slows to a standstill: if no one is spending money, how can anyone make money?