I think that's the key, what's bloatware to one isn't to another. There are features I consider to be useless, for example the ability to store photo's with the dive log. That's bloatware to me as is the Dive Op's name, Captain, etc. That's what the memo field is for. Look at a real paper logbook and then look at this program. Things not in the paper log are bloatware.
However, some people find those extra's useful and want them so there they are. It's a computer program, it doesn't slow down because you added a feature. With memory being so cheap, large hard drives being so cheap, a few more megs of size are not an issue either. So add the features that users want, it won't slow down the program because only a routine executed during the function will slow down a program. So, if you click add a dive then the PDE feature doesn't slow down the computer because that routine wasn't called.
I don't care how much bloatware is there as long as the program does what I want it to. So far, it's still broken when it comes to temperature logging and I'd like that fixed. My lowest temperature which is recorded in the dive log is not listed in the temp section. I want that fixed. I can't print the lifetime dive number on the log page printout, I want that fixed. I can't easily export my dive log to DAN, I want that fixed.
However, it's a dive program that honestly isn't even needed. Paper does just fine. I like bells and whistles, so I use this program.
IMO there has been no logical well thought out reason presented not to include the things I want added or fixed. For the TWO who don't want it, tell me why? Tell me what the addition of the items I want will do to impact the computer programs operation? The implementation of what I want won't even add a megabyte of code to the executables size. It's all there already, it just needs another sort and email routine added. Very little extra coding would be needed. The button needed to export it wouldn't take up valuable real estate either, there's room on the dive log page for a button.
Tell me what negative impact would result? I am experienced in a few computer languages and I do know of which I am speaking when it comes to program operation. I have a foundation upon which I am speaking because I can design and implement computer programs. Based on my background I say it will have no negative impact.
To be rational, tell me why based on your background it's an unreasonable request for Version 3 to add a couple features.