Like usual the answer is it made it easy to use. Think Linux and Windows. You have a customized Linux setup kind of agent. Open claw is the easy install wizard assisted version of that that the masses can easily setup.
It's nothing new, its just the old stuff packaged together and pre-configured.
Cause it was written by AI.the entire mid section is classic AI slop writing. Repeating the same points and numbers over and over, repackaging the same idea with "key takeaway" and shit. The voice of the author is heavily AI coded there.
> I don't know, manufacturing seems to have learned pretty well that they can ship everything overseas and people will eventually accept products just aren't made the same way they used to be.
I mean this is true, but we aren't talking about the consumer here. We're talking about the industry which is to say the powerful people who own and run all these companies.
What has happened is that those overseas countries now have all the experienced engineers over there and they know it. So you see things like the Trump admin begging Korean companies to keep their workers in the US because they understand how to actually do these things. And the reason the Trump admin did that is because they owe favors to the rich people who want to profit off of factories in the US.
The causes of homelessness are plentiful. Some, perhaps a majority I don't know any exact figures, would be helped by simply giving them money. Others are suffering from mental health crises and/or drug addictions that must be dealt with first before they can have any hope of taking care of themselves when given the money to support themselves.
This is where good faith opinions can differ. Do these folks still deserve freedom/autonomy or can we force them into rehab or mental heath treatments? If the only crime they have committed is not having a bed to sleep in, I'm not sure I'm comfortable with taking away their freedoms. I'm closer than I was five years ago but I'm not universally there yet.
Hah, yes. In Australia when I was growing up there was a program called Work for the Dole (Unemployment) after you had been unemployed for a while. During the dotcom era, that was me. There was one program that was tech and web development skills. I went to a church twice a week (the organization running the program wasn't the church, they just rented rooms), and we poked at shitty old computers while I tried to help the staff figure out how to get Dreamweaver running on them (I knew more than the staff) in a way that was basically trying not to break the licensing - since they'd only bought one copy for the entire classroom. I knew more than the staff, the computers were decrepit, etc., and we were stuffed in the back room of a church.
I got to meet the "org executives" (it was really only the two of them, grifting, in the entire org) who were collecting a nice fat government check per person enrolled in their program. They came by to see how we were doing, and were there for less than 15 minutes. Two ladies in their 50s who were more interested in talking about how excited they were to be going off to pick up their new company cars after lunch, matching Jaguar XJs.
I feel like you missed the first third of this article that was quite clear they are not saying there are no uses cases. They are saying there doesn't seem to be an economic model that makes sense.
As the article itself describes, programs that expose kids to fields they might otherwise not have a chance to interact with. A field trip for kids that focuses on creating more people in the future who are interested in the field from more diverse background.
Tell me you haven't read the article (or used racket) without telling me.
> I believe that an intro course should get students coding since the first major hurdle is learning how to construct any kind of program at all. The switch to a more "employable" language isn't going to make education worse.
None of this is the issue at hand. The switch to python is because industry uses it. The article correctly makes the point that racket was intentionally designed to get students coding as easily and quickly as possible. It has multiple steps of teaching languages for exactly that purpose, introducing concepts in ways that let students grapple with them one at a time in an interactive environment.
Meanwhile in python complex topics like duck typing, object oriented methods, exceptions, the distinction between iterables and lists, how to use a command line/terminal or how to configure an IDE, and so on must be covered before people can start writing code for the exercises. Racket is streamlined for beginners.
> Meanwhile in python complex topics like duck typing, object oriented methods, exceptions, the distinction between iterables and lists, how to use a command line/terminal or how to configure an IDE, and so on must be covered before people can start writing code for the exercises.
No, they dont have to be at all. You might as well suggest you need to learn the JVM before writing a line of Java.
Python supports imperative, OO and functional programming paradigms. And to start you can use any text editor, an IDE is not required. In fact you can start working in the REPL right away, in which case you need a terminal and the command “Python”.
To quote the above person: "tell me you haven't read the article without telling me".
You thought that supporting multiple "programming paradigms" is a nice thing, but it's the opposite for teaching beginning student. Experienced programmers want expressivity/customization/choices to do whatever they want. That's not what newbies need when they get stuck on an assignment.
I think the argument the poster is making is as root cause analysis.
The root cause of the messenger failing was the missing nail. Sure it could have been many other things, but in this case it was the nail. And if it was a pitched battle that was narrowly lost by one message, sure, they could have won or lost because of a dozen other factors, but in this case it was the missing message. There are likely many other important things to worry about, but in the system as it is today, it failed for want of a nail.
Plenty of large engineering outages were because of single keystroke typos. Should these systems be less prone to human error? Of course. Are they? Some of them are, but right now some of them aren't.
The point being made is that small things can be important if other things go wrong. We should fix the other things, but often they are much harder to fix than the small thing. And really, we should care about both, since humans are capable of that.
For me, this is the moral of horseshoe nail story. It's something I preach to my team - details matter. I’ll add that unfortunately we often don’t know which details will matter ahead of time.
If you look at the problem as a swiss cheese model and not just a teleological propagation from one root cause, then there are many things that need fixing, not just a cobbler being short one nail.
reply