Jtsummers

> But avoiding the word artificial isn’t completely random.

Maybe not completely random, but it is pretty stupid. It's not a scary word, not unless you're afraid of nearly everything around you in modern society. Every bit of technology and construction around you is artificial.

People have artificial valves put in their hearts. Artificial retinas are a developing technology. Artificial joints have been a thing for decades. Homes have artificial stone and wood, for facades and flooring and other things. Rings have artificial diamonds. So scary.

At present, they don't learn and adapt. New models can be created to incorporate new information and new capabilities, but an existing model is a static object. It's not living in any meaningful sense.

If models updated themselves based on feedback, then it'd be different. But they don't.

> how is it legal exactly?

There's, apparently, no law making it illegal. Which is how most things that are legal are legal. What are you confused about?

Who is scared by the word "artificial"? In context, it just means man made. Your car is artificial, it is not natural, does that scare you too?

And it's not like this is a new term, it's been used for 70 years now.

You gave your agent access to your system with your permissions. Then you asked it to do something that you can do with your permissions, and it did. You don't want it to do what it can do, but instead of doing the correct thing (don't give it your permissions) you want to add a million and one rules, that will never be complete, restricting its access.

The correct thing, and this isn't hard, is to give it a different set of permissions than yours. Do not let it get into your .ssh directory at all, problem solved. People keep posting these stories as if there's something useful in them, and there is:

The moral of the story is don't be a fool. Give your agents different, restricted, permissions, than your own permissions.

This is the same approach when working with people. Your agent should be, from an authentication and authorization perspective, treated like any other employee: Given an appropriate set of permissions to their needs, not root level access to all your systems.

It prints by curing a resin instead of heating and forming plastic. They've been around in industry for decades.

Per dang in many previous comments, it's not a dupe. Multiple submissions of the same topic are fine, it's only (maybe) a dupe when a discussion starts or it's actually the same submission. You linked to a submission with 0 comments submitted a whopping 15 minutes earlier. This one is the one that got traction, neither is a dupe. If someone submits it again, now that there is a discussion, or submits the same Wired article, then those would be dupes.

If you open the file and execute:

  M-x elisp-enable-lexical-binding RET

It will add a cookie (lexical-binding) to the top of the file. If you want to do it manually put this:

  ;; -*- lexical-binding: nil; -*-

or this:

  ;; -*- lexical-binding: t; -*-

at the top of your custom.el file. They want it to be explicit now because eventually lexical will be the default. If you put in the former then when lexical becomes the default, the file will still use the current dynamic bindings. And if you use the latter, if there are issues you'll discover them now before the default changes and you're surprised by it.

The only expression I have gotten was something like "Why not vim?" and my response was "Because emacs is better, and I can always use evil-mode if I want the vim bindings". Then it gets installed (by me or an admin) and I use it. I can't imagine anyone actually caring, that's pretty petty of them, or lazy based on your other comment about it being too much work for sysadmins.

> I believe, Emacs is considered unprofessional in a lot of places?!

Why would it be "unprofessional"? It's an editor. I've used it in every job since I left college 20+ years ago.