Hacker News new | ask | show | jobs
by ajross 992 days ago
> - "Switch to dev mode". But I don't want to be prompted to factory reset each boot.

Developer mode simply puts up a splash at boot warning you that the OS is custom, you just press enter to boot. The requirement to do a drive wipe is a one-time thing when you enable it the first time (for obvious reasons, to prevent exfiltration of data stored by a secured OS).

1 comments

Thanks - has this changed in the past few years?

A few years back (when I last looked in depth), it was very easy at every boot (not only first boot) to accidentally wipe everything - e.g., https://www.reddit.com/r/Crouton/comments/3be2su/reducing_ri...

I also remember that it made a loud beep on every boot!

I used a Chromebook as my main laptop for a year in college, and I always had to apologize to nearby strangers for the beep.

(CS major, coding happened mostly over SSH to the school servers, but I did run RStudio locally)

How often does one reboot their laptop around nearby strangers? I gotta be honest that some of these criticisms seem a little strained. I mean, it's true, they beep at boot when dev mode is enabled!
I shut all of my computers all the way off when I’m finished using them, which means I have to turn them on when I start using them.
Is this an adaptation to some past trauma? I can't imagine a good reason to do this today, certainly not with ChromeOS.
I don't think it's trauma, although I've been burned with suspend/wake cycles before. Suspend works great. It is usually that wake part if it's going to go wrong.

If I close the lid, when I get back _I_ need a clean slate. I'll never remember what I was doing anyway.

Modern machines boot and launch apps so fast I'm not really saving any time sleeping an empty desktop either.

I used a Samsung Chromebook sometime 5 years ago, and it couldn’t handle suspend/sleep well. I could leave it overnight with 80% and find it with 0% in the morning. So I learned to turn it off each time I stop using it. It booted within seconds anyways, so the only issue was to enter my gigantic generated password.

For me ChromeOS’s top UX fault is the password. You either do it with pin, or with a Bluetooth device to unlock. Otherwise it’s pain to enter the password.

When talking about other OS, you might want to turn it off if you have your disk encrypted. So it serves its purpose.
Isnt suspending an adaptation to trauma? The trauma of slow drives/startup or being interrupted constantly?

When I put my machine e away I am usually 'done', and when I open it, it isn't to see where I left off.

It’s been awhile and I don’t remember why I had to reboot, but it did happen. I guess past me did a lot of work in cafes, office hours, and common areas.

I do remember that running a certain R program consistently caused the Chromebook to turn off, which was quite an issue for one particular office hours session!

The key combo you use to get into dev mode, ctrl+D, will exit the warning screen before it beeps.