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?
Only 40%? Would have thought it would be much higher. Don't more projects generally fail then that without being in a bubble?
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.
I don't agree go is simpler to read. It is simpler to learn the syntax but the syntax is only part of what makes a language. Having learnt both, and having spent more time actually writing go I still prefer writing rust and finding it far easier to work with then go. Go has too many hidden gotchas that you need to trip up on to learn and then remember forever or else trip up on them again.
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.
Well, that is the first option they suggest:
Option 1: Give Linux Mint a try
Wasn't this the fork created by the guy that got banned from X development because they were causing a large amount of churn that kept introducing breaking changes and regressions?
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.
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.