Google Chrome and Multiple Profiles
Google Chrome has always supported multiple profiles, but you had to use a command-line flag (—user-data-dir="c:\path\to\the\p rofile") to associate a profile with a folder where the browser will save its state. — At some point, Google added an option …
Context & Ripple Effects
The move slots directly into the framing of the New York Times' piece from the day before, which described Google's bet on the browser doing everything an operating system once did. Until this week, splitting Chrome into separate user environments meant hand-editing a --user-data-dir launch flag — power-user territory that kept the feature effectively hidden.
First-order effects
- Anyone sharing a computer — family members, coworkers at a shared desk — can now create and switch isolated browsing profiles (bookmarks, history, saved state) from within Chrome's own interface instead of maintaining custom shortcuts with command-line flags.
Second-order effects
- Profiles give Google a native hook for per-profile sign-in and synchronization inside the browser, pulling account management down from the operating system level into Chrome itself — useful groundwork if the rumored Chrome OS netbooks, still unconfirmed by Google, ship as reported.
Third-order effects
- If the pattern holds, the browser becomes the de facto identity boundary for shared machines, with multi-user support migrating from the desktop OS into whatever application fronts the web — a structural shift in who owns the login screen.
The trend: Chrome is steadily absorbing operating-system responsibilities — windowing, apps, and now user accounts — as part of Google's broader push to make the browser the computing environment itself.