5 comments

  • zgubi 5 hours ago ago

      ┌───────────────────────────────────────────────┐
      │  KRNL — the text-mode web browser, in the cloud │
      │  Ctrl-C or close the terminal to end the demo.  │
      └───────────────────────────────────────────────┘
    Starting BrowserBox Terminal Kernel...

    Error: Failed to start kernel - Cannot find module 'chroma-js' Require stack: - /tmp/sea-terminal-kit-f476015698c8cef721a6637233bd9330/client/node_modules/terminal-kit/lib/termkit.js - /tmp/sea-terminal-kit-f476015698c8cef721a6637233bd9330/client/noop.js Connection to krnl.duetbrowser.com closed.

    • rrvsh 3 hours ago ago

      same sadly

      • keepamovin 3 hours ago ago

        edit: Can confirm I fixed a few bugs, rolled the fleet and the new version looks pretty good. LMK what you think!

        Thanks! That's weird. I just confirmed a real launch is live so the service remains available generally.

        Can I ask what region you connected to?

        I'll check any logs to see what might be up. Possible timing race on module load inside SEA.

  • quotemstr 9 hours ago ago

    You might want to consider using atomic update escape codes: https://github.com/contour-terminal/vt-extensions/blob/maste...

    The interface flickers like crazy right now.

    • keepamovin 9 hours ago ago

      Thank you. Can you record a video of the flickering you’re seeing?

      edit: I just recorded a demo here: https://youtu.be/dbNlXjC0lo0

      Which parts are flickering? In your run, what did you see? A video (or asciinema) would be most helpful!

      I just tested your atomics idea now and it seems to improve render speed noticably, and it might appear more smooth. Thanks for that. Please check it out and lmk what you think - the fleet will be rolled a bit later, I'll let you know when you can try the update.