Wow, you really have no understanding of how this technology works. Even if a rapper were to have 3 second segments on an audio track, it sill has to be pressed in a linear fashion. Also, stop/start has no impact on the data of disks, since there is no physical contact with the data portion of the disk in any way. It's simply a laser that scans the surface.
Oh, yeah... I know:
Shit, piss, fuck, cunt, cocksucker, motherfucker tits.
RIP Carlin, we need you now more than ever.
LedgerSMB began as a fork from SQL-Ledger by developers who were unhappy with the security of that codebase.
The last year has seen 3 major releases and 21 minor ones. The major releases have added better Point of Sale support, local sales tax support, and many other features, and have also included structural security enhancements. The minor releases have continued to address security issues as well as other bugs in the software. Every major release to date has had at least moderate structural security enhancements, and we expect the next major release (1.3) to be the final release in that trend.
When 1.3.0 is released, we expect it to finally create a stable and robust security architecture. Additionally, the contact management portions of the application will be re-engineered and rewritten on the new architecture. This framework is designed to allow people to write applications in other languages which integrate with the application using any of a number of options (from database stored procedures to web services). 1.3.0 is close to feature freeze at the moment.
Following 1.3.0, we expect to move all the rest of the financial logic over to the new framework. Following that, we will implement any additional outstanding areas into the mew framework. clean it up, and address user interface and workflow issues."
Link to Original Source
Could it be that the recent fork of LedgerSMB was too popular for the author of SQL-Ledger?