what happened is the programmer made assumption based on the illusion created by the libraries: writing application on arduino is just like using a library on a unix-box. (which is not correct)

That is why I have become carefull to promote tools that make things to easy, that are to good at hiding the complexity of things. Unless they are really dummy-proof after years and decades of use, you have to be very carefull not to create assumptions that are simply not true.

I know where you’re coming from. And I’m not saying you’re wrong. But just a thought: what do you think will prevail? Having many people bash together pieces and call in someone who understands the matter only about things that don’t. Or having more people understand the real depths?
I’m afraid that in cases where the point is not to become the expert, first one will be chosen as viable tactic

Long time ago we were putting things together manually crafting assembly code. Now we use high level languages to churn out the code faster and solve un-optimalities throwing more hardware at the problem until optimizations come in in interpreter/compiler. We’re already choosing the first one

Apparently new NVIDIA open source kernel module has the same performance as propietary so I’d fall back on the data from this and decide based on that

Some tools for fan curves etc might be still a little bit unpolished for NVIDIA, maintainers had a lot more time to fix them for AMD. But there are many NVIDIA users out there so I’d wager on the biggest issues being addressed rather sooner than later

Well, you have configuration and flag options to define what is it supposed to be trying to use. What order, I think too. But definitely understanding SSH a little bit will make the log more understandable. As with everything tbh :D

The whole point of ssh-agent is to remember your passphrase. If you don’t want to do that your problem might be that for some reason ssh client doesn’t pick up your key. Try defining it for the host

Also, there’s -v flag for ssh. Use it to debug what’s going on when it doesn’t try to use your key

That can become an issue but IMO the person in your example used the tool wrong. To use it to write the boilerplate for you, MVP, see how the libraries should be used sets one on the track. But that track should be used to start messing with it and understand why what goes where. LLM for code used as replacement is misuse. Used as time booster is good. Unless you completely don’t want to learn it, just have something that works. But that assumption broke in your example the moment they decided to add something to it

I have a very “on hands” way of learning things. I had in the past situations when I read whole documentation for a library back to back but in the end I had to copy something that somehow works and keep breaking it and fixing it to understand how it works. The part between documentation to MVP wasn’t easier because I’ve read the documentation
For such kinds of learning, having an LLM create something that works is a great speed up. In theory a tutorial might help in such cases. But it has to exist and very often I want something like this but… can mean that one is exploring direction that won’t address their use-case

EDIT: A thought experiment. If I go to fiverr asking for a project, then for another one, and then start smashing them together the problem is not in what the freelancers did. It’s in me not knowing what I’m doing. But if I can have a 100 line boilerplate file that only needs a little tinkering generated from a few sentences of text, that’s a great speed up

Illusion — Why do we keep believing that AI will solve the climate crisis (which it is facilitating), get rid of poverty (on which it is heavily relying), and unleash the full potential of human creativity (which it is undermining)?

Because we keep reading sensationalist advertisements presented as articles instead of experimenting with it ourselves, understanding what it is

And unfortunately, this article is also just a response to media clickbait, not a discussion point it tries to look like

~20 years ago:
“Reading documentation is for wimps! Real programmers read the source code directly”

LLMs are just a tool. And meanwhile our needs and expectations from the simplest pieces of code have risen

does it also include ‘high-level’ concepts like windows, input fields and so?

AFAIK MC uses ncurses for GUI. So I while I don’t know if it has the concept of non-modal dialog, for example, for sure it has dialogs, fields, radios, boxes, etc

I think it will depend on what exactly is in the PDF. If these are text, you can in a pinch just copy and paste it but I’d expect libreoffice to be able to open it. If these are images, you’ll have to use some OCR

wrote a library in BASIC for screen / window applications in DOS. (you know, pop-up text-windows and so on). How do I do that on linux (in C)?
(…)
I know there exist things like QT and ncurses

So it’s graphical interface we are after or text based?

For text, I agree with others, ncurses

For graphical

• pyGTK
  basically everything you need, some learnig curve as it’s big and versatile. But to be honest, when trying to achieve something I’d suggest to start from GTK reference to me it somehow conveys the logic better than the PyGTK reference
• Kivy
  haven’t used it, but might be fun to use
• wxWidgets
  very cross-platform. Not only you can use it to write UI that will require minor fixes to have the same code for Windows and Linux at the same time, you can also tell it whether the toolkit used under the hood on Linux should be QT or GTK
• Tk
  old, simple (more fancy things need some gymnastics) but simple (easy to use) and supported in Python out of the box (you don’t even need to install anything)
• QT
  I’m putting it here just for fairness. I don’t like it, don’t like its signal-slot design, I think it’s hogging up too much resources. But last time I used it was ~10 years ago and in the end, it does in fact work