Why is it so hard to see code from 5 minutes ago? • Hacker News Board

Re: Why is it so hard to see code from 5 minutes ago?

#421

Post by AlexCoventry » Tue, Feb 23, 2021, 11:53 PM UTC

Hackbraten wrote: post #415

AlexCoventry wrote: post #122

Earlier quoted context omitted.

Where would you want to use `git commit-tree`?

It’s a convenient shortcut to take an existing commit and append to it a new commit that changes the file tree to any state you want. For example, if you want that new commit to result in the exact same file tree as another existing commit in the same repository, you can tell git commit-tree to make exactly that happen. It will also just print the new commit hash without moving `HEAD`, which is why it may also be use…

Thanks.

Re: Why is it so hard to see code from 5 minutes ago?

#422

Post by SureshG » Fri, Feb 26, 2021, 8:33 AM UTC

strken wrote: post #299

pharke wrote: post #253

Earlier quoted context omitted.

That's an insane approach, eslint solves this just fine and is fully configurable for almost any style preference.

All Go code everywhere never has unused variables, never has unused imports, and is formatted similarly. But, when you're debugging a function, you can't leave unused variables or imports lying around. It's a tradeoff. I don't think either side of the tradeoff is insane.

You can do underscore import and local variable to workaround this limitation and I have seen that in the code.

Re: Why is it so hard to see code from 5 minutes ago?

#423

Post by happimess » Mon, Mar 01, 2021, 5:02 PM UTC

quacked wrote: post #406

happimess wrote: post #382

Earlier quoted context omitted.

For the record, I think the second version is a clear improvement.

Out of curiosity, do you do much creative writing? I agree that the second version is clearer and more grammatically sensible, but the first version bends the normal usage of syntax to evoke emotion, although a word here or there could be adjusted. Here's an example of a similar update; would you say you like the second version more? "Halting, stuttering, his words slurred, his eyes watery, his knees trembling, he th…

In both, the aloneness of "him" is the focus. In the first, his companions are the subject of both sentences. In the second, The fog and "he" are the focus, with his companions only mentioned as an afterthought.

Re: Why is it so hard to see code from 5 minutes ago?

#424

Post by SharpNinja » Thu, Mar 04, 2021, 2:04 PM UTC

I have had this same idea and would love to collaborate. I can see tgis as either an extension to be added to existing IDEs or an enhancement to the Monaco Editor.

I see it as a product named Multiverse Editing. You start off coding in the prime universe. Each Undo places a node on the current universe's timeline. If you continue editing you are still on the prime timeline. But you can click on any node in the timeline to go back, and editing from there branches to a new universe with its own unique timeline. Each node represents either complete before and after code for the current timeline and a pointer to the root of one or more new universes. you can select any two or three nodes and perform a merge which results in another new universe branching from the source (left) node of the merge. A database will exist for each source file, each representing their own multiverse. Source control events would become nodes on the timelines such as branches becoming a new universe and merges collapsing universes together. Ideally the database would be in the SCP and not the editor, though that might get slow, nut that would preserve the complete edit history for a file. Each node would have metadata where the developer could add notes in MD format, etc.