As one who was interested by Nim and tried it out for some personal projects, I found that this was the biggest problem with the project. There's several options for any given need (including internal tools like LSP or installing the compiler) with very little clear way to choose between them. Each will have different (dis)advantages that you must discover primarily by digging through forum posts or GitHub issues.
In some ways it's the sign of a very strong language, like the curse of Lisp: someone can easily just write their own version of whatever they need. But as a user trying to navigate the ecosystem it is frustrating. I do keep meaning to try it out again though; the language itself is very pleasant to use.
The stakes of changing the way so many people work can't be seen in a short term. Could be good or bad. Probably it will be both, in different ways. Margarine instead of butter seemed like a good idea until we noticed that hydrogenation was worse (in some ways) than the cholesterol problem we were trying to fight.
AI company execs also pretty clearly have a politico-economic idea that they are advancing. The tools may stand on their own but what is the broader effect of supporting them?
Because it's rules for us and not for them. If I take Microsoft's code and "transform" it I get sued. If Microsoft takes everyone else's code and "transforms" it (and sells it back to us) well, that's just business, pal. Thomas's argument is completely missing this point.
There can be no clearer example than iTunes's downgrade into the awful Music and somehow even worse Podcasts. On the plus it has invogorated the 3rd party space.
Without a source code license somewhere on site (I don't see any after looking around) you had better not copy-paste these into a next project. The default state if there's no explicit permission granted is that it's not usable: https://choosealicense.com/no-permission/
Also he's got to approaching retirement age at this point, and there is no backbench corps of other DTS who do what he does. Maybe another decade we'll have his help, then what?
I'm still not sure how I feel about the actual copyright issue, but this was a bad test case. Thaler is trying to have his cake and eat it too; his position is inconsistent (this similar to a previous comment I've made: https://news.ycombinator.com/item?id=34783707).
He wants credit for creating the AI, and he wants to that AI to be recognized as autonomous and independent by getting the Copyright Office's imprimatur. But at the same time he wants to treat the art created by the AI as if it were his, or at least to act on behalf of the AI as if it were not autonomous.
Assuming that the linked post is accurate and that the "approval from senior leadership" to turn the dump back on does not come...then yes, I would say so. Actually there is already Codidact, although if I recall correctly they explicitly ruled out importing SE data when they started up. https://codidact.org
This was one of the promises originally of Stack Overflow: all the content is Creative Commons licensed so that if they "turned evil" (I believe it was Joel that put it this way) the community could, in a way, create a fork. https://web.archive.org/web/20230203170609/https://stackover...
Unfortunately the dumps themselves are not a legal requirement, just a gentleman's agreement, so realistically exercising this ability was still at the whim of the company.
A citation is needed for the number of iOS projects that have more than a minuscule amount of code at the application level that risks memory unsafety.¹ The value proposition becomes stronger for the system frameworks that the app consumes, of course. (Although even the stdlib dips more than once into memory-unsafe Swift for performance.) But this brings us to another of the points from the article: is it really best to use one language for both use cases?
¹And additionally for whether those project would eliminate such code if rewritten in Swift.
GP was most likely thinking not of large roundabouts that take the place of major intersections, but the smaller traffic-calming type where the center can be as minimal as a 3 foot wide concrete block. They can be fit into pretty much any intersection because their purpose is not to change the path so much as to, frankly, eat up whatever extra space is available, which forces cars to slow around them.
This idea ("make a stronger license") has come up in previous discussions of Copilot as well[0].
The problem is that the Copilot project doesn't claim to be abiding by the license(s) of the ingested code. The reply to licensing concerns was that licensing doesn't apply to their use. So unfortunately they would just claim they could ignore your hypothetical Free³ license as well.
Some core designers of Swift, at least Doug Gregor, John McCall, Dave Abrahams, were very much part of the C++ world. Abrahams mentions Gregor's proposals for C++ here: https://youtu.be/6JYAXADQmNQ?t=1157
You do have to remember to use it, but the thing to keep in mind is that you can pipe a list of ANYTHING into it. Any list of text items you can search through with a text query is fair game.
git log --oneline | fzf
for example is one of my favorite tricks. Instead of scanning by eye or repeatedly grepping to find something, it's a live fuzzy filter. And depending on how deep you want to go you can then add key bindings to check out the selected commit, or preview the full message, or anything really.
Regardless of how many there are, I believe the point is not to monitor them live but to have recordings if the store wants to bring charges for something.
In some ways it's the sign of a very strong language, like the curse of Lisp: someone can easily just write their own version of whatever they need. But as a user trying to navigate the ecosystem it is frustrating. I do keep meaning to try it out again though; the language itself is very pleasant to use.