Yeah I don’t like this either. So many chances for a mistake, be in the wrong dir, file misspelled, something not cloned correctly or anything else not setup as you think it might be and suddenly the package manage does something you don’t expect (like try to install globally rather then in a project or vice versa).

For a lot of things I would rather have something web based than app based. I hate having to download some random app from some random company just to interact with something one time. Why do all restaurants, car parking places etc require apps rather than just having a simple site. Not everything should be native first IMO.

If the package is popular then it is very likely already packaged by your distro. You should always go there first if you care that much. If the package is not popular enough to be packaged by a distro then how does another centralized approach help? Either it is fully curated like a distro package list and likely also wont contain some random small project, or it is open for anyone to upload scripts to so will become vulnerable to malicious scripts. Worst yet people would be able to upload scripts to projects they don’t control as the developers of said project likely wont.

Basically it is not really any safer then separate dev owned websites if open nor offer better package support then distro repos if curated.

Maybe the server was hacked and the script was changed?

Same thing can happen to any system though. What happens if your servers for this service are hacked? Being a central point makes you a bigger target and with more people able to change (assuming you are not going to be the only one to curate packages) things you have a bigger area of attack. And once hacked they can compromise far more downloads than a single package.

Your solution does not improve security - just shuffles it around a bit. Sounds nice on paper but when you look at it in more details there are a lot more things you need to consider to create an actually secure system that is better then what we currently have.

Then how would you trust these scripts in a central repo? Seems to add no real value or safety over dev managed scripts if you are not willing to go down the path of becoming yet another distro packaging system.

There is also no way to verify that the software that is being installed is not going to do anything bad. If you trust the software then why not trust the installation scripts by the same authors? What would a third party location bring to improve security?

And generally what you are describing is a software repo, you know the one that comes with your distro.

Random programming certificates are generally worthless. The course to get them might teach you a lot and be worth while, but the certificate at the end is worthless. If it is free then it does not matter too much either way, might be a good way to test yourself. But I would not rely on it to get you a job at all. For that you need other ways to prove you can do the job - typically with the ability to talk about stuff and having written some real world like application. Which a course might help you do to.

YAML is not a good format for this. But any line based or steamable format would be good enough for log data like this. Really easy to parse with any language or even directly with shell scripts. No need to even know SQL, any text processing would work fine.

CSV would be fine. The big problem with the data as presented is it is a YAML list, so needs the whole file to be read into memory and decoded before you get and values out of it. Any line based encoding would be vastly better and allow line based processing to be done. CSV, json objects encoded into a single line, some other streaming binary format. Does not make much difference overall as long as it is line based or at least streamable.

Never said it had to be a text file. There are many binary serialization formats that could be used. But is a lot of situations the overhead you save is not worth the debugging effort of working with binary data. For something like this that is likely not going to be more then a GB or so, probably much less it really does not matter that much if you use binary or text formats. This is an export format that will likely just have one batch processing layer on. This type of thing is generally easiest for more people to work with in a plain text format. If you really need efficient querying of the data then it is trivial and quick to load it into a DB of your choice rather then being stuck with sqlite.

export tracking data to analyze later on

That is essentially log data or essentially equivalent. Log data does not have to be human readable, it is just a series of events that happen over time. Most log data, even what you would think of as traditional messages from a program, is not parsed by humans manually but analyzed by code later on. It is really not that hard to slow to process log data line by line. I have done this with TB of data before which does require a lot more effort to do. A simple file like this would take seconds to process at most, even if you were not very efficient about it. I also never said it needed to be stored as text, just a simple file is enough - no need for a full database. That file could be binary if you really need it to be but text serialization would also be good enough. Most of the web world is processed via text serialization.

The biggest problem with yaml like in OP is the need to decode the whole file at once since it is a single list. Line by line processing would be a lot easier to work with. But even then if it is only a few 100 MBs loading it all in memory once and analyzing it all in memory would not take long at all - it just does not scale very well.

What is wrong with a file for this? Sounds more like a local log or debug output that a single thread in a single process would be creating. A file is fine for high volume append only data like this. The only big issue is the format of that data.

What benefit would a database bring here?

The attack is known as the evil maid attack. It requires repeated access to the device. Basically if you can compromise the bootloader you can inject a keylogger to sniff out the encryption key the next time someone unlocks the device. This is what secure boot is meant to help protect against (though I believe that has also been compromised as well).

But realistically very few people need to worry about that type of attack. Encryption is good enough for most people. And if you don’t have your system encrypted then it does not matter what bootloader you use as anyone can boot any live usb to read your data.

On their readme

Harper currently only supports English, but the core is extensible to support other languages, so we welcome contributions that allow for other language support.

It does not matter if the battery is plugged in or not. Far more important is the state of the battery. All LiPo batteries degrade over time. But they can degrade faster or slower depending on the state they are stored in. They degrade faster when at higher charge levels or when stored in hotter environments or if they go through more charge/discharge cycles. Older battery technology also degraded faster in general, new ones tend to last longer in sub-optimal conditions.

Apart from newer battery technology itself battery monitoring and charging technology has also improved. A lot of modern laptops have smarter charging circuitry that lets them stop charging before the battery is at 100%, sometimes configurable in the bios, sometimes controllable via the OS. This can help a lot to preserve the battery life for longer, especially if you leave it plugged in as it spends less time at 100% charge. Older devices also tended to run hotter for longer periods of time, even when idle. Both of these combined with worst battery technology would lead to batteries degrading quite a lot faster if you left them plugged in all the time - hence where the advice came from (note that removing the battery at 100% charge was also not great for it, better to store lipo batteries at 40-60% charge, but it did still save it from the heat of the device) . But when setup correctly modern devices suffer from this a lot less so it is much less important to remove the battery at all - I doubt you would really notice the difference overall on modern systems.

will charge the battery and then start running directly from the wall-power once the battery is full. They bypass the charging once it is indicated to have a “full charge”.

That does not make sense. Batteries cannot be charged and discharged at the same time - they are either charging or discharging or neither. When a device is in use while it is plugged in the device is being run directly from wall power - and anything left if sent to charge the battery. The only devices that don’t do that is ones that power off while the charger is plugged in - which does not include any laptop that I have ever seen, generally just smaller devices.

Modern laptops have smarter controllers that can turn off charging before the battery is full or when other conditions are met. But none are able to draw power from the battery while the battery is being charged - that just does not make any sense.

Huh? If it can be used while it is charging - which is all laptops since forever - then it will run off the adapter while plugged in. Regardless of the battery state. You cannot charge a battery and discharge it at the same time - if it is charging then power must be coming from anything other then the battery. Epically with LiPo batteries which you cannot continue charging after they are full - doing so will cause them to burst into flames. So all LiPo charging circuits will cut off power to the cells once they reach a desired voltage - weather that is considered 100% (aka once it reaches 4.2V) or at a configurable lower amount.

You don’t need anywhere near 50% market share to be a valid alternative. If anything market share has nothing to do with it being a valid alternative except that it more likely to be the case with higher numbers. Past 50% it is really no longer even the alternative at all - it would be the main choice.

Every OS has paper cuts. You learn to live with them over time as you have no other choice. When you switch OS it cuts in different ways and they feel fresher then the old ones you had gotten used to over time. It does not matter if you switch from Windows to Linux, Linux to Windows or to or from MacOS. They all have papercuts.

I said editor, not an OS that lacks a decent editor :)

What editor is more feature-rich then vim? Out the box it is lacking some sane config but it is one of the more powerful and flexible editors out there - more then a rival for any modern IDE.