__hugues

they do have to include the deep fat fryer and oil...

unless you want some sad thawed potatoes instead of fries

and that's going to run you a lot more than $4, and take quite a while to amortize

seems really dumb and like it would need to violate basic information theory to work?

input tokens are cheaper than output tokens. seems like it would maybe reduce input tokens at the expense of many more output tokens if you're actually triggering OCR via thinking?

45s? how long do your apps take to start? what dependencies exist between your apps?

sway-layout does not enforce any dependencies between apps. everything is started concurrently, so unless your apps manage their own interdependencies, it's not going to work

on the other hand, that means the initial wait should be much shorter

one potential avenue you could explore might be to configure a headless output, and try to have your slow starting apps/workspaces anchored there until they are ready. I haven't trie it though...

>> There is a path by which these policies can be implemented without material adverse consequences, but it is narrow, and will require currency offset for tariffs and either gradualism or coordination with allies or the Federal Reserve on the dollar. Potential for unwelcome economic and market volatility is substantial, but there are steps the Administration can take to minimize it.

"gradualism", "coordination with allies", are things that this administration is famously good at, so it's probably all going to work out /s

In your email example, the sender would be in violation of the license, not the recipient so it doesn't seem like a huge problem: if someone wants to build a better email client (for whatever metric) then the users of that client either need to make their own emails public (granted, not terribly exciting) or obtain a written permission for private use (presumably but not necessarily conditioned on paying a fee)

Yeah, communication tools are not a good fit for this experiment.

What I had in mind was mostly dev tools (e.g. slipcover, ruff, uv, ...) where

- individuals being able to freely use them on personal/unreleased code, and anyone being able to use freely them on open source projects unlocks a ton of public benefit

- large tech companies might legitimately cut their ec2 costs by 50% or more thanks to the increased efficiency

- there is not much room for SaaS or maintenance contracts to generate an income for the original author

Having a short period people working on projects they are unwilling to open source are incentivized to share a portion of their cost savings seems like it would be a low-hassle way to foster a healthy ecosystem of public benefit tooling