and figure out whether the new framework with a weird name actually addresses
Couldn't name what this is about in the title, nor in the teaser, I guess?
"Latest hotness" and "the new framework with a new name" isn't very discerning.
and figure out whether the new framework with a weird name actually addresses
Couldn't name what this is about in the title, nor in the teaser, I guess?
"Latest hotness" and "the new framework with a new name" isn't very discerning.
From the paper abstract:
[…] Novice workers who rely heavily on AI to complete unfamiliar tasks may compromise their own skill acquisition in the process. We conduct randomized experiments to study how developers gained mastery of a new asynchronous programming library with and without the assistance of AI.
We find that AI use impairs conceptual understanding, code reading, and debugging abilities, without delivering significant efficiency gains on average. Participants who fully delegated coding tasks showed some productivity improvements, but at the cost of learning the library.
We identify six distinct AI interaction patterns, three of which involve cognitive engagement and preserve learning outcomes even when participants receive AI assistance. Our findings suggest that AI-enhanced productivity is not a shortcut to competence and AI assistance should be carefully adopted into workflows to preserve skill formation – particularly in safety-critical domains.
And there are cookies 🍪
Do they share my cookies with third parties? /s
I have the January feature update installed but I don't see a/the compress empty lines setting.
I've been using the Extension Shrink Empty Lines for quite a while. Great to see it's supposedly supported natively now.
That's really cool.
Repo already archived, only 26 days after the linked post?
Oh, they rewrote the ruby tool into Go. Even better.
https://github.com/git-pkgs/git-pkgs
Looks like it probably lost some dependency manager systems support through that.
You add more tags?
In my main work projects I regularly archive tags into refs/archive/tags/* - which is hidden from normal tooling, but still accessible in Git and (some?) Git tooling and UIs.
Branches get "path" prefixes like draft/* or other longterm category indications. I don't archive them, but if I would, I would put them into non /refs/heads like /refs/archive/heads/*.
What's Codeberg's stance on this? Do they advocate for this, accept it, or dislike it?
Their FAQ talks about having disabled mirroring because of resource use of abandoned mirrored repos. Their blog post about the drop of mirroring says that manual mirroring is still possible.
Is it open source if there's no source yet 🤔
I wouldn't call such things agents though. They're not acting autonomously or out-of-process.
Powered by LiveKit
Apparently it's AI coded? Or maybe not?
What does powered by mean when LiveKit is about AI agents?
Are we letting AI agents meet instead of ourselves?
The linked LiveKit website and linked LiveKit blog post seem completely disconnected. I don't get it.
If the XML parser parses into an ordered representation (the XML information set), isn't it then the deserializer's choice how they map that to the programming language/type system they are deserializing to? So in a system with ordered arrays it would likely map to those?
If XML can be written in an ordered way, and the parsed XML information set has ordered children for those, I still don't see where order gets lost or is impossible [to guarantee] in XML.
https://www.w3.org/TR/2004/REC-xml-infoset-20040204/
[children] An ordered list of child information items, in document order.
Does this not cover it?
Do you mean if you were to follow XML standard but not XML information set standard?