511 karma · joined June 4, 2020
Okay... Pauli and Dirac both received Nobel Prizes for discovering spinors. Nobody needed to discover pointing in some direction.
Except just about all relevant applications that exist in computer science and physics where fixating on a representation is the standard.
Literally everything you do gets the full power of the chips. They finish tasks faster using less power than previous chips. They can then use smaller batteries and thinner devices. A higher ceiling on performance is only one aspect of an upgraded CPU. A lower floor on energy consumed per task is typically much more important for mobile devices.
Claude Code is still only a mildly useful tool because it's horrific beyond a certain breadth of scope. If I asked it to solve the same problem 10,000 times I'm sure I'd get a great answer to significantly more difficult problems, but that doesn't help me as I'm not capable of scaling myself to checking 10,000 answers.
But now that the map only shows me three possible countries I can trivially remember which one it was. Ask me again tomorrow while only showing me the full map and I might guess it's in South America.
To not lose. History is full of stories of incumbents not wanting to cannibalize themselves and dying because of it.
We can't prove the correctness of the plurality of physics. Should we call that a dead end too?
...and that's just as asinine of a claim as the original one
lol
That's incorrect. The optimizer has to assume everything escapes the current optimization unit unless explicitly told otherwise. It needs explicit guarantees about the visibility to figure out the extent of the derivations allowed.
That's absurdly naive to think the simplistic constraints of your own workflow is a general rule.
I don't need most of the history, but there's 0 chance in hell I'm auditing that many lines to decide what I need and what I don't need.
iterm window->iterm tab->ssh->tmux windows->tmux panes
With `tmux -CC` it lets you hoist that chain upwards and map the entire ssh session into an iterm window.
iterm window (ssh session) -> iterm tabs (tmux windows)
The biggest benefit for me is that you can then open another tmux session within the CC one and use tmux as normal
iterm window (ssh session) -> iterm tabs (tmux windows) -> tmux2 windows -> tmux2 panes
And then the normal feature of tmux is that it persists across ssh sessions. This also means that the entire iTerm2 window and all its tabs and splits are also maintained across sessions. I think my current layout on my main development machine that I remote into is over 3 months old.
Another point of view is that it decouples the state of your tmux tabs/panes from your terminal emulator itself. e.g. if you use this locally instead you could then terminate the entire iterm program and reopen it and restore the same exact window/tab/pane splits you previously had. This is a nice perk for restarting/updating iTerm.