Has probably been forgotten by Australia and everywhere else though.
1,226 karma · joined September 3, 2018
Has probably been forgotten by Australia and everywhere else though.
- Lots of text seems slightly offset. It's not all centered within buttons etc.
- The text also doesn't seem to quite line up with the icon on said buttons (it feels relatively a little too high)
- Similarly the text within the little notification popups ("New") isn't centered and hits the top of the outline
- The colours have poor contrast. I don't have any vision impairment but the peach colour doesn't feel distinct enough from the purple/lavender to me. (It's better in light mode when the peach turns to a stronger red).
- On that note, maybe yellow was not the best background for the beer badge when most of the glass is yellow with a bit of white.
I don't know if there's something that makes this render any differently for me than anyone else. I'm using Chrome though so I wouldn't have thought it'd be especially unusual.
The only real difference there (although it is a significant one) is that most of those internal Google tools tended to be very good, often ahead of the external state-of-the-art. That's a very different feeling to a baroque old stack inside a bank somewhere. Maybe the external world has caught up on a bunch of them more recently though which would start to change that.
I've rolled with the "we'll keep a local patch against upstream" for small changes before, which helps keep on track with upgrades, but depends how feasible that is.
The Lovecraftian vibe could have been cool but it doesn't really come through in the game in the way the satanic / hell thing did in Doom.
Honestly I think Doom is where it came together the best, Quake was technically better (of course) but it was not a better game.
The wood barely moves after it's split. If you split it perfectly, the two halves will almost certainly both fall to each side (they're pushed outwards by the axe).
You can't just randomly split it across the grain into slices like you're slicing bread.
I guess mostly: it's not tiring, which sort of sucks when you're doing it for real, but it is satisfying. This doesn't scratch that itch for me, but I guess it's fun in a way, similar to that cleaning simulator thing.
Also the context menus are super noisy, I tried cutting some bits out in config, but there's just so much crap in there. Obviously all the AI stuff, but also just the basics; right-clicking on a tab has a sub-menu for "Close Multiple Tabs" which hides "Close other tabs" and "Close tabs to the right" which are probably what I use the most. In Chromium they're top-level menu items.
And it went through a phase a few months ago where the context menus were sometimes offset or goofily sized; I think that's fixed now.
I guess it's easy to criticise, but it just doesn't feel like this stuff is well aligned to actually using the browser, whereas Chromium feels like a solid product.
I think that's financially sensible in the long run, assuming they believe they can run the thing basically as well on Azure, and aren't expecting major issues during the migration. These have turned out not to be good assumptions.
And I do still think there is an advantage for this kind of tooling to choose languages that are designed to compile to a native binary. At best Java and C# are equivalent to Go and Rust here, maybe they are less "cool" but I don't see any reason why this rewrite would be better if it were to Java than Rust.
I'm not sad to see the pendulum swing away from "javascript everywhere" though.
I feel like we're using about 1% of its features at this point - really just as a fast K/V store - so it would be easy to switch if needed, but I can't see a case where we would.
Debatable how much they have been "right", although this gets them somewhat closer. And I think they have not been "wrong" in the ways they wanted to avoid (they referenced some issues with Java generics as prior art, although I forget the details).
What would have been significantly better is just rewriting Claude in a language that's actually well suited to what it's doing in the first place (which could well be Rust, Codex is written in it as prior art). It's funny how the vibe coding promoters are keen on things like this, rewriting other codebases as fast as possible with little quality checking, but they are still defensive of their own code.
I suppose Go programs are slower than the equivalent thing in C or C++, but I'm not sure that's a very relevant comparison in most cases today (how many new things being written would choose those languages).