"You are using it wrong"™

I have no understanding of any of this except that Ghostty is an alternative to iTerm2. Can someone do a ELI5 for the uninitiated?

Ghostty is a terminal like iTerm. This compiles it so it runs in the browser directly, or browser-based environments like VS Code or the Hyper terminal. Without that you’d have to reimplement a whole terminal in JavaScript. Which is what people have been doing with via the xterm.js project. Naturally, there is effort and bugs that go into maintaining a clone/port like that. This lets you use the Ghostty terminal code directly - compiled to WebAssembly and with no other dependencies - as an API-compatible drop-in replacement

Only other relevant thing to add is that Ghostty is also written in zig and makes for a good showcase of the language.

This runs in the browser, so it would allow you to connect to a server from your browser and render normal terminal commands in that environment

For instance if you're a cloud provider, and you want people to be able to "drop in a shell" on a machine, but make that available through the web, you could use this

That actually pretty much is the ELI5. Its merely a different terminal that offers more features than iTerm2 and also runs on OSX.

Unless you actually need/want those features (which, although I am a terminal aficionado, I must admit are niche as fuck), pick whichever terminal makes you happy. Features that are important to some people are performance, Unicode support, and OS support.

The most decidedly non-ELI5 feature comparison: https://www.jeffquast.com/post/state-of-terminal-emulation-2... and https://ucs-detect.readthedocs.io/results.html

You could argue whether or not it's a "feature", but one of the thing ghostty claims as an advantage is the out of the box configuration.

With no config at all, ghostty looks nicer than my alacritty setup. The rendering is just real nice. I could probably get alacritty to look as nice or nicer, but ghostty just worked this way with no config needed.

So you could consider aesthetics and rendering quality, and simplicity of setup both as features, which people may need/want (or not).

I wouldn't argue against that at all: OOBE is absolutely a feature.

Problem is, we don't all agree with what the OOBE should be. I, for example, always strip out menus, tabs, and other UI features. For me, the terminal that requires the least lines in the config file is probably going to be the winner (assuming no unfixable defects that effect me).

I also have ton of questions. Hopefully the author can add more documentation to ghostty. Right now I don't fully understand the use cases or how people may benefit from ghostty.

I have been using Foqos app since a month now and it’s been amazing on my iPhone. You can create a block list of apps and when you start “Foqos” those apps will be blocked. You have to unblock before using those apps. But here is the best part. The unblocking can be configured such that it does only when you tap on a NFC tag. I spend a lot of time on the phone as soon as I wake up. So I have been blocking before sleep and keeping the NFC tag in the garage. Amazing setup for me.

This app I assume is exactly like the more mainstream Brick app but this app lets you configure any off the shelf NFC tags which you can get under $5.

Also, one of the highest taxes.

So what?

Their model obviously works well.

Custom feeds really intrigue me. If I understand the API right, if you are an implementer of a custom feed, you need to expose an endpoint that the bluesky server can hit whenever a user wants to load content for that custom feed. And the endpoint that you implement will return the results. Does this mean that the implementer of this feed will have to take into account the network costs? What I am trying to get at is that if you implement a custom feed, you need to be aware that you are potentially looking at hitting your data caps on your internet provider if a lot of folks start consuming that feed. Do I understand this right?

I am aware that there are services that let you create custom feeds. But they are mostly for simple compositions like a feed for the following set of words and/or set of people, etc.

You end up sending back post IDs that get hydrated on the server side, but yeah!

There's more complicated feeds, but right now the easy to make feeds are more prevalent because they're easy to make.

Where?

Nowhere.

I think the user has to mentally tune out the bad websites that significantly use fillers -- most "news" sites. AI summary is definitely time saved for such websites.

Well written articles deserve to be long form and not summarized as you note. But the large majority of web articles belong to the former category.

Dolce&Gabbana Casa Leopard Silk & Wool Throw - $3245.00 - Purchased

Goddamn.

Pretty sure they read

"If I can't get in, they can't blame me if something goes wrong down the road."

as

"If I can get in, they can't blame me if something goes wrong down the road."

That's the only interpretation that sounds threatening.

Ohhhhh, that makes much more sense now. If I read it that way, I'd also think I was a creep.

Yep, they confirmed it.

How exactly? His tweets (at least to me) come off extremely jealous of the fact that Apple integrated with OpenAI.