Read the statement by Michael Teeuw here.
CALL FOR TESTERS: New install script
-
@karsten13 Sorry, that didn’t come out right. I meant the first paragraph for you and the rest for everyone. Should have made that clearer, my apologies.
-
@drdeath I applaud you for the effort and time you put into this. I was just explaining what the encoding meant and how the others could go about decoding it. I have a fully setup system and my own dev environment and probably would not be able to test your script. My apologies for that. But again, good work and nice effort.
P/s - do not take offence to the community. We are all dev’s around the table and we try and assist to make things better where we can.
-
S sdetweil moved this topic from Upcoming Features on
-
@drdeath can you provide user guidance on choosing your solution vs the others available
-
@mumblebaj Thank you for your kind words. You can’t imagine how much I needed that right now - for at least one person to actually say “thank you”.
On the subject of the “standard user’s” reaction, I guess this is another occasion to break out my favorite corollary to a corollary to the famous statement of Arthur C. Clarke: “Everything looks like magic to those who don’t understand it”. Whether you condemn it as evil magic or marvel at the wonderful magic however depends entirely on your own personal disposition.
Personally I tend towards the opinion that these days users are totally used to making use of tools they don’t understand but know how to work. If you for instance went into a dark room and asked “How’s the light work?” you would much more likely get pointed to the light switch than an explanation of the function of the power grid. There would certainly be a few die-hard sceptics who refuse to use it on the grounds of “I don’t understand it, hell no” - to then complain about it on the forums they don’t understand either using their smartphone they understand even less, the irony - but most users would probably not look at it at all, or if they did, just shrug and run it anyways.
That however goes for end users, it certainly does not go for reviewers. Someone should definitely understand the code, and I would never hold it against anyone who doesn’t if they decided to wait until those who understand it better give their blessing.
What I will hold against people though is the attitude to condemn a thing merely because they don’t understand it and can’t be bothered to learn. That sort of thing gets right up my nose.
-
@sdetweil I most certainly can and will. Where would you like it to live? I’d suggest the README in the repo.
In a nutshell, if you want a reduced footprint in cpu, ram and memory usage and/or want your magic mirror system to be more of an embedded-appliance style rather than a general use computer running an application, then my script is right for you.
By the way, I just thought I should probably add the option to enable automatic system updates via apt as a logical extension of that concept.
What do you think? Should I include it now or when I get around to re-creating automatic updates for MagicMirror and its modules?
-
@drdeath we’ve had lots of successful appliances built so far without your approach.
and the user issues are mostly unrelated to the os or MagicMirror runtime.look and feel, consistency of error recovery
and module function/integration are the primary issues. power saving , new monitor hardware are the next most.and user skill is always a critical issue. we have a lot of new users that know nothing without a graphical desktop . cant find help, don’t know file commands, cd? redirects, copy, move, networking
and on and on.what can the user save by using your approach?
note that the older pis are going by the wayside with the os changes. pi4 and 5 class devices are the norm across sll the vendors
can they do without a fan?
functionally nothing else changesi am not in favor of automatic updates in this space, the amount of breaking changes are too high. we still have significant disruption of the existing user base on each release
some OS related (tools used for blanking the screen or video feeds dropped out or function limited), some deprecation limited (remove request and other libs no longer supported), new versions of electron taking new code with bugs not yet discovered which cause fatal errors for the user . new electron requires, new node version, which doesn’t run on this os… oops… but discovered too late
some MM related… the deprecated lib thing… we don’t want to carry dead baggage… oops authors didn’t know, we added checking for things to prevent crashes (good thing) which cause accidental side effects
position: “” used to work, now fails. -
@sdetweil Well if you put it this way, the less software you have installed on a system, the less likely it is going to break during an update. That could actually be a major selling point for doing it my way, because almost all of the tools I’m using have been around for at least 30 years and are going nowhere. Desktop environments have big breaking changes all the time (I’ve been there when they swapped out KDE3 for KDE4 in SuSE Linux over night, boy were people enraged) whereas the basic toolset I rely on has stood the test of time and is virtually unchanged save for the occasional bugfix since the mid 90s.
On the subject of how the users interact, I’ve said so here multiple times and I’ve also put it in the README that this script isn’t written with the wet-behind-the-ears noob at the forefront of the brain. That being said, it’s actually really hands-off and easy to use when you think about it. Download it, start it, answer a couple of questions, bam, you’ve got a working mirror. The major concern I have with the current script is actually that may be too easy to use, prompting people to treat their mirror like a maintenance-free washing machine and let the system rot.
-
@drdeath interesting, but there is no less software.
curl, git, node, MagicMirror and all its dependencies .
whatever window manager is noise, there is one
there are a few users like you that want to be near the bare minimum, i don’t think that’s the right place for 99% of our users. they are still exploring the possibilities.
-
@sdetweil I beg to differ, yes less software, because the whole thing is based on the lite image, not the full image, with all the packages not installed and daemons not running there’s actually a pretty significant reduction in installed software and services. Actually, I consider the possibility to work on the lite image a significant advantage of my script over other installation methods.
curl, git, node and MagicMirror are pretty much a given, since omitting any of these would pretty much defeat the purpose of the whole thing.
About “noise”, you lost me there. There is no package or binary called “noise” installed on my test system, and since I know pretty much all of the common mainstream window managers and quite a few obscure ones at the very least by name, “noise” would either have to be pretty new or a quite obscure one. If you doubt my admittedly boastful claim, kindly research “sithwm”, evilwm and xmonad. I’ve actually used all of those at some point, if only for evaluation purposes
The script in itself neither installs nor sets up any window manager at all. Xserver-xorg-common, which is pretty much the only suspect, doesn’t even contain or depend on any. I can definitely say it’s not a dependency or part of any of the packages my script installs. If you could tell me where you found that information, I might be able to shed some light on the issue.
PS: Found it. /usr/bin/noise is part of the openfoam package. My script definitely didn’t install that one.
-
@drdeath noise in this context meant insignificant to the problem at hand
