Get people hooked, tell them spending time coding is no longer needed, let their skills deteriorate, tell them they need cough up for a licence to do their job
Forcing developers to pay for models that were build on code they scraped scott-free
A tax to do their job that developers are jumping at the chance to pay
Everybody's finally realising that node dependencies are a threat, but letting these AI companies gatekeep the industry is a bandwagon people are scrambling towards
> Forcing developers to pay for models that were build on code they scraped scott-free.
Yes this makes me sad behound explanation. Specially when I see open source developers happily using these tools. These companies stole your, free, hard work and charge you a subscription!! Not to speak about them torrenting books and (most likely) training on private repos.
This and devs paying a subscription to use a tool that is marketed as trying to replace them.
I had 150$ monthly budget thatbI used for various open source projects and I've cut that entirelly.
I don't get what you're saying. You're frustrated that Open Source projects were used to build these AIs and that OS devs (or devs in general) are paying to use AI.
Then you say you had money that you used to donate(?) to OS and have cut that because of the frustration?
Open source just means sharing the source code for people to learn off or have the ability to customize on their own. I don't think there is any need to be frustrated about that (now if it was copyright/private of course).
> To summarize the analysis that now follows, the use of the
books at issue to train Claude and its precursors was
exceedingly transformative and was a fair use under Section 107
of the Copyright Act. And, the digitization of the books
purchased in print form by Anthropic was also a fair use but not
for the same reason as applies to the training copies. Instead, it
was a fair use because all Anthropic did was replace the print
copies it had purchased for its central library with more
convenient space-saving and searchable digital copies for its
central library — without adding new copies, creating new
works, or redistributing existing copies.
> Forcing developers to pay for models that were build on code they scraped scott-free
That's also caused by some very smart (even brilliant) developers (you can see many of them in this very thread) choosing to be oblivious about all this and bury us all under, hoping that they'll be among the last ones to go. Writing this down I realise that they maybe aren't all that smart.
I'm perhaps missing something but if there were a significant connection, wouldn't this mean those in sunnier climates would have better verbal and visual memory?
If there were a connection then I would wager that there are more significant factors, since I have seen or heard of no evidence to assume those in sunnier climates have better verbal and visual memory.
The results of this study seem to show no significant correlation, anyhow.
Not necessarily, if the effect was due to exposure to levels beyond what you’d even get in sunnier climates. It also could be possible those in sunnier climates do experience this effect and it was unnoticed, due to political and socioeconomic issues associated with typical equatorial countries
The rust conversion was a byte-for-byte replica of the original's bytecode, was it not? Thereby it was easily possible to validate the quality of the AI-based work. The same would obviously not be possible for patches. I don't believe you can use the rust conversion as a valid, if implied, argument that you can take AI-patches in good faith.
My implied argument is not so much that "because llm was used, then llm must be used."
The original argument proposed by the author is essentially distilled into, "because llm could be used, we must no longer accept public contributions."
Which is, in my opinion, a disproportional and misguided overreaction. The llm was apparently good enough to do the byte for byte replica, so we know that it can be used (within the context of ladybird) in a way that's apparently acceptable to the maintainers.
To attempt to get more precise, argument is that "closing the gates" is moving in the wrong direction against progress, and a signals a potentially net negative impact to the ladybird project.
I don't have a fully formed thesis, it's a lot of vibes. It just feels wrong. I'm willing to acknowledge that, much like the overreaction that I'm calling out, I could be experiencing a similar kind of conservative gut reaction to the changing of the open source community that unsettles me.
Well see how it all shakes out. Right now the topic is so charged and we don't have a good suite of tools and heuristics for the new world, that were bound to see the gamut of reactions.
From my fairly quick reading, their premise seems to be "we can no longer trust /unknown/ developers who use AI to understand and maintain the code they submit", rather than a simple attack on those who use AI.
This seems fair to me: numerous developers would love to put "contributed to the Ladybird project" on their curriculum vitaes, and AI tools can now make this within the reach of a huge number of people.
But the Ladybird project needs more than just working-code, something that AI can easily produce: they need code that is understood and maintainable by the person who submitted it.
Not only does AI-generated code fail to guarantee this understanding and maintenance (to a greater degree than before), but the developers increasingly need to get through an avalanche of AI-generated pull requests rather than, say, code new features.
I would prefer projects to be developed in the open: but when developing in the open makes the code checking exponentially harder, and the chance of the submitters sticking around becomes significantly lower, then I can at least understand.
When the dam starts to overflow, then something needs to be done.
I see where you're coming from, but I think it's less the fact that they _can_ use an LLM to do this and more that they can't guarantee anybody else has exercised equal diligence with their code or equal experience with browser engines.
It's not unreasonable to feel conflicted about this, but at the same time, I wonder if they're starting to burn out on code review.
How the Russian interests have taken over significantly invalidates the purpose and existence of the FBI, CIA, and NSA.
But then again, President Biden's administration had multiple grounds to prosecute Trump for crimes committed, whether the attempted coup or espionage with top secret documents or Epstein, and they just did not make it happen in a way that had any effect.
OpenAI etc, are, however advertising them like they are magical oracles, on the verge of lifting humanity to next phrase of civilisation. The idea the majority of users know what nondeterministic even means it's a massive, massive ask
Most of the time you don't need redundancy. You need regular backups for exceptional circumstances. And k8s gives you more complexity, and more problems through more moving parts, to give you the possibility of using a feature you'll never need, and if you do start to use it it'll probably be instead of fixing performance problems downstream
Are we talking for personal projects where there are no expectations, or small startups where you don’t have much scale but you still care about down time and data loss?
Personal projects are one thing, but even the smallest startup wants to be able to avoid data loss and downtime. If you are running everything on one server, how do you do kernel patches? You need to be able to move your workload to another server to reboot for that, even if you don’t want redundancy. Kubernetes does this for you. Bring in another node, drain one (which will start up new instances on the new node and shift traffic before bringing down the other instance, all automatically for you out of the box), and then reboot the old one.
Again, you could do all of this with other tech, but it is just standard with Kubernetes.
> but even the smallest startup wants to be able to avoid data loss
Seems true at a glance!
> and downtime.
Maybe less so - I think there’s plenty out there, where they’re not chasing nines and care more about building software instead of some HA setup. Probably solve that issue when you have enough customers to actually justify the engineering time. A few minutes of downtime every now and then isn’t the end of the world if it buys you operational simplicity.
I think the continuous churn of versions accelerates this disregard for supply chain. I complained a while back that I couldn't even keep a single version of Python around before end-of-life for many of the projects I work on these days. Not being able to get security updates without changing major versions of a language is a bit problematic, and maybe my use cases are far outside the norm.
But it seems that there's a common view that if there's not continually new things to learn in a programming language, that users will abandon it, or something. The same idea seems to have infected many libraries.
IME there’s a core set of very popular Java libs you can go very far without adopting obscure libraries you’ve never heard of. Eg apache-commons, spring, etc. the bar to adopt a 3p lib seems higher in some ecosystems than others.
How can node scripts write to files, make network requests, etc etc without any standard library? Of course it has a standard library. You could maybe say javascript doesn't have much of a standard library (Array, String, Promise, Error, etc) but js is used with a runtime that will have a standard library.
It frames themselves as under attack, which thereby gives themselves moral justification to attack, and when those attacked attack back they fulfill their justification, and the circle of violence and death perpetuates.
People from a nation think and write alike because they share a common canon of literature and stories.
It's just a pity AI was trained on mindless, garbage business-speak, and now that's our globalised common literature.
And now we're feeding that regurgitated mindless, garbage business-speak back into AI models, thereby reinforcing the garbage and further rotting our minds.
This is just a culmination of the last two years of tension. The most recent friction is around Lebanon where France sees itself as the protector of its former colony.
Interesting take from Le Monde: "Israel turns its back on France as Paris struggles to maintain dialogue"
Forcing developers to pay for models that were build on code they scraped scott-free
A tax to do their job that developers are jumping at the chance to pay
Everybody's finally realising that node dependencies are a threat, but letting these AI companies gatekeep the industry is a bandwagon people are scrambling towards
reply