Unfortunately, some of us are stuck in a country which is a Microsoft shop, which makes it next to impossible to get into a Linux job - especially an entry-level one (these are basically non-existent where I live). I've even considered moving to a place where Linux jobs are a thing (Europe), but that would mean learning the local language first and also already having sufficient professional Linux experience (no one would hire a foreigner for an entry level role when they could just hire a local).
So unless you've got any bright ideas, I'm stuck in this Microsoft job till someone comes up with some magical Linux roles, or I start my own Linux-based company and twiddle my thumbs because there's no customers...
They could also just be people with bills to pay who are maybe faced with—by some accounts—a very challenging employment market. Or maybe due to disabilities they find the process of finding new work difficult or impossible.
That is fine, but they adopt or delegate corporate opinions onto others. I feel that if you need to lie to people because of money, your job is not honest. (I don't mean you; I mean people who need to do this because otherwise they may lose their job etc...)
Except for the "disabilities" part, which is problematic to classify, wouldn't your description broadly fit the word "losers"?
EDIT: I don't understand the downvotes. It's not a value judgement on Github employees, it's about the meaning of the word "loser". Go back to your teenage years. What's a loser? Someone, often through no fault of their own, keep being in a bad situation, having the "short end of the stick". What characteristically makes them losers is that they lack the audacity to snap out of it.
Isn't that an accurate definition of what "loser" generally means?
> Isn't that an accurate definition of what "loser" generally means?
"Loser" is a catch-all taunt that bypasses empathy. But certainly they might be 'in a losing situation', which is an important distinction.
> Except for the "disabilities" part, which is problematic to classify
Disability in this context is something intrinsic to the person (e.g., physically, mentally) that makes the employment process substantially difficult to engage with.
In addition to disability, difficulty can also arise do to any prejudice that might be levelled against them (e.g., ageism, sexism, junior vs senior, skin color, language skills, country of origin), as well as visa consideration, financial situation, etc. There's so many things that affect the risk calculus of changing jobs.
Github is migrating from their old infra to Azure. Doing migrations like that is hard, no matter who you are. And from a business and engineering perspective I think it makes sense to leverage the economies of scale of Azure instead of GitHub running their own boxes.
Anyone being forced to use Azure has, at least temporarily until they can find a new job, lost at life, not necessarily through any fault of their own. The poor souls probably also have to use Teams.
The engineers at github are getting paid $300k/year at SWE3 to do their job. I don’t think they lost at life.
Why bring people down so hard? That is really solid money and you can provide for a family, retire in your 40s, and it is work that does not destroy your body.
Spending your life working on making things worse (and knowing it) is pretty demoralizing. I know many people who have made the decision to take a pay cut or just quit when they realize that’s their job.
Sometimes those people aren't realizing that they're making things worse, they're just in a depressive spiral and can't see the other end, or see how much good is still being generated while other things are temporarily worse, or see that different tradeoffs have been made to make things worse in some ways and better in others. Just as people can delude themselves that they're always making a positive impact, people can delude themselves that they're making a negative one. The latter tends to be more costly, though, which can sure be annoying to those with a bias for a more cynical or pessimistic outlook...
Trying to ascribe positive/negative impact to strangers isn't usually a useful exercise, even if you have enough data to make a solid case. It can be cathartic -- imagine a different world where programmers making things worse would screw off and go do something else that's not programing! (I have a similar imagining, like of a world where programming is done by those who love it even outside of work -- even though I've worked with and helped hire excellent engineers who only treated programming as a job, they weren't my favorite to work with, and some were very much not excellent.) The best you can hope for is to trigger some self-reflection, and I do think that's important on an individual level. It's better to not make the world uglier, if you notice yourself doing so, and it's not just a distortion of your thinking, then you should probably stop, do something else, or figure out if it's at a level that you can compensate. A Richard Stallman quote I like:
"The straightforward and easy path was to join the proprietary software world, signing nondisclosure agreements and promising not to help my fellow hacker....I could have made money this way, and perhaps had fun programming (if I closed my eyes to how I was treating other people). But I knew that when my career was over, I would look back on years of building walls to divide people, and feel I had made the world ugly."
> they are dispirited clock-punchers who don't care about their craft.
Interestingly that is synonymous with losers according the definition of it in gervais principle. Which weirdly makes being called a loser less of an insult. (More like realist)
The absolute state of Github is that I use it dozens of times a day and it works flawlessly, for free, with intermittent outages.
Microsoft is doing more with Github than I can say for most of their products. I won't go to bat for the Xbox or Windows teams, but Github is... fine. Almost offensively usable.
Also, there have been increasing reports of open source maintainers dealing with LLM generated PRs: https://news.ycombinator.com/item?id=46039274. GitHub seems perfectly positioned to help manage that issue, but in all likelihood will do nothing about it: '"Either you have to embrace the Al, or you get out of your career," Dohmke wrote, citing one of the developers who GitHub interviewed.'
I used to help maintain a popular open source library and I do not envy what open source maintainers are now up against.
> GitHub seems perfectly positioned to help manage that issue, but in all likelihood will do nothing about it
I genuinely don't understand this position. Is this not what Github issues bots were made for? No matter where your repo is hosted, you take the onus of moderating it onto yourself.
Downtimes are an issue, it's why I jokingly mentioned it. Besides that I'm without gripe. Make Github a high-nines service and I'll keep using it until the wheels fall off.
Given the trajectory of Microsoft products it stands to reason Github’s future is uncertain. Also Git is ultimately a hosting platform that any competent software shop can recreate; the people behind the platform matter more than the platform itself.
My thinking as well. If people don’t like Microsoft, the last place to start their quixotic adventure would be GitHub.
I don’t use Azure or Windows. At work I push against Teams and actively try to persuade customers not to use Microsoft products. The reason isn’t even ideological - most of the time their products suck and the dev support is bad. VScode may be an exception, I’ll give them that.
So you are ok with 2FA, right? If you contribute code there.
Now - what if you are not ok with it? What can you do?
> Almost offensively usable
I think you conflate two points here. One is how useable github is. The other is: control. At which point are you no longer ok with what a private company does? This is not solely about Microsoft alone by the way.
Yes. Are you not? It's one of the most effective measures to prevent a whole class of supply chain attacks. On Github the 2FA is also flexible enough to allow non-hardware passkeys, so you can choose a privacy preserving option with good UX.
...so far... but the problems are noticeably increasing in frequency, especially in Github Actions, and most of those don't show up on the status page because they are so random (eg restart the ci pipeline and it works) It feels exacty like Github is slowly rotting from the inside and I guess the reason is that everybody is forced to work on pointless AI features so there's nobody left doing actually important feature and maintenance work.
I’m sure this isn’t directed at everyone that works at GH, but it would have been more tactful to fault the people making decisions. Those frustrations are real though.
A blanket ban on LLM-generated code is a completely reasonable position. If someone couldn't be bothered to write the code, why should anyone else bother to read it, let alone merge it?
But to determine its merit a maintainer must first donate their time and read through the PR.
LLMs reduce the effort to create a plausible PR down to virtually zero. Requiring a human to write the code is a good indicator that A. the PR has at least some technical merit and B. the human cares enough about the code to bother writing a PR in the first place.
It's absolutely possible to use an LLM to generate code, carefully review, iterate and test it and produce something that works and is maintainable.
The vast majority of of LLM generated code that gets submitted in PRs on public GitHub projects is not that - see the examples they gave.
Reviewing all of that code on its merits alone in order to dismiss it would take an inordinate amount of time and effort that would be much better spent improving the project. The alternative is a blanket LLM generated code ban, which is a lot less effort to enforce because it doesn't involve needing to read piles and piles of nonsense.
What people don't like about LLM PRs is typically:
a. The person proposing the PR usually lacks adequate context and so it makes communication and feedback, which are essential, difficult if not impossible. They cannot even explain the reasoning behind the changes they are proposing,
b. The volume/scale is often unreasonable for human reviewed to contend with.
c. The PR may not be in response to an issue but just the realization of some "idea" the author or LLM had, making it even harder to contextualize.
d. The cost asymmetry, generally speaking is highly unfavorable to the maintainers.
At the moment, it's just that LLM driven PRs have these qualities so frequently that people use LLM bans as a shorthand since writing out a lengthy policy redescrbiing the basic tenets of participation in software development is tedious and shouldn't be necessary, but here we are, in 2025 when everyone has seemingly decided to abandon those principles in favor of lazyily generating endless reams of pointless code just because they can.
Usually I hate quoting "laws" but think about it. I do agree that it would be awesome if we scrutinize 10+k lines of code to bring big changes but its not really feasible is it?
> A blanket ban on LLM-generated code is at least arguably a reasonable policy.
No, I don't think it is. There's more nuance to this debate than either "we're banning all LLM code" or "all of our features are vibe coded".
A blanket ban on unreviewed LLM code is a perfectly reasonable way to mitigate mass-produced slop PRs, but it is not reasonable to ban all code generated by an LLM. Not only is it unenforceable, but it's also counterproductive for people who genuinely get value out of it. As long as the author reviews the code carefully before opening a PR and can be held responsible, there's no problem.
Banning all LLM code doesn't mean they see things in binary terms like that. There is nuance between "all code must have 100% test coverage" and "tests are a waste of time", for instance, but that doesn't mean a project that adopts one of those policies thinks the middle ground doesn't exist.
A blanket ban is really the only sensible thing to do so that no time is wasted for both sides (contributors know upfront that there's no point trying to get an AI-generated PR accepted - so they won't waste time creating one, and project maintainers don't waste time reviewing what might be broken AI slop - even if some AI generated PRs would be acceptable from a quality point of view).
When there's a grey zone then there will be lots of pointless discussions like "why was this AI-generated PR accepted but not mine" etc etc...
Perhaps you misunderstood my comment. I'm not advocating for vibe-coded AI-generated PRs, and I do think that blanket banning them is pretty reasonable for the reasons you stated.
However, I don't think that banning all AI-generated code is reasonable. Having an LLM generate a couple of functions or a bit of boilerplate in an otherwise manually coded PR should not invalidate it from being accepted if it's helpful.
Given my own experience working on compiler stuff with LLM, I'd say it's a very good decision.
LLMs jump at the first opportunity to use regex for EVERYTHING instead of doing proper lexing/parsing, for example. You need to repeatedly tell it not to use regex. In the end you might as well hand write your code, because you actually know how it works, unlike a clueless LLM.
No wonder they moved to Codeberg. Those kinds of projects tend to do the ol' move to Codeberg for whatever reason. If I had to put an analogy to it, Codeberg is like Kick and Github is like Twitch.
More seriously: I probably wouldn't have called every single current employee of GitHub a "loser", but more because I think truly cool people don't define themselves by where they happen to work at any given time. I'm sure the vast majority of people at GitHub are just tech employees trying to earn a living and don't particularly care whether the Zig guy thinks they're cool or not. What actually matters is that GitHub is a big centralized platform run by Microsoft for their own ends, and it's good to be free of it.
Holy shit, some people in the Zig community are toxic af. By extension, this means the community itself has issues it needs to face.
Not only have some of these folks - including the creator - been shitting in Rust threads, but here they're in here shitting on the awesome engineers at Github for no reason at all.
Good god.
edit: this is written by Andrew, the creator. The culture is rotten from the head.
Their "VP of Community" wrote this in 2020: https://kristoff.it/blog/addio-redis/ I didn't come across it until 2022. Still, particularly that and other writing from him and others convinced me the Zig community is full of goobers. That's not so bad, I have my tastes in immature humor and can sometimes be a goober too, but the application in that post's clearly-marked over-the-top skit still is just bizarre and doesn't encourage me to interact with them. To be more fair to the author and the community though, especially with respect to this GitHub migration, his more serious writing is better: https://kristoff.it/blog/the-open-source-game/ (2021). Some nice things said about Rust and the Rust community, even. In that he outlines a core position of "software you can love" being what he wants to create and inspire people to create, and how tents like "big tech" and "open source" don't really cater to that. The migration off of GitHub is predictable in the sense that GitHub stopped being something a lot of people loved a while ago -- of course some still love it, this tent creates obvious tension. (Though I don't know that Codeberg is any better and worthy of love. A few libraries I use have migrated to it and it seems fine at least, though them using Anubis is annoying and I've gotten the fail page of "Internal Server Error: administrator has misconfigured Anubis." a number of times. It does not spark joy in me.)
someone called some indeterminate anonymous corporate group of people who actively participate in enshittification of a product “losers”. you call that specific private individual “rotten”.
I can't imagine being someone like Andrew, or any BDFL of a popular open source project, and having to deal with folks like this. Imagine posting a timed output of your compiler on a thread about a similar language's slow compiler and having someone cite this as bad behavior.
Anyway, the clear absurdity of this particular post aside, it's not OK to call other people monkeys. I make no statement on the quality of their engineering. But they're people! I'd hope to see a quiet dignity from the Zig folks here. They've done so much excellent work, and I'm sure it's frustrating to see what software can be and then have it sharply laid against what software often is. But kindness is always the way.
Thanks to everyone involved with Zig for their work and love of software!
It's completely fine for someone working on a programming language that is useful for some of the same things as Rust to compare that language to Rust, including in ways that make the language not seem as good. Indeed, this is useful information for someone who is using Rust and is considering using Zig (or vice-versa), or who is new to both languages and trying to figure out which is better for their use case.
In what way is the tone of the linked messages not appropriate? Rust is a programming language, not a sacred object. It's fine to say that a different programming language does something better than it, regardless of whether or not you're the developer of that language.
To be clear I like Rust and use it frequently and have for about as long as it's been publicly released, whereas I have only played around a little bit with Zig and I suspect I won't like it as much as Rust even when it's feature-complete. But I don't like seeing an attempt to enforce a social norm that it's wrong to point out shortcomings of Rust, especially when it's aimed at people doing the interesting and valuable work of exploring other areas of the systems programming language design space that Rust is not doing.
Ziglang is a small organization supported by donations, Microsoft is one of the largest companies in the world. If anything, they're punching up.
Calling people losers isn't classy, but if I were a well-paid Microsoft employee I'd laugh all the way to the bank that some community funded purist called me that. If it's supposed to be bullying he isn't very good at it.
Hmm, that seems plausible, yeah. It's unfortunate munchler didn't say something like that. But it seems like now people on HN are dogpiling on this Andrew guy? I imagine he'll feel the same way reading this thread, won't he? Surely there's a solution for bullying other than more bullying?
Regardless, it's hard for me to imagine that many readers will find great intellectual interest in a long thread about what a terrible person Andrew is.
Look at the absolute state of what they are working on. If they are not losers, they are dispirited clock-punchers who don't care about their craft.
It’s more likely that most of them are competent professionals doing their best in an impersonal corporate environment, just like the rest of us.
Shielding individuals from outside criticism is a big part of that impersonal corporate environment.
Not all of us sold out to corporations.
Admittedly some of those may be a bit ... unusual. Like the guy who created TempleOS.
Gotta sell yourself to someone in this world. There’s no sense in demeaning someone about it.
Unfortunately, some of us are stuck in a country which is a Microsoft shop, which makes it next to impossible to get into a Linux job - especially an entry-level one (these are basically non-existent where I live). I've even considered moving to a place where Linux jobs are a thing (Europe), but that would mean learning the local language first and also already having sufficient professional Linux experience (no one would hire a foreigner for an entry level role when they could just hire a local).
So unless you've got any bright ideas, I'm stuck in this Microsoft job till someone comes up with some magical Linux roles, or I start my own Linux-based company and twiddle my thumbs because there's no customers...
They could also just be people with bills to pay who are maybe faced with—by some accounts—a very challenging employment market. Or maybe due to disabilities they find the process of finding new work difficult or impossible.
That is fine, but they adopt or delegate corporate opinions onto others. I feel that if you need to lie to people because of money, your job is not honest. (I don't mean you; I mean people who need to do this because otherwise they may lose their job etc...)
> I feel that if you need to lie to people because of money
Then your beef is with capitalism, not Github/MSFT.
It’s not either/or
Except for the "disabilities" part, which is problematic to classify, wouldn't your description broadly fit the word "losers"?
EDIT: I don't understand the downvotes. It's not a value judgement on Github employees, it's about the meaning of the word "loser". Go back to your teenage years. What's a loser? Someone, often through no fault of their own, keep being in a bad situation, having the "short end of the stick". What characteristically makes them losers is that they lack the audacity to snap out of it.
Isn't that an accurate definition of what "loser" generally means?
> Isn't that an accurate definition of what "loser" generally means?
"Loser" is a catch-all taunt that bypasses empathy. But certainly they might be 'in a losing situation', which is an important distinction.
> Except for the "disabilities" part, which is problematic to classify
Disability in this context is something intrinsic to the person (e.g., physically, mentally) that makes the employment process substantially difficult to engage with.
In addition to disability, difficulty can also arise do to any prejudice that might be levelled against them (e.g., ageism, sexism, junior vs senior, skin color, language skills, country of origin), as well as visa consideration, financial situation, etc. There's so many things that affect the risk calculus of changing jobs.
Github is migrating from their old infra to Azure. Doing migrations like that is hard, no matter who you are. And from a business and engineering perspective I think it makes sense to leverage the economies of scale of Azure instead of GitHub running their own boxes.
Anyone being forced to use Azure has, at least temporarily until they can find a new job, lost at life, not necessarily through any fault of their own. The poor souls probably also have to use Teams.
The engineers at github are getting paid $300k/year at SWE3 to do their job. I don’t think they lost at life.
Why bring people down so hard? That is really solid money and you can provide for a family, retire in your 40s, and it is work that does not destroy your body.
Spending your life working on making things worse (and knowing it) is pretty demoralizing. I know many people who have made the decision to take a pay cut or just quit when they realize that’s their job.
Sometimes those people aren't realizing that they're making things worse, they're just in a depressive spiral and can't see the other end, or see how much good is still being generated while other things are temporarily worse, or see that different tradeoffs have been made to make things worse in some ways and better in others. Just as people can delude themselves that they're always making a positive impact, people can delude themselves that they're making a negative one. The latter tends to be more costly, though, which can sure be annoying to those with a bias for a more cynical or pessimistic outlook...
Trying to ascribe positive/negative impact to strangers isn't usually a useful exercise, even if you have enough data to make a solid case. It can be cathartic -- imagine a different world where programmers making things worse would screw off and go do something else that's not programing! (I have a similar imagining, like of a world where programming is done by those who love it even outside of work -- even though I've worked with and helped hire excellent engineers who only treated programming as a job, they weren't my favorite to work with, and some were very much not excellent.) The best you can hope for is to trigger some self-reflection, and I do think that's important on an individual level. It's better to not make the world uglier, if you notice yourself doing so, and it's not just a distortion of your thinking, then you should probably stop, do something else, or figure out if it's at a level that you can compensate. A Richard Stallman quote I like:
"The straightforward and easy path was to join the proprietary software world, signing nondisclosure agreements and promising not to help my fellow hacker....I could have made money this way, and perhaps had fun programming (if I closed my eyes to how I was treating other people). But I knew that when my career was over, I would look back on years of building walls to divide people, and feel I had made the world ugly."
> lost at life
It's so refreshing to read such a truly philosophical insight.
> they are dispirited clock-punchers who don't care about their craft.
Interestingly that is synonymous with losers according the definition of it in gervais principle. Which weirdly makes being called a loser less of an insult. (More like realist)
The absolute state of Github is that I use it dozens of times a day and it works flawlessly, for free, with intermittent outages.
Microsoft is doing more with Github than I can say for most of their products. I won't go to bat for the Xbox or Windows teams, but Github is... fine. Almost offensively usable.
> works flawlessly
> intermittent outages
Those seem like conflicting statements to me. Last outage was only 13 days ago: https://news.ycombinator.com/item?id=45915731.
Also, there have been increasing reports of open source maintainers dealing with LLM generated PRs: https://news.ycombinator.com/item?id=46039274. GitHub seems perfectly positioned to help manage that issue, but in all likelihood will do nothing about it: '"Either you have to embrace the Al, or you get out of your career," Dohmke wrote, citing one of the developers who GitHub interviewed.'
I used to help maintain a popular open source library and I do not envy what open source maintainers are now up against.
> GitHub seems perfectly positioned to help manage that issue, but in all likelihood will do nothing about it
I genuinely don't understand this position. Is this not what Github issues bots were made for? No matter where your repo is hosted, you take the onus of moderating it onto yourself.
Downtimes are an issue, it's why I jokingly mentioned it. Besides that I'm without gripe. Make Github a high-nines service and I'll keep using it until the wheels fall off.
GitHub: 60% of the time, it works every time.
Given the trajectory of Microsoft products it stands to reason Github’s future is uncertain. Also Git is ultimately a hosting platform that any competent software shop can recreate; the people behind the platform matter more than the platform itself.
As someone who is intimately familiar with GitHub’s data models, I wouldn’t say that replacing it is so technically trivial.
But even then, you are right that that the moat of social cachet and implicit trust is still more valuable than the moat of technical implementation.
True eventually, but not today
My thinking as well. If people don’t like Microsoft, the last place to start their quixotic adventure would be GitHub.
I don’t use Azure or Windows. At work I push against Teams and actively try to persuade customers not to use Microsoft products. The reason isn’t even ideological - most of the time their products suck and the dev support is bad. VScode may be an exception, I’ll give them that.
So you are ok with 2FA, right? If you contribute code there.
Now - what if you are not ok with it? What can you do?
> Almost offensively usable
I think you conflate two points here. One is how useable github is. The other is: control. At which point are you no longer ok with what a private company does? This is not solely about Microsoft alone by the way.
> So you are ok with 2FA, right?
Yes. Are you not? It's one of the most effective measures to prevent a whole class of supply chain attacks. On Github the 2FA is also flexible enough to allow non-hardware passkeys, so you can choose a privacy preserving option with good UX.
> intermittent outages
The outages have gone from "almost every Friday" to "several times per week".
...so far... but the problems are noticeably increasing in frequency, especially in Github Actions, and most of those don't show up on the status page because they are so random (eg restart the ci pipeline and it works) It feels exacty like Github is slowly rotting from the inside and I guess the reason is that everybody is forced to work on pointless AI features so there's nobody left doing actually important feature and maintenance work.
I’m sure this isn’t directed at everyone that works at GH, but it would have been more tactful to fault the people making decisions. Those frustrations are real though.
Is it really a surprise that the project that declared a blanket ban on LLM-generated code is also emotional and childish in other areas?
A blanket ban on LLM-generated code is a completely reasonable position. If someone couldn't be bothered to write the code, why should anyone else bother to read it, let alone merge it?
Not wanting to review and maintain code that someone didn't even bother to write themselves is childish?
This argument obviously makes no sense. Especially when one of the examples is a 7 character diff.
But it's fine to say "this PR makes no sense to me explain it better please" and close it.
Denying code not on it's merits but it's source is childish.
But to determine its merit a maintainer must first donate their time and read through the PR.
LLMs reduce the effort to create a plausible PR down to virtually zero. Requiring a human to write the code is a good indicator that A. the PR has at least some technical merit and B. the human cares enough about the code to bother writing a PR in the first place.
It's absolutely possible to use an LLM to generate code, carefully review, iterate and test it and produce something that works and is maintainable.
The vast majority of of LLM generated code that gets submitted in PRs on public GitHub projects is not that - see the examples they gave.
Reviewing all of that code on its merits alone in order to dismiss it would take an inordinate amount of time and effort that would be much better spent improving the project. The alternative is a blanket LLM generated code ban, which is a lot less effort to enforce because it doesn't involve needing to read piles and piles of nonsense.
> Denying code not on it's merits but it's source is childish.
No, its pretty standard legal policy actually.
I think most people are in complete agreement.
What people don't like about LLM PRs is typically:
a. The person proposing the PR usually lacks adequate context and so it makes communication and feedback, which are essential, difficult if not impossible. They cannot even explain the reasoning behind the changes they are proposing, b. The volume/scale is often unreasonable for human reviewed to contend with. c. The PR may not be in response to an issue but just the realization of some "idea" the author or LLM had, making it even harder to contextualize. d. The cost asymmetry, generally speaking is highly unfavorable to the maintainers.
At the moment, it's just that LLM driven PRs have these qualities so frequently that people use LLM bans as a shorthand since writing out a lengthy policy redescrbiing the basic tenets of participation in software development is tedious and shouldn't be necessary, but here we are, in 2025 when everyone has seemingly decided to abandon those principles in favor of lazyily generating endless reams of pointless code just because they can.
Brandolini's law
Usually I hate quoting "laws" but think about it. I do agree that it would be awesome if we scrutinize 10+k lines of code to bring big changes but its not really feasible is it?
I don't see how the two are related at all. A blanket ban on LLM-generated code is at least arguably a reasonable policy.
> A blanket ban on LLM-generated code is at least arguably a reasonable policy.
No, I don't think it is. There's more nuance to this debate than either "we're banning all LLM code" or "all of our features are vibe coded".
A blanket ban on unreviewed LLM code is a perfectly reasonable way to mitigate mass-produced slop PRs, but it is not reasonable to ban all code generated by an LLM. Not only is it unenforceable, but it's also counterproductive for people who genuinely get value out of it. As long as the author reviews the code carefully before opening a PR and can be held responsible, there's no problem.
Banning all LLM code doesn't mean they see things in binary terms like that. There is nuance between "all code must have 100% test coverage" and "tests are a waste of time", for instance, but that doesn't mean a project that adopts one of those policies thinks the middle ground doesn't exist.
A blanket ban is really the only sensible thing to do so that no time is wasted for both sides (contributors know upfront that there's no point trying to get an AI-generated PR accepted - so they won't waste time creating one, and project maintainers don't waste time reviewing what might be broken AI slop - even if some AI generated PRs would be acceptable from a quality point of view).
When there's a grey zone then there will be lots of pointless discussions like "why was this AI-generated PR accepted but not mine" etc etc...
Perhaps you misunderstood my comment. I'm not advocating for vibe-coded AI-generated PRs, and I do think that blanket banning them is pretty reasonable for the reasons you stated.
However, I don't think that banning all AI-generated code is reasonable. Having an LLM generate a couple of functions or a bit of boilerplate in an otherwise manually coded PR should not invalidate it from being accepted if it's helpful.
Given my own experience working on compiler stuff with LLM, I'd say it's a very good decision.
LLMs jump at the first opportunity to use regex for EVERYTHING instead of doing proper lexing/parsing, for example. You need to repeatedly tell it not to use regex. In the end you might as well hand write your code, because you actually know how it works, unlike a clueless LLM.
No wonder they moved to Codeberg. Those kinds of projects tend to do the ol' move to Codeberg for whatever reason. If I had to put an analogy to it, Codeberg is like Kick and Github is like Twitch.
Purity testing. I mean, one of the first lines in their announcement is relating to politics.
You know what else isn't cool? Working at GitHub!
More seriously: I probably wouldn't have called every single current employee of GitHub a "loser", but more because I think truly cool people don't define themselves by where they happen to work at any given time. I'm sure the vast majority of people at GitHub are just tech employees trying to earn a living and don't particularly care whether the Zig guy thinks they're cool or not. What actually matters is that GitHub is a big centralized platform run by Microsoft for their own ends, and it's good to be free of it.
Oh no! Not the poor Microserf drones! I will play a dirge on the world's smallest violin while they count down the days until stock vesting.
Holy shit, some people in the Zig community are toxic af. By extension, this means the community itself has issues it needs to face.
Not only have some of these folks - including the creator - been shitting in Rust threads, but here they're in here shitting on the awesome engineers at Github for no reason at all.
Good god.
edit: this is written by Andrew, the creator. The culture is rotten from the head.
Their "VP of Community" wrote this in 2020: https://kristoff.it/blog/addio-redis/ I didn't come across it until 2022. Still, particularly that and other writing from him and others convinced me the Zig community is full of goobers. That's not so bad, I have my tastes in immature humor and can sometimes be a goober too, but the application in that post's clearly-marked over-the-top skit still is just bizarre and doesn't encourage me to interact with them. To be more fair to the author and the community though, especially with respect to this GitHub migration, his more serious writing is better: https://kristoff.it/blog/the-open-source-game/ (2021). Some nice things said about Rust and the Rust community, even. In that he outlines a core position of "software you can love" being what he wants to create and inspire people to create, and how tents like "big tech" and "open source" don't really cater to that. The migration off of GitHub is predictable in the sense that GitHub stopped being something a lot of people loved a while ago -- of course some still love it, this tent creates obvious tension. (Though I don't know that Codeberg is any better and worthy of love. A few libraries I use have migrated to it and it seems fine at least, though them using Anubis is annoying and I've gotten the fail page of "Internal Server Error: administrator has misconfigured Anubis." a number of times. It does not spark joy in me.)
someone called some indeterminate anonymous corporate group of people who actively participate in enshittification of a product “losers”. you call that specific private individual “rotten”.
i’m really twisting my finger at the temple here.
You have accused me of "shitting in Rust threads". Do you have any evidence for this libel?
[flagged]
I can't imagine being someone like Andrew, or any BDFL of a popular open source project, and having to deal with folks like this. Imagine posting a timed output of your compiler on a thread about a similar language's slow compiler and having someone cite this as bad behavior.
Anyway, the clear absurdity of this particular post aside, it's not OK to call other people monkeys. I make no statement on the quality of their engineering. But they're people! I'd hope to see a quiet dignity from the Zig folks here. They've done so much excellent work, and I'm sure it's frustrating to see what software can be and then have it sharply laid against what software often is. But kindness is always the way.
Thanks to everyone involved with Zig for their work and love of software!
> Imagine posting a timed output of your compiler on a thread about a similar language's slow compiler and having someone cite this as bad behavior.
That was the entirety of the contribution. It was gloating. And there is a long history of this.
There's open source contributions, and then there's this.
> Anyway, the clear absurdity of this particular post aside, it's not OK to call other people monkeys.
You don't see how the two are related?
It's completely fine for someone working on a programming language that is useful for some of the same things as Rust to compare that language to Rust, including in ways that make the language not seem as good. Indeed, this is useful information for someone who is using Rust and is considering using Zig (or vice-versa), or who is new to both languages and trying to figure out which is better for their use case.
You seem to be running a lot of interference in this thread.
In what way is the tone of the linked messages appropriate?
In what way is the tone of the linked messages not appropriate? Rust is a programming language, not a sacred object. It's fine to say that a different programming language does something better than it, regardless of whether or not you're the developer of that language.
To be clear I like Rust and use it frequently and have for about as long as it's been publicly released, whereas I have only played around a little bit with Zig and I suspect I won't like it as much as Rust even when it's feature-complete. But I don't like seeing an attempt to enforce a social norm that it's wrong to point out shortcomings of Rust, especially when it's aimed at people doing the interesting and valuable work of exploring other areas of the systems programming language design space that Rust is not doing.
[dead]
[flagged]
I'm not sure that your unsupported assertion represents a substantive contribution to this discussion. Why do you believe it's not cool, munchler?
It's bully behavior.
It reminds me of the creeps in school that punched me, shoved me into lockers, tried to assault me.
I almost killed myself as a kid because of bullies. Some people never grow out of that, it seems.
Ziglang is a small organization supported by donations, Microsoft is one of the largest companies in the world. If anything, they're punching up.
Calling people losers isn't classy, but if I were a well-paid Microsoft employee I'd laugh all the way to the bank that some community funded purist called me that. If it's supposed to be bullying he isn't very good at it.
Hmm, that seems plausible, yeah. It's unfortunate munchler didn't say something like that. But it seems like now people on HN are dogpiling on this Andrew guy? I imagine he'll feel the same way reading this thread, won't he? Surely there's a solution for bullying other than more bullying?
Regardless, it's hard for me to imagine that many readers will find great intellectual interest in a long thread about what a terrible person Andrew is.