I'm curious how you came to the conclusion that naming it 'screen' was the best thing for your project?

It's unusual to see so many negative comments on a new project announcement and yet you persist and even double down with a sarcastic "thanks for your feedback" reply.

Thanks for all the feedback! I've updated the readme to use the word "renderer" rather an "emulator."

Gonna stick with the name screen though

script kiddies are now going to have high-fidelity shells with 256 colors for when they pwn you and get root on your godaddy drupal install

sidenote: screen is a terrible name for this as there is already gnu/screen (colloquially referred to as screen) which has 38 years head start - https://en.wikipedia.org/wiki/GNU_Screen

also til screen is older than me

I'm a little confused--is it an interactive terminal? Or is it more like an ANSI renderer where you are producing a single static image of the final result of printing a series of bytes? I don't see any JavaScript to hint at interactivity.

I was hoping for an actual desktop app powered by PHP, which would be really cool having PHP as a desktop runtime.

Didn't we have this back in 2001. I seems to remember that we kicked a guy of our project because he installed one of the PHP consoles on our Solaris box, which basically gave it the same rights as the Apache user.

Oh, interesting!

I started a very similar project probably ten years ago and just never got it to a very usable state. My idea at the time was based in wanting to be able to write tests for the final output of scripts full of control codes.

I am very excited to see this and to play with it!

Does it render to plain text or styled HTML? Not quite clear from the readme.

Commendable work but note that this is not a terminal emulator. This is a terminal renderer.

Nice, but your terminal app has a name collision with the long lived ''screen'' terminal multiplexer utility:

https://www.gnu.org/software/screen/manual/screen.html