Both_Confidence_4147@alien.topcakeB to Emacs@communick.newsEnglish · 1 year agoWhat is the point of using Vterm or Eat?message-squaremessage-square24fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1message-squareWhat is the point of using Vterm or Eat?Both_Confidence_4147@alien.topcakeB to Emacs@communick.newsEnglish · 1 year agomessage-square24fedilink
minus-squareMitchellMarquez42@alien.topBlinkfedilinkEnglisharrow-up1·1 year agoVterm: none that I can see Eat: it’s awesome, very good and fast and mouse input works out of the box
minus-squareBoth_Confidence_4147@alien.topcakeOPBlinkfedilinkEnglisharrow-up1·1 year agoThat does not justify 5000 lines of code
minus-squarenoooit@alien.topBlinkfedilinkEnglisharrow-up1·1 year agoIf you have to compare with vterm, it doesn’t. Vterm has more features, faster and less buggy.
minus-squareMitchellMarquez42@alien.topBlinkfedilinkEnglisharrow-up1·1 year agoMy weakest computer can fit twenty million lines of codes on it. I’d say if anything, the usefulness of eat would justify a lot more. Thankfully doing one thing well lends itself to brevity, and storage is cheap
minus-squareBabySavesko@alien.topBlinkfedilinkEnglisharrow-up1·1 year agoI believe the EAT readme itself recommends vterm for particular use cases, like (if I recall correctly) needing an emulator that handles large volume of text streaming
Vterm: none that I can see
Eat: it’s awesome, very good and fast and mouse input works out of the box
That does not justify 5000 lines of code
If you have to compare with vterm, it doesn’t. Vterm has more features, faster and less buggy.
My weakest computer can fit twenty million lines of codes on it.
I’d say if anything, the usefulness of eat would justify a lot more. Thankfully doing one thing well lends itself to brevity, and storage is cheap
I believe the EAT readme itself recommends vterm for particular use cases, like (if I recall correctly) needing an emulator that handles large volume of text streaming