> That would be like antropic and google crying about china stealing the weights that were originally built by scraping as fuck stolen content :-)
do you really see a relation between the two, or are you just willfully 'buying an advertisement' by trying to shape a metaphor from the social qualms that you wish to rebroadcast to people?
in other words, no -- this isn't at all similar to the companies that steal media in order to train models only to complain about similar theft from other companies targetted towards them -- but I agree with the motivation, fuck em; they're crooks...
but don't weaken metaphors simply to advertise a social injustice. If you want to do that, don't hijack conversations abroad.
This is the first thing that occurred to me. The people above suggesting a cobol to python or go update confuse the heck out of me. Why not just convert to vanilla jacascript at that point? Bizarre
GitHub recently added new repository settings to turn off pull requests or limit them to approved contributors. The announcement doesn't mention AI agents, but that's certain relevant.
GH also needs to find a way to stop AI scraping of IP.
(Or not. It might be lucrative to host some novel algorithm on GH under a license permitting its use in generative LLM results, at a reasonable per-impression fee.)
I've always found OCaml's (* ... *) comments annoying, because it needs shift for both characters. But I suspect it's easier to type on a french keyboard.
That was back when there was "real" UNIX around, as well as a number of clones, including Microsofts own Xenix (maybe they had offloaded that to SCO by then). So UN*X was one way to indicate that it meant UNIX-like OSes.
IIRC Microsoft's internal email still ran on Xenix at the time (until Exchange betas got good enough for internal use c. 1995?), so perhaps more trademarks than some sort of absolute hatred of Unix. Also note that one of the two APIs that NT OS/2 was initially going to support was POSIX, albeit perhaps more because the US government wanted that than a true love of UNIX. Although the design rationale document (ntdesrtl) does lament that existing POSIX test suites tend to also test "...UNIX
folklore that happens to be permissible under an interpretation of the POSIX spec".
Did Microsoft never run Microsoft Mail internally?
It was an email system that ran on top of file system. If I recall, mail clients connected over a networked drive to access mailboxes. So it was never regarded as being very scalable.
Yes, MS Mail for PC Networks used a shared file system for email.
The Workgroup Apps (WGA) divison ran MS Mail for PC Networks since they produced MS Mail. Gotta dogfood your product. The WGA email system used a Xenix gateway to connect with the rest of Microsoft.
The rest of Microsoft ran MS Mail for Windows with a Xenix email backend and address book, since MS was already using Xenix before MS Mail for PC Networks existed.
Windows for Workgroups 3.11 contained a one postoffice-version of MSMail, (which could be upgraded to the full version).
It is a generic way to refer to unix and unix-like systems. It is still in use today, e.g. to indicate Linux as part of the set. For this document most likely it refers to Xenix (MS's unix).
As others are saying, the * is meant as a wildcard, not as censorship. It's meant to also cover the likes of Linux or Xenix etc, although there isn't actually any other name that would strictly fit the pattern of "UN*X".
And Google and Microsoft have huge distribution advantages that OpenAI doesn’t. Google and Microsoft can add AI to their operating systems, browsers, and office apps that users are already using. OpenAI just has a website and a niche browser. To Google and Microsoft, AI is a feature, not a product.
I like Basecamp’s framing of software development time as management’s “appetite” for a new feature, how much time they are willing to spend on a project, as opposed to an estimate. This helps time box development and control project scope.
reply