Earlier quoted context omitted.
Theoretically, secure boot could help prevent bootkits (e.g. the "evil maid" attack). Although I have no idea whether this works in practice.
It does, if the stars align. The default setup of these computers (no full-disk encryption, easy to disable secure boot) typically means that it offers no such security. Look at Chromebook for an example of apparently doing it right.
It wipes your hard disk if you enable developer mode(which is a painful process in itself). And then at every single boot you either have to wait thirty seconds to go past a very scary warning or press Ctrl-D. Every single time you boot. If you switch back to ChromeOS, the hard disk is wiped again.
I would love to see HN commenters' reactions if on disabling Secure Boot, the Windows 8 partition is wiped along with any documents and files you saved locally and if you wanted Windows 8 back, it wiped your Linux partition in the name of security.