51–60 of 167 posts
The post title is misleading. This is a more of 20% project, not an officially Google supported one.
There's no difference.
The title certainly made me think that it was the former, even though it's the latter.
Earlier quoted context omitted.
I do not think Google figured anything better than BCL. Disclaimer: Was owner of borgcfg 2016-2019.
We still haven't. :(
GCL, used outside borg, is a much more pleasing experience, because there is a decent tool. And the team have done good job to innovate continuously.
The tl;dr is buried deep in the docs > CUE is an extension of JSON. This improves familiarity and makes it easy to get going quickly. > In its simplest use case, CUE can substitute for a more pleasant way to write JSON.
So it’s a google branded yaml? Let’s raise a glass to our blue eyed comrades who’ll adopt this fully, only for google to decide in 2-3 years to completely and aggressively kill it again for no apparent reason.
Earlier quoted context omitted.
There's no difference.
There is a large difference between battle-tested tech maintained by a properly staffed team and a proof of concept built by someone in their spare time. The title certainly made me think that it was the former, even though it's the latter.
This seems to describe very few Google products. Almost daily, I have the following thought: "Has anyone at Google actually even used this product?"
(Most often with Assistant, but definitely with other products, too)
A new configuration language. Yes. That's exactly what we need.
We do indeed. XML is awful, YAML is a clusterfuck, JSON is often insufficient, and so is INI. TOML looks promising, but might not make it out of its niche. If Cue is basically a better YAML with built-in schemas, that sounds pretty good.
And that seemed to be the most mature TOML parser that I could find for Python, so I decided TOML isn’t likely in my future.
my time at Google has made me hate GCL so much.
Weird flex, but ok. Is it true that there are dozens of internal language and DSLs? Why does G have so many?
2. find a use case where you want a config with ~700 lines, most of it just a repeated variant of something
3. add more fields to your config to reduce the verbosity
4. realize that your configs are now obscenely complex, and build a limited-purpose DSL
5. five teams now use your limited-purpose DSL and make more feature requests
6. cry because you now maintain a DSL
7. ???
8. promo for cross-team impact
Seems like an interesting language, but I'm very disappointed that my first attempt to view example code took 5 clicks. The most important part of any programming language website is a short example snippet: put it above the fold on the front page!