> It starts with child abuse material, because who’s going to defend not catching that?
After the recent X CSAM generation arguments and the potential for X to get blocked in the UK, it seems like more people than I expected will defend it.
There were people on HN defending it. Although I'm sure they're 99% defending Musk, and only because they reflexively jump into defense mode any time one of his companies' wrongdoing is discussed. If it were Adobe's or Microsoft's products generating CSAM, you wouldn't hear a peep out of them
I will defend absolute freedom of all speech by Musk and against Musk. By Adobe and against Adobe. My Microsoft and against Microsoft. By you and against you. By me and against me. Unlike many who merely theorize about this from their armchairs, I've lived in a place without free speech and I know what that leads to, how fast, and how hard it is to get out of that hole. There is no such thing as "let's just have a little less freedom of speech". It either exists or very quickly it does not.
Should it be legal to (1) create and (2) distribute an AI generated sexual image of a (1) 18 year old, (2) 12 year old? (In both cases without their consent.)
Unbelievable. People pretending not to understand something stated very clearly just to insult someone they don’t even know. Is this where society is now?
>>> If it were Adobe's or Microsoft's products generating CSAM, you wouldn't hear a peep out of them
>> I will defend absolute freedom of all speech by Musk [...] By Adobe [...] [B]y Microsoft
Your support of the "absolute freedom" of "all speech" is very clear. If you somehow didn't mean the words you chose, then the lack of clarity is on you, and needs no pretense on my part.
X installs went UP the in UK when the gov said "X allows you to generate child porn, lets block it". Thousands of brits go "free child porn on X better check it out"
Depends on the shareholder. At Sergey Brin's level, that shareholder value shapes the future of humanity, a legacy affecting many more people and will last far longer than spending time with single, or even double digit number of children.
I can't really tell what you're trying to say, do you really think the shareholder value of Google is positively aligned with the future of humanity?
As in: If Google builds a really good AI and makes a lot of money from that, this will be a net positive for the world?
My nontechnical wife isn't going to care it's a single binary when I remove the PiHole web interface that she's used to using on the odd occasion she needs to disable blocked for a bit (for example).
When I got started it was much more difficult as you had to do a lot of manual work to get things started, and you really had to believe the promises that CUE offered (which I did...), but nowadays they've made so many steps in the right direction that getting something going is far quicker!
Maybe it’s just me, but these sample workflows don’t look less complicated, just another kind of complex? If you’re already heavily using CUE in your project this lateral complexity shift might make sense, but I don’t see why I would start using it…
Like my guy 'diarrhea' already echoed: using CUE absolutely does not make sense at a small scale; just write your YAML and get on with your day. We were using it to generate dozens upon dozens of GitHub Actions workflows from what was essentially a single source of truth, and because CUE can export to JSON too then that single source of truth could then easily be leveraged to provide other input files to be used elsewhere.
To some extent yes. If all you have is 2 GitHub Actions YAML files you are not going to reap massive benefits.
I'm a big fan of CUE myself. The benefits compound as you need to output more and more artifacts (= YAML config). Think of several k8s manifests, several GitHub Actions files, e.g. for building across several combinations of OSes, settings, etc.
CUE strikes a really nice balance between being primarily data description and not a Turing-complete language (e.g. cdk8s can get arbitrarily complex and abstract), reducing boilerplate (having you spell out the common bits once only, and each non-commit bit once only) and being type-safe (validation at build/export time, with native import of Go types, JSON schema and more).
They recently added an LSP which helps close the gap to other ecosystems. For example, cdk8s being TS means it naturally has fantastic IDE support, which CUE has been lacking in. CUE error messages can also be very verbose and unhelpful.
At work, we generate a couple thousand lines of k8s YAML from ~0.1x of that in CUE. The CUE is commented liberally, and validation imported from native k8s types, and sprinkled in where needed otherwise (e.g. we know for our application the FOO setting needs to be between 5 and 10). The generated YAML is clean, without any indentation and quoting worries. We also generate YAML-in-YAML, i.e. our application takes YAML config, which itself is in an outer k8s YAML ConfigMap. YAML-in-YAML is normally an enormous pain and easy to get wrong. In CUE it's just `yaml.Marshal`.
You get a lot of benefit for a comparatively simple mental model: all your CUE files form just one large document, and for export to YAML it's merged. Any conflicting values and any missing values fail the export. That's it. The mental model of e.g. cdk8s is massively more complex and has unbounded potential for abstraction footguns (being TypeScript). Not to mention CUE is Go and shipped as a single binary; the CUE v0.15.0 you use today will still compile and work 10 years from now.
You can start very simple, with CUE looking not unlike JSON, and add CUE-specific bits from there. You can always rip out the CUE and just keep the generated YAML, or replace CUE with e.g. cdk8s. It's not a one-way door.
The cherry on top are CUE scripts/tasks. In our case we use a CUE script to split the one-large-document (10s of thousands of lines) into separate files, according to some criteria. This is all defined in CUE as well, meaning I can write ~40 lines of CUE (this has a bit of a learning curve) instead of ~200 lines of cursed, buggy bash.
reply