Why this constraint is more common than the industry admits
Music software marketing assumes a machine you own and control, running Windows or macOS, with enough disk for a library and enough authority to install a driver. An enormous number of people who want to make music have none of that. They have a school-issued Chromebook, or a work laptop with a locked policy, or a six-year-old desktop shared with a family. The tools built for the assumed machine simply do not run for them, and the usual advice - "just get a free DAW" - misses the point completely, because free is not the obstacle. Permission is.
The browser is not a compromise here, it is the platform
On a Chromebook there is no desktop DAW to compromise against. The Web Audio API is the audio engine, and it is a real one: oscillators, filters, convolution reverb and dynamics running in native code, scheduled sample-accurately. The instruments are not scaled-down versions of desktop products, they were built for this. What that actually feels like is covered on the Chromebook page, and the engineering on the browser-based DAW page.
The one thing to be careful about
Nothing in a browser works offline, and nothing hosted by someone else is permanently yours. Export stems and MIDI at every milestone - not because this platform is going anywhere, but because that is the only habit that makes any hosted tool safe to depend on. It costs thirty seconds and it is the single most useful thing in this article.