I cant get my epson ecotank et2710 to work under arch/endevaouros.

Maybe read the original blog post from the gnome dev then? The post the article references… it says right there why the ai code is a problem, it has to much unnessecery code in it and reviewing that takes time. The author also says the submitted ai code doesnt adhere to good practices.

The worst is if you select the windows repair entry, that takes even longer…or a old entry that doesnt have a valid installation behind it…

Have you read the first paragraph if the lidnked articel? It quotes the criteria right there: "Extensions must not be AI-generated

While it is not prohibited to use AI as a learning aid or a development tool (i.e. code completions), extension developers should be able to justify and explain the code they submit, within reason.

Submissions with large amounts of unnecessary code, inconsistent code style, imaginary API usage, comments serving as LLM prompts, or other indications of AI-generated output will be rejected."

Maybe instead of commenting under every comment that lines this change read the articlw first? Ai is fine if your code is fine and you uderstand it. If the reviewer has to argue with a llm because the submitter just pasts the text into his llm and then posts the output of said llm back to the reviwer it is a huge waste of time. Thiss doesnt happen if the person submitting the code understands it and made shure that the code is fine.

Ok thanks, i quiet like kde but it is very annoying to not be able to copy paste without cleanup.

Wait, is wayland the reason copy paste doesnt work and inserts weird character and brackets all the time?

I get what you mean but i still think that there isnt a difference. All the “intuitive” stuff on guis is just stuff you learn as you would learn a cli program. The discette for saving isnt intuitive most people have never held one in their hands. Media player keys? Well you dont just know that double vertical bars will pause and triangle will play. People find gui more intuitive because they already spent a lot of time learning it. Once you learn “cli” you will have the same experience when doing something new.

Typing a word into the consome is far from programming. Missclicking on a gui is far easyer than typing a whole other word than you wanted to use.

Building a pc has no bearing on what a programm does or how some software works. With win11 as a tech savy person i alwas struggle to find where to do things that i knew in the old gui. Windows isnt better because of gui. Its just that people always used it and know where stuff is. The next generation of kids that grew up on phones will not know how to do things in windows. Learning a console command is not more difficult than knowing a gui. The only hard part is knowing what program is used for what purpose, if you have no idea that pacman is your package manager you cant write pacman -h for the help text but the same is true with guis, if you dont know the icon for your purpose you cant run it. The biggest problem i see with people is that they just dont want to read something. I have people who were developing apps for/on windows before and if they get a error in the linux console they dont read it at all and just put sudo in front of it or ask chatgpt.

The last person that startet in our department and decided to go while they still can said “you can only stack shit that high…” and i think its beatifull… imagine a codebast that startet in assembly bad c code with lots of hardware specific shit and the demand to always ship features to old systems build byy electrical engineers who didnt know better.

I hope in like 10 years i will understand how all of the stacked shit works…

I work in a company that has a old codebse in c with tons of realtime intime stuff that is acessed via a shared memory from the realtime to the non realtime system. Tons of strucs get copied around then typecast to other structs and global variables all over the place. You never know where a variable is written to and where it is also acessed from or if it is just a copy. No assembly but still super obscure.

Seriusly, if you cant filter information or you are not able to react to your surroundings please dont drive. Half a second of reaction time more is a lot when you are driving a 2 ton car with 100kmh around… that si rhe reason drunk driving is not allowed or driving while high…

With embedded stuff its still done like that. And if you go from the arduino functionss to writing the registers directly its a hell of a lot faster.