I got tired of keep optimizing prompt and rolling out changes in production. So I built a neurosymbolic language to help with that, where prompts as policies instead as hard rules.

https://github.com/canto-lang/canto-lang

Logic systems are a good place where the library first approach tends to work well: you keep a small, boring core (the inference engine), and let people extend it with predicates, rules/operators, and domain packages.

I’ve been experimenting with a small defeasible-logic core (argumentation semantics + priorities + conflict detection) that stays stable, while most of the real meaning lives in extension points. https://github.com/canto-lang/canto-lang

I wonder why nobody said one word about Shen Language[1].

[1] http://www.shenlanguage.org/

Pony is amazing, I am curious about the object capability model applied to distributed systems.

http://erights.org/talks/thesis/markm-thesis.pdf has several chapters dedicated to the concept. Happy reading.

that's an awesome paper. thank you for posting it.

Thanks.

We still have tons of work to do in general. There's a paper on how to do distributed actors with Pony but as yet, we haven't implemented anything yet. We started but deprioritized it.

https://www.doc.ic.ac.uk/~scd/Disributed_Pony_Sept_13.pdf

The standardization is "easy", however we should not forget the browser must support the wrong behavior, because a bunch of applications are expecting that behavior, otherwise the implementation of the "standardised" URL parsing would break the web.

In fact, it is a kind of common practice to generate tons of code. For C language, we have Csmith[1]. It is used to find bugs in llvm and GCC.

[1] https://embed.cs.utah.edu/csmith/

SVG is amazing, my main concern about it. it is because it creates a huge burden to browser developers. The spec is huge [1]. And some parts are outdated[2].

[1] https://github.com/WebKit/webkit/tree/master/Source/WebCore/... [2] https://developer.mozilla.org/en-US/docs/Web/SVG/SVG_animati...

> SVG is amazing, my main concern about it. it is because it creates a huge burden to browser developers.

Yes, it would have been better if SVG was designed on top of something simpler; and this something simpler could be implemented by browser developers. Probably, such an approach is more secure too. But, I guess it is too late now.

I imagine they could implement it on top of Canvas/WebGL.

Like https://github.com/canvg/canvg (which AFAIK doesn't do hit testing like 'real' SVG, but is a promising start).

Browser support is kind of okay. The problem is more that it is hardly supported outside of browsers because of the complexity

To be fair, this is equally true of HTML.

Probably local hire would be much better, however good programmers don't want to work in the Group 2. The want to work in a big company or in a cool startup.