ParetoOptimal

Yeah... you captured it very well. Another idea might be having it do a jarring transition to another topic, speed up a bit, go to another topic, etc.

The snap back to "now it's time to give your morning standup update" hit hard btw :)

> While going through the simulator, I was shocked with the response to some choices and situations. I was not aware that these things were so disruptive to some people.

Well, I guess the simulator did a good job spreading awareness that it is like that for some?

I have ADHD and while I'm medicated I cannot fathom some of the struggles or decisions that unmedicated me makes... like I struggle to have empathy for unmedicated me.

I imagine without such deep personal experience it would be much harder or impossible to understand or empathize.

It makes it easier to read though because the least important parts are most easily ignored. The reader can focus on the contents of the list.

> All that really matters is consistency. Let a team make some decisions and then just move forward.

Not so! Amount of tokens correlates to perceived code complexity to some. One example is how some people can't unsee or look past lisps parenthesis.

Another example is how some people get used to longDescriptiveVariableNames but others find that overwhelming (me for instance) when you have something like:

    userSignup = do
        let fullName = userFirstNameInput + userLastNameInput
            userName = take 1 userFirstNameInput + take 10 userLastNameInput
        saveToDB userName

Above isn't bad, but imagine variables named that verbosely used over and over, esp in same line.

Compare it to:

    userSignup = do
        let fullName = firstName + lastName
            userName = take 1 firstName + take 10 lastName
        saveToDB userName

The second example loses some information, but I'd argue it doesn't matter too much given the context one would typically have in a function named `userSignup`.

I've had codebases where consistency required naming all variables like `firstNameInputField` rather than just `firstName` and it made functions unreadable because it made the unimportant parts seem more important than they were simply by taking up more space.

> I promise after a week you'll just get used to whatever format your team lands on.

Arthur Witney formats like this:

    C vt[]="+{~<#,";
    A(*vd[])()={0,plus,from,find,0,rsh,cat},
     (*vm[])()={0,id,size,iota,box,sha,0};

If your code was formatted automatically like that, do you think you'd get used to it after a week?

My point is there is meaning of how code is formatted and there is an effect on understanding for certain people.

I think that at a certain point of "reasonable" and for most "normal" people your statements hold true, but I don't want anyone to think that every person caught up on formatting is just doing it for bike-shedding or other trivial reasons.

I don't know what is actionable if what I say is true, but it feels important to say.

Yeah, pretty ridiculous... maybe we can move off of hackernews too.

You probably give up just as much privacy with VS Code as you do with Zed, no? Just sent to different overlords?

Maybe it's more capable because driving small truck could make people think your genitalia is small?

Not my personal opinion... but wonder how much of a factor this is :)

> Google has been sued and lost for much lesser privacy infringements, like tracking users while in incognito, which if you read the suit is pretty absurd.

But those suits dont matter:

- the penalty they have to pay is laughably small

- consumers by and large dont know or dont care enough to switch away from Chrome.

> How do you fix a bug you can't reproduce?

You strangle it from the edges.

This is the way.

I think it doesn't work over tcp but try with the other GUI library.

There is inherent limitation of latency/responsiveness in the tramp model versus the copy vscode server to my server and communicate with it model.

The tramp model does have the advantage of little to no resource usage, but these days most aren't concerned about that.