Computer terminal

GUI, such as like Chrome, Finder, any Google Drive, that's all GUI that has a user interface that you can actually look at and go, ah, that file is this.

Whereas Terminal, it's just text on a screen and it looks scary and it goes really fast and it fills up the screen and you got to scroll and you got to like, how do I copy paste? Lots of that stuff.

Lots of that stuff.

And this is something I've been picking away at over time.

And everybody was like, whoa, this is too much.

They saw Terminal and they were like, I don't even know what Terminal is.

I don't know how to do that.

Define

Terminal for everyone listening.

So Terminal is kind of, I don't know if some of the old-timers out there remember like DOS or DOS Shell on a Windows computer, but it's kind of the backup, kind of like this is where you enter prompts for your computer type thing.

It's on every Mac.

You go up to the top screen and you just type in Terminal and it will come up as a black screen where you can kind of just put in stuff.

Oh, got it.

Like iTerm and Terminal.

Don't get me

wrong.

But the...

Sucks strong.

They don't work the way that I would like the Terminal to work.

And so they just thought, well, okay, that's like a big... opportunity to get a bunch of developers as users and then for venture-backed companies they're like there is a little bit of like well if we can do that we'll figure out how to like monetize it um they like that it was kind of non-obvious right like

And it's a true shell script.

So it's printing stuff in Terminal.

I kind of tell you how much I dislike working in Terminal.

I don't like typing specific commands.

I always mistype something, and that doesn't work.

They came out, they made their announcement around code context.

It was bigger than just an announcement about context of code, bringing context to your code base, but they tied it into thinking about it as a more multi-step, process, how it ties into Robo, how it ties into IDEs, how it ties into Terminal, how it ties into Jira.

So it's not a feature per se, but it's a capability that is enabled through all these other products, right? Because you're not going to go in and say, well, let me look at the context of my code.

That's going to be embedded within other tools, right? Right.

Cato Network says attackers are buying sponsored search results and using Google Sites to push a fake Codex download for people searching for the Codex macOS download.

The page impersonates OpenAI Codex and uses a ClickFix-style trick that pastes a command into Terminal.

That command decodes a URL, pulls shell scripts, and strips macOS quarantine attributes.

Cato saw overlap with an Atomic macOS stealer, also known as Amos Delivery Framework, but says that doesn't prove the final payload was Amos.

Um, it beats paying for a big Photoshop license.

Terminal.

I, I live in Terminal.

Um, that's part of the programming and the AI infrastructure that I'm building, so I've got six or seven Terminal windows open.

Mm-hmm.

Um, I also like to use the QuickTime Pro app.

104.

Unleashing Your Terminal Superpowers.

A fun bash scripting tutorial dive into the exciting world of bash scripting and learn how to automate tasks, manage files, and navigate your system like a pro.

This beginner-friendly tutorial 105.

How do you get over the initial difficulties? There's a few ways you can do this.

My favorite is to just go to the language or technology official documentation that will tell you exactly how to set up step by step.

Alternatively, you can dive into internet tutorials, why do you think platforms like YouTube, Quora exists? But recognize that sometimes they are aimed at already proficient programmers, who know what OOP and GitHub are, and are fluent with writing commands into Terminal.

If you get one of these, you can try to follow it, but don't feel bad if you screw it up.