Zambyte

In all seriousness, this seems like it could be fine if done well. You can just have a model do a pass over the system prompt and set reasonable parameters based on that. That's probably not what they're doing, but it could be.

The shorter the copyright the better. Zero is the best.

Commercial enterprises stand on the shoulders of lax copyright laws. For example, foundational Disney works would have been illegal for them to make under the copyright laws they have since purchased.

https://drewdevault.com/blog/Alice-in-Wonderland/

Copyright is a textbook ladder pull.

There are lots of famous artists that are older than copyright.

And worse than them being recognized, they might even get accused of copying their own art if someone else became famous due to a copy.

You mean like right now? Here is A24 claiming copyright for Backrooms related media that came out before their Backrooms related film: https://kotaku.com/backrooms-a24-copyright-strikes-kane-pars...

Being "accused" of copying literally does not matter if copyright didn't exist. This framing is only an issue under copyright.

Society would miss out a lot.

Society actively misses out a lot. We could have had tons of derivative art that has been buried for the sake of propping up companies. We could have had Aaron Swartz. Abolish copyright.

Okay, but why is that something to be concerned about? How would one be able to probe to see if a server recognizes a public key? Why does that matter?

stole

Copying is not theft.

The correct way to legislate this is to abolish copyright. It is strictly a negative force. Nobody makes art because of copyright, only in spite of it.

What?

The only actually interesting thing about this regarding "career ruining messages" is how easy accidental disclosure violations would become.

This is the Zig repository. It is totally appropriate to expect people to be Zig experts when working on Zig itself. People should understand the repository they are talking about. If you're not even invested enough to write a project in Zig, of course your opinion is nothing but noise.

Nit pick: the layers are decoupled from each other, not decentralized. The data layer is internally decentralized. AppViews are a layer of centralized projections of the decentralized data layer.

This isn't true. I knew what gleam was (though do not use it) and what tangled was already (and I do use it), and this announcement is new information to me.

No, the CHLCA (Chimpanzee–Human Last Common Ancestor) would be smarter than humans. It could be that chimpanzee intelligence declined faster than human intelligence. Unlikely, but I want to clarify that we did not evolve from chimpanzees. We share a common ancestor.

... Because AI is more capable?

Understanding how transformers work does not mean understanding how they compose into the capabilities we observe. The former is concretely understood. The latter is an active area of research where no, we (in general, including you) do not understand how they work.

Importantly, Bluesky going south means nothing for your profile or all of the associated data. Your home Mastodon instance going south likely means starting a new account from scratch.

Their most valid criticism of Bluesky is essentially that they don't understand it (they quite clearly haven't tried it, but feel validated in sharing their opinion anyways).

I'll share two reasons why Mastodon is not "the Only Good Choice", as someone who hosted multiple Pleroma instances for myself and others, for years.

- Where do you sign up? The fact that if anyone asks this question for Mastodon, they are almost certainly not directed to a sign up page is far more friction than most people are able to allocate effort to overcome. I went out of my way to host instances so I could have an obvious answer to this question. This is far more friction than the average person would be able to allocate in order to have access to an obvious answer to this question.

- Conversations are simply broken. If you communicate at all in a decentralized way, you will interact with threads where you do not see whole branches of the conversation. Not even due to defederation, just because the branch hasn't naturally federated to your instance. This is not a good social experience.

I encourage people to not accept the articles shallow claims that Bluesky is not decentralized and that it would fail if the company behind it did. Just because Bluesky actually works does not mean it is backed by centralized infrastructure. The data is decentralized, and that is what matters.

By "research project" you you mean by people who understand assembly? Because then we're back to where we started.

I believe the problem stems from ) and )) both being one token wide. I wonder if repeated parentheses being removed from the token vocabulary would improve accuracy for Lisp code generation.

I take it you never run models locally then? Local models that can run on reasonable consumer hardware have gotten to the point of being very useful, but they still occasionally are tripped up with syntax errors. Especially if you quantize the model and KV.

Oops, I found it here: https://doc.rust-lang.org/stable/reference/#rust-releases

I just assumed it was a stable link to the version being read (in this case, the latest stable version).

D and Swift integrate just as easily.

Sure, but those languages are not Rust, which was what was asked about.

Also languages do not exist in isolation, thus the question remains what product will drive Zig adoption, beyond its core community.

The Zig team seems to be banking on providing an excellent build system that is useful beyond applications written in Zig to fill this role.

Do you have any examples as to how Zig is more simple than Rust?

On the surface: just the scale of the things you're expected to know in order to program in Zig vs the scale of things you're expected to know to program in Rust. I read the entire Zig language reference[0] in an afternoon, and then started comfortably writing Zig. I have been wanting to find time to read the Rust language reference[1] for years, but I have never carved out the time to do it, in large part because it simply demands so much more time. I end up just limping along looking up everything when I touch Rust.

I know you're hoping for more concrete examples though, so I'll try to give a few.

- One of the more obvious ones coming from a Zig perspective is the comptime story. Comptime in Zig is super easy, Rust macros less-so.

- In Zig, C libraries can be directly imported and C functions can be called directly. Rust requires (? maybe wants is more accurate?) bindings written in Rust.

- You mention Erlang and Elixir have frictionless async, and while they are essentially async utopias, I would put Golang not terribly far behind. The latest release of Zig introduced an async API that is very close to Golangs async API; I described the parallels in this comment[2]. Zig is certainly no Erlang, but the standard async API is quite nice, even when comparing to languages beyond the scope of ones with minimal runtimes like Rust and Zig.

It's hard for me to go into much more detail than that because I don't really have enough experience with Rust to say much more with confidence.

[0] https://ziglang.org/documentation/0.16.0 (though it was 0.14.0 at the time I read it end to end)

[1] https://doc.rust-lang.org/1.49.0/reference/

[2] https://news.ycombinator.com/item?id=48636824

Simplicity, and a much easier transition from C. Zig very much takes an "extend (or as they actually say: maintain) it with Zig" philosophy, rather than the classic "rewrite it in Rust". Zig integration with C rivals that of C++. Rust can do it, but it introduces a lot of friction by design, and that friction may or may not be desirable for a given project.

I suppose technically, it's not a font in the traditional sense of a TTF font file. But, Ghost Font is an experiment of a way to graphically communicate in writing in a format that AI cannot easily understand

And this thread is seemingly full of people claiming AI can read it while simultaneously sharing that AI could not read the actual message, only the decoy as demonstrated in TFA.

I have often described Zig to people as a middle ground between C and Go. It sounds like you might really enjoy it.

jj with agentic coding is really underrated. The automatic committing is awesome for being able to see diffs between every prompt, roll back changes done by a given prompt, etc.

Notably the posted project is Apache licensed, and your project is Elastic licensed. Your project looks cool and you've clearly put a lot of thought into making it useful, but the license makes it a non-starter for me.

This is victim blaming. The customer is not the one deciding make the batteries non-removable. This is protection from Nintendo.

It's not that they didn't care, it's that they did care in the wrong way. A non-replacable battery means people will be more likely to buy a whole new device if (when) the battery fails.