Remix.run Logo
antisol a day ago

(2/2)

  > it's there while I'm releasing the Enter key
This is empirically, demonstrably untrue, because the "launch application" action does not begin until the "key release" event has fired. Which is something you'd know if you understood how your interface works.

  > And before you start taking into account that a lot of gui software is just poorly written trash seemingly written by morons under the CADT model (Hi, gnome!).
  
  We can definitely agree here!!! :)
*cough* Whoosh!

  > Better than reinventing a whole new kind of terminal applications which aren't actual terminal applications, 
OMG you're totally right! Let's just stay using 1970s tech and never improve anything! Just remember to never ever update your browser!

Why are they not actual terminal applications? What terminal functionality do they lack? Please provide excruciating technical detail on this subject about which you know nothing.

  > but only work in an environment emulated by the very thing they want to replace.
I know right! It's so rare and exotic for people in 2026 to have hardware capable of graphics! And in colour, too! Such an onerous requirement! And also it's obviously totally impossible to ever detect whether a program is running in an environment where graphics are supported and fall back to a text-only mode! Oh noes! What will we do when they force graphical output into the kernel with no option to disable it?!?!

For the umpteenth time, who said anything about replacing guis? I have repeatedly stated that they have their uses and are the best option for a bunch of things.

  > The same morons will come and screw up with all kinds of things there again, once that'd get more momentum. But now, since they also have to maintain EFL plugins or other graphical-to-terminal translations for their apps and file formats, they will even screw up heavier.
Why are these people writing gui programs that run in a terminal in your contrived fantasy scenario? Again, for the 50th time, who suggested this or advocated for it? When?

EFL plugins? Graphical to terminal translations? What are you talking about? It's almost like you don't understand the technology and have invented some fantasy architecture for all this stuff which is nothing like the actual architecture that exists and has been described here and elsewhere.

  > On an average day, I open a Dolphin window maybe once or twice... Often not even once (e.g. I just open my IDE and stay there, or the browser, or a game, you name it). You don't need a new one for every operation! 
Right, but we're not talking about an average day. We're talking about a specific scenario where you have described a specific workflow which you are claiming is somehow superior to the one which I have outlined, and which is demonstrably superior by several metrics which I and others care about. I don't actually give a fuck what you do on an average day, or how often you start dolphin. You're the one who claimed that you would start dolphin, and then another program like vlc, to do what I can do without starting anything. If you're now claiming that you don't actually need to start dolphin, then why did you waste my time by advocating that workflow?

  > if your workflow is seriously superior, then be happy that EFL and all that exists and supports all the file formats that you want to preview, and be happy that it provides all the features you need. I'm happy with you then. I have the feeling that it's a very special workflow for a very special task at best, though.
Your "feeling" about my workflow is worth less than nothing. Because, yet again, you don't know what my workflow is. Because you don't understand it. Because you haven't bothered to try to understand it. And that's fine for you, if you prefer your worse windows-like UI then go and enjoy writing trash in visual studio. I'm happy for you. But don't think that that means you're somehow qualified to talk about terminals and their pros and cons.

  > And you type "xdg-open" while I can just press Enter (or double-click ^^)
Well, it's actually only 'xo' for me, I set up an alias a long time ago. I said "xdg-open" because not everybody has that alias.

  > Why should I constantly want previews of something, so often that I'd care about a second of waiting time once in preparation,
As I've said elsewhere, you don't understand the point and you're fixated on the speed thing. Because you don't understand the point.

  > Couldn't you just leave it open then?! Yeah, you'll definitely have some reasons...
I have a bunch of reasons.

Have you ever left dolphin open for 160+ hours in a directory containing 80,000 mp3s? How'd that work out for you? How did it handle it? How much ram did it use? What was your system load like?

  > Sure you do! I know! Terminology is one of them. That's exactly the point.
...that you don't understand my point and the problems I have with the flow you suggest?

  > For an actual (virtual)terminal, it would at least remotely make some sense to me. Because there it's not an option to just use a common X11/Wayland image viewer.
Again, do you mean "running outside of a graphical environment"? That oh-so-common situation that so many of us deal with on a daily basis in 2026?

Let's say you do mean that: You still have no clue what you're talking about. For instance it's trivially easy to view an image or play a video with no graphical environment running*, as long as you have hardware that can do a framebuffer. Like, for example, every graphics card made in the last 30+ years. And if you have that hardware, then you can run terminology on it, too. As raster already mentioned and you failed to understand.

* (one of my machines is indeed set up to play video 24x7 and does not run a windowing system or graphical environment at all)

  > It's trying to make terminal apps graphical, right? 
Terminology doesn't give a shit what software you run on it. It's non-sentient, you see. It doesn't care either way. It's definitely not trying to convert terminal programs into gui programs, or the other way around, like you seem to think because you haven't bothered to understand what I'm talking about.

If you think it might be, you might want to look into that. Ascribing motivations to inanimate objects seems like it might not be healthy.

  > And all that technical complexity is just there
All what technical complexity? Where is the complexity, exactly? Please be precise and detailed.

You don't know. Because you don't understand how it works, and you've ignored the people who tried to tell you.

  > because you don't have to move your eyes to another window 
You. Do. Not. Understand. My. Point.

Please try re-reading my other responses and this time try to comprehend what I'm saying if you'd like to continue this discussion.

  > there are very basic image viewers without any features
...No features at all, huh? Please provide examples.

So then, you're saying they don't open up a window? They don't decode jpeg?

I question the usefulness of this software. But I can't wait to see your list.

  > I've no idea why they should be slower than the EFL previewers
Then I'd suggest you re-read and this time try to comprehend my detailed explanation in a previous message explaining how they are and always will be fundamentally slower and cannot help but to be so due to how software and physics work.

  >  I'd definitely dislike to see all that arriving in major desktop environments. And I'm still optimistic in that regard
Oh noes! It's already been in KDE and konsole for more than 5 years! I'm so so so so so so so so so so so sad for you! How this must ruin your day and impact very negatively on everything you do in daily life! And the bugs! All those bugs that the shoddy implementation and extreme technical complexity have caused for you! Do you need a hug?

  > If it does, at least there might be ways to integrate the Dolphin thumbnailers. :)
What. the fuck. are you talking about???

Are you saying that you wish lsix[6] existed? And that it worked in konsole? And that you wish you could use it right now with literally 3 seconds of effort to install it? Are you saying that, after typing a hundred thousand words railing against the inclusion of any graphical features in any terminal ever?

  > In some way that's exactly what I'm wondering about when people have terminal-centric workflows in an environment that could actually just do graphics.
Some people value being able to get stuff efficiently. Apparently, you're not one of them.

I love how, after having the massive complexity of gui applications explained to you, you just brush that off and say "just do graphics". That's pretty good trolling right there.

  > In particular when they then start to patch graphics support inside their terminals
For what I really really really really hope is the final time: if you bothered to try to understand the point which I have made to you repeatedly and in several different ways, then you might understand. But that would require more than zero effort on your part, so it's not going to happen.

[1] https://en.wikipedia.org/wiki/Sixel

[2] https://bugs.kde.org/show_bug.cgi?id=391781

[3] https://github.com/hpjansson/chafa/issues/78

[4] https://invisible-island.net/xterm/xterm.log.html#xterm_359

[5] https://man.archlinux.org/man/extra/xscreensaver/phosphor.6....

[6] https://github.com/hackerb9/lsix