| ▲ | pm215 4 hours ago | |||||||||||||
If you're going to set a firm "no AI" policy, then my inclination would be to treat that kind of PR in the same way the US legal system does evidence obtained illegally: you say "sorry, no, we told you the rules and so you've wasted effort -- we will not take this even if it is good and perhaps the only sensible implementation". Perhaps somebody else will eventually re-implement it later without looking at the AI PR. | ||||||||||||||
| ▲ | hparadiz 3 hours ago | parent | next [-] | |||||||||||||
How funny would it be if the path to actually implement that thing is then cut off because of a PR that was submitted with the exact same patch. I'm honestly sitting here grinning at the absurdity demonstrated here. Some things can only be done a certain way. Especially when you're working with 3rd party libraries and APIs. The name of the function is the name of the function. There's no walking around it. | ||||||||||||||
| ||||||||||||||
| ▲ | pmarreck 2 hours ago | parent | prev [-] | |||||||||||||
You not realizing how ridiculous this is, is exactly why half of all devs are about to get left behind. Like, this should be enshrined as the quintessential “they simply, obstinately, perilously, refused to get it” moment. Shortly, no one is going to care about anyone’s bespoke manual keyboard entry of code if it takes 10 times as long to produce the same functionality with imperceptibly less error. | ||||||||||||||