Both_Confidence_4147@alien.topB to Emacs@communick.newsEnglish · 10 months 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.topB to Emacs@communick.newsEnglish · 10 months agomessage-square24fedilink
minus-squareMitchellMarquez42@alien.topBlinkfedilinkEnglisharrow-up1·10 months 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.topOPBlinkfedilinkEnglisharrow-up1·10 months agoThat does not justify 5000 lines of code
minus-squareMitchellMarquez42@alien.topBlinkfedilinkEnglisharrow-up1·10 months 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-squarenoooit@alien.topBlinkfedilinkEnglisharrow-up1·10 months agoIf you have to compare with vterm, it doesn’t. Vterm has more features, faster and less buggy.
minus-squareBabySavesko@alien.topBlinkfedilinkEnglisharrow-up1·10 months 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
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
If you have to compare with vterm, it doesn’t. Vterm has more features, faster and less buggy.
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