Skip to content

馃晵 Introducing the 'Time Travel Debugging' Feature - Because Why Not? 馃晵#17

Description

@wweziza

Dear Time Lords of 'Next.js Use PHP',

I've recently embarked on a journey with your framework, and let me just say, it's been... a unique experience. But, I've noticed a glaring omission that's practically a deal-breaker. I'm shocked, nay, appalled, that there's no built-in time travel functionality. How could this be overlooked?

Here's why it's absolutely essential:

  1. Debugging in the Past: Who needs modern tools when you can just go back to the moment your code was written and ask your past self what they were thinking? I mean, come on, it's just common sense.

  2. Future-Proofing: I need to know if my code will still be hip and happening in the year 3000. What if JavaScript is replaced by telepathic coding? We must prepare for such eventualities!

  3. Temporal Styling: Style trends change. I need to ensure my CSS is just as snazzy in the Renaissance as it is in the distant future.

As a forward-thinking (and backward-thinking) developer, I propose the immediate implementation of a 'Temporal Debugging' feature. It's clearly what the industry has been missing.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions