Splizard

No, by leveraging unkeyed struct initializers as the switch case pattern, which the Go compiler does exhaustiveness checking on.

You can also add support for exhaustive switches on tags.

Tagged unions can be implemented in user code, you dont actually need language support to use them.

https://github.com/splizard/tagged

exactly

What are your plans around the maintenance of this project, how would you feel about solo being incorporated into the musl build for graphics.gd ?

Small nitpick but Go doesn't really have any YOLO C/C++ code in its runtime and standard library.

yea this headline is pretty disgusting

Maybe you could look at using some AI assistance to provide some real 'useful' feedback to the OP about what made you lose interest, as your false confidence in some opaque 'AI-detection' heuristic is lazy and only harms individuals who are trying to find effective ways to share information.

you can patch musl, to initialize the brk state as -1 and then it won't use it.

You have to tell musl to use mmap instead of brk. You're right that it doesn't work in all cases but as long as you switch TLS on calls (and callbacks), at least with a project the size of Godot, you can approach a workable solution.

If only there was an easy way to fund all the Open Source programs you like and use, so the projects who struggle with it, can put more focus into design.

Seems like a win-win, take my money solution, for some reason the market (and I guess that means investors) are not pursuing this as a consumer service?

The issue appears to be cascading internationally due to internal dependencies on us-east-1

The problem with configuration formats, is not syntax, or abstraction, it's the lack of consistent language server integration, it's problem when I can't lookup the definition for a key, the expected type, or quickly jump to definitions that clearly show which keys are available to configure.

> neither of those languages has dynamic linking

what do you mean by this?

you can totally still do this

Very exciting stuff!

Remind me again why we can't use HTTPS certificates to sign code that is linked with a domain?

Only Linux, BSD and other operating systems that are entirely Open Source.

Even Windows has scary warnings now that pop up unless you pay several hundred dollars a year plus you have to go through a completely unreasonable process (that often requires being shipped a physical USB device) just to sign your application.

> require your device to be running an official rom signed by Google

How exactly does the app detect this?

If only this was voluntary and automated by an Open Source service provider, so that I only have to pay one monthly fee and all the FOSS that is detected to be in-use on my machine is funded.

Go is a great language because it has distinct types by default, it's not about "making invalid states unrepresentable", it's about recording relationships about a particular type of value and where it can be used ie. it doesn't matter that UserID is just a string, what matters, is that now you can see what string values are UserIDs without making assumptions based on naming conventions.

Can you add support for duplex numbers? (duplexnumbers.com)

This is great! There's way too many arcane text file formats (configs, Dockerfiles, workflow definitions etc) without any sort of fast feedback loop on type-safety, documentation etc.

We need more projects like this and if a system is running SystemD, this needs to be enabled and integrated with any LSP-supported editors.

> makes it easier for integrators to build a robust integration with you

No, don't say 'easier'. It makes it possible to build a robust integration. We need to stop with this notion that omiting idempotency from an API just makes things "more difficult" to develop. Without idempotency, you garuantee that the resulting system is "difficult" to use and full of nasty issues that are waiting for the right conditions to collapse the entire house of cards you've built.

So many SaaS providers have never even heard of idempotency, let alone design it into their APIs. Many people believe you can just sprinkle it on as a library without having to think about it.

All APIs with multiple distributed servers must support idempotency. Refuse to do business with any organisations who do not design this into their APIs!

> The second part demonstrates how agents communicate with each other through workflows defined in YAML

oh no

You've set the Go code to use int64 but the other faster implementations are using int32.

Why create a new language, rather than use an established programming language like Go where you can actually write an implementation too?

I think the point the author is trying to express here, is that it can be a useful in API representation, to couple the design with other representations designed by other parties.

I don't think "No Abstractions" is a good framing for this, although I would have to admit I dislike use of the term abstraction, as it implies there is a hierarchy of representations.

Alignment, if you add a uint8 tag for example, you'll end up effectively doubling your pointer size.

Consider a codebase where all variables are consistently named with single letters and all values are string-typed for consistency.

Somebody comes along and creates a new, isolated piece of functionality using words for variable names and using the languages type system for numeric values and structures. It works well.

It certainly looks like this inconsistency would make it easier to work with this code in the future. Any conversion functions introduced that deal with the consistent string types and the new inconsistent types will help new developers understand both types of code.