It has been that way for a while now. I see Veritasium video titles and thumbnails change quite often, it can be quite annoying as it sometimes gives the appearance of it being a whole new video.
A/B testing a title feels wrong to me, its almost as bad as A/B testing a UUID.
Just pick a title and stick to it unless you need to fix a factual error.
Right, but then there's this thing called "shared reality" and once you break it, all kinds of bad consequences happen.
This is even worse, as it also breaks temporal continuity for individual reality. E.g. I expect that if I saw a video titled X today, I'll be able to find it under title X tomorrow, and if I can't, it's one of the rare/marginal cases when it got banned/deleted/retitled, or I just misremembered. Titles becoming unstable in the general case is a bad situation.
it seems to me like the acceptance of breaking changes by the Zig community is more coming from "it's worth it to get a nice, polished language" than some "source of pride" which i personally have not seen in my time in a/the Zig discord server.
what is the problem with zig being developed for 10+ years? if people want stable languages there are stable languages to be used. if a language like zig is not achievable in less than 10 years, should it just not be developed from the start?
i think your problems with build.zig are overstated. where do you see someone saying "to build your first Hello World, first understand this build script in non-trivial Zig"? you can literally just do `zig run file.zig`, so if someone is advocating for that then i think many would agree they are teaching the wrong way. i wonder if you saw an example project with a build script that was intended to show the power and possibilities of Zig rather than to be a starter guide.
files aren't converted to structs on import, they _are_ structs (well, their contents are the inside of a struct declaration). also, public members don't become comptime fields? file structs are basically left as-is on import, nearly like you copy&pasted the file contents into a struct declaration
you have to go into your Privacy & Security settings and scroll down until you see something like "Posturr.app was blocked to protect your Mac." and then press "Open Anyway"
What's interesting is that the scope of the proposal isn't a Zig-specific ABI, but a codified way of expressing certain Zig concepts using the existing C ABI.
reply