Tiny Core Linux
Tiny Core Extensions => TCE Talk => Extension requests => Topic started by: meo on June 05, 2026, 01:51:29 AM
-
This is a hard guy since nobody is maintaining it at present that I know of. But it is a very good programming IDE.
Regards,
meo
-
Which architecture do you want it for?
Edit - ah, it’s based on qt5, which is too bloated for me.
-
Sorry I forgot that. I run piCore on my Raspberry Pi 5. So I was thinking of using it on the piCore Since it's a very good IDE for programming just about in any programming language. Well perhaps not Malbolge! It crashes with some more resent libraries. I used it on Q4 but when I installed zoom it stopped working. It would be great to have.
Regards,
meo
-
For RPi5 I guess you're speaking of piCore64?
Anyway, neither piCore nor piCore64 have qt4/qt5.
-
OK, then I know. Funny that I just saw that it was made available for debian and Raspberry Pi OS. Strange what can occur. Now I can download it to my SSD on the RPi 5. Thanks for checking it out!
Kind Regards,
meo
-
Whow! Notepadqq with dependencies needed over 220 MB to be installed on Raspberry Pi OS. One of the big Guys then, I'm glad that I opted for a SSD.
Greetings,
meo
-
I ask for a friend of mine: what is the purpose to use big/ fat/ bloat extensions (200+ MB) on a "distro" like TC?
I mean TC is focused on CPU=486, + apps. compiled with -O2 (so small but not the faster) + low RAM + maybe HDD (not SSD). The clue is in the NAME -> TINY.
I asked long time ago the TC users to vote / share their devices limitations / type. To understand the attraction/ advantages of small CORE. Because if we talk about IDE (Integrated DEVELOPMENT Environment) then you need fast CPU + huge RAM to compile/ develop in reasonable time, etc.
https://mirrors.dotsrc.org/tinycorelinux/17.x/x86_64/tcz/?C=S&O=D
So for me, to use firefox, (or vivaldi / librewolf) or Libreoffice, dotnet7-sdk.tcz (209 MB), atom.tcz (180MB) -- this is only tcz WITHOUT their dependencies -- is ... "not optimum" to be polite. YMMV.
My naive summary: if you have low resources (CPU/GPU/RAM/HDD) then you are more rewarded to use small apps. Or else, if you are loaded with comfortable resources then ANY distro is OK (some are out-of-the-box ready) for your bloated/ demanding apps.
-
My naive summary: if you have low resources (CPU/GPU/RAM/HDD) then you are more rewarded to use small apps. Or else, if you are loaded with comfortable resources then ANY distro is OK (some are out-of-the-box ready) for your bloated/ demanding apps.
Hi nick65go. There is at least one more scenario: Users who have "comfortable resources" and use demanding applications, but want the underlying OS to be as small, easy to understand, and easy to manage as possible.
I'm a user in the above category. I need some big apps (e.g., Brave, Thunderbird, Libreoffice, Gimp) but the size and complexity of today's mainstream distros is NOT OK as far as I'm concerned.
A lot of big apps run just fine on TCL.
-
There is at least one more scenario: Users who have "comfortable resources" and use demanding applications, but want the underlying OS to be as small, easy to understand, and easy to manage as possible.
I'm a user in the above category. I need some big apps (e.g., Brave, Thunderbird, Libreoffice, Gimp) but the size and complexity of today's mainstream distros is NOT OK as far as I'm concerned.
A lot of big apps run just fine on TCL.
Thanks for your feed-back. I was such a user (chasing for the underlying OS to be small), I did manage to understand it (at some time in the past, job done!). But "easy to manage as possible" became complex when we involve more and more complexity (UEFI, close-source firmware, wayland, pirewire, etc).
Ex1: I mean we just lean about sound in kernel as OSS v3, then come ALSA, then pipe-wire. And all my knowledge become wasted.
Ex2: just learn to tweak up Xorg server + drivers, then Wayland types come and we need Xwayland etc.
Ex3: small/ effective drivers for sound/gpu/wifi/bluetooth, but now they need firmware.
I could go on and on. So today easy to manage is "integrated tools" (instead of shell scripts). Ex: In KDE the burden is on developers and me/user just use them. It comes a time when you just want to enjoy driving a car, not daily repair it.
But today my biggest concern is the fast step (temporary for maybe 1 year peak) of A.I. discovering bugs (some intentional by national agencies) in kernels + drivers etc. And fast/prompt corrections involve a big team of developers, so the bet is (temporary) on big distro clean-up their shit, then followed by small /passionate distro.