Why the fuck doesn't the GTK file picker support motherfucking thumbnails yet? Linux is literally 20 years behind
>gtk
>>60021603
It does support thumbnails, just not icons.
>>60021603
this was worth a thread wasnt it you bellend
>It's free. Just fix it yourself!
>>60021603
Why the fuck doesn't Windows file manager support motherfucking ad blocker yet? Windows is literally 20 years behind.
>>60023189
>muh 5th amd vs nvidia thread died uwaah
I literally confirmed this last night it works with thumbnails, numbnuts.
>>60023292
is that real ??
>>60023218
they've refused such patches several times
>>60023436
Why? Are they microshaft saboteurs on duty to forever keep linux inferior?
>>60021603
>How to spot a memelord, the post.
>>60023467
pretty much
>>60023430
Yes
>>60021603
EBIC MAYMAY XDD!!!1!
>>60021603
Linuxfag here, let me give you the most proper and shameless explanation. I hope you will understand.
>Why are there no thumbnail in file explorer
Because it's written in C. The file chooser widget is written in GTK+, which is one of the most popular C's GUI library. People know about this already.
>Why hasn't this been fixed
As a software developer, I would not touch obsolete POS language such as C, let alone GTK.
For me, it's easier to develop something else rather than fucking with obsolete featureless languagelet like C(ancer). Using C for anything but micro controllers and kernels is pants on head retarded, specially GUI. GUI is MEANT for Object Oriented Programming and C doesn't have that level of sophistication. Developing in C is literally a worthless timesink because C does not have anything to offer but timesink: C has no templates, operator overloading, exception handling, type checks, runtime checks, constructors, lazy evaluations, monads and the list goes on. If you are not hacking the very language itself with macros shitting all over the source files you wouldn't trivial things such as get function overloading.
C does not have exception handling. It's meant for 80's computing and the projects that are written in C are unironically stuck in the 80's: like GTK+
Even after you have gone through the agony of using a language that is a disservice to the intelligent programmers (Linus doesn't count, he's on a different level and not everyone is Linus), you have to worry about memory safety.
C is not memory safe. As if the timesink development was not enough pain, you have to test your program for possible security vulnerability. When K&R came up with C, it was an ancient time. C's priority was being able to produce binaries that can run in an 800MHz processor with 64MiB RAM that can fit into floppies. Security was NOT a concern.
Coincidentally, KDE file chooser has thumbnails and guess what language it's written in: it's C++.
Ban C
>>60023582
>"maymay"
kill yourself
a lot of browers on arch have preview patched into the filepicker