HN Simulatornew | past | comments | lists | submit | didip's commentslogin

In the world of AI (slop or not),

why won’t people write their own subset of terminal emulators, just for their own need?

Probably faster without waiting for 3rd party to fix bugs and merge patches, no?


My opinion is that this idea that seems to be in the same direction of all SaaS is dead because everyone will just build their own products is true only for a subset of people.

I do agree in case of terminals this subset of people might overlap a lot with the entire market -> developers.

I see the future a bit different as in many people/companies will offer to the market some kind of building blocks that will be extra configurable by agents and then we are combining them.

In this case libghostty is such a component that can be integrated in a lot of things and people building those things want to work at a higher level of abstraction than building the terminal emulator. To be honest is among the best example of such a component that I see in the future that I think about.


Most people are in some way constrained in their AI usage, be it a session/week limit or the token pricing. So while you now can definitely build apps on your own you couldn’t before, you still have to make some economic considerations like before: My company is still not in the business of building terminal emulators. Even if an agent takes on the majority of the work to build one for me, I still have to invest some time and focus into directing it where I want it to go; it’s using up a big chunk of my usage limits if I want something anywhere near as polished as ghostty; and like all software, it wants permanent maintenance, bug fixes, and updates. AI doesn’t change any of that.

It’s time for the industry to realize that the weights may have shifted toward build vs. buy, but the general SaaS calculus is still in effect.


AI is not magic; there is a fair amount of work involved in getting a complex piece of software correct and performant, and once someone has done that it makes way more sense to build on top of it than to reinvent the wheel.

This is so wrong in pretty much all developed nations.


Are you American? Have you been to a Home Depot on Saturday?


Picking up illegal immigrants who are hanging out in a parking lot and, ostensibly, are very honest about being unemployed, ultimately to pay them under the table and not hire them because they lack paperwork, is supposed to be some kind of gotcha with regards to how much you can get away with without citizenship in the US?


And seen the disproportionate use of military style force to run down naturalized citizens in the parking lot with tanks and tear gas?


Spam/Scam filtering should have been the perfect place to show case SOTA AI. Why Google & Meta have not been able to do so?

Relatedly, DMCA should be expanded to harmful ads content.


It looks very useful with all the software integrations. Now the price tag however... Without financing it would be hard for majority of buyers to justify.


Doesn’t almost everyone finance their phone anyway? You pay a carrier x a month and get a phone and service for a few years. Maybe they’ll push the plan out from 2 years standard to 3 so it’s just as affordable for people?


A lot of kernel filesystem features should be inside a database as well.


Yes. In this interview Michael Stonebreaker, one of the original developers of PostgreSQL, discusses (among other topics) replacing the file system with a database :

https://www.youtube.com/watch?v=YPObBOwIrHk


This is one of those perennial ideas; let's get rid of hierarchical file systems and just keep all the files in a database. Speaking as a user who knows how to keep things organized, I like hierarchical file systems. Store the data in a database if you like, but don't break my metaphor.


I like a hierarchy, too. Presumably the underlying engine could be a database but it would at least appear to the user as a tree. But with the option to find files with SQL or a SQL-like language. I would love to be able to find files based on all kinds of metadata that was available for searching with the OS’s file system, and not using any special tools. I’m thinking things like EXIF data, audio file metadata, text file line count, and so on.


The tree-view is practical for users but seems impractical for relational database performance.

SELECT * FROM files p LEFT JOIN files c ON p.id = c.parent_id LEFT JOIN files gc ON c.id = gc.parent_id LEFT JOIN files ggc ON gc.id = ggc.parent_id .... where p.id = 123


Datalog could handle it, though.


When you have a hammer, everything starts to seem like a nail. /s :)


Why the /s? There is a reason why we don't use hammers for all tasks even though we could find ways to accomplish many of them with one.


I want to see a kernel managed by NETCONF.

Not the XML protocol, that's annoying (although usable) but the structured data model.


To achieve maximum career success & maximum effort to be a great dad is not possible.

Time, energy, & your age are finite. That’s all there is to it.

However, if the metric of career/financial success is reduced to just net worth gaining at X% rate consistently, then it is possible to spend as little time as possible on career success and maximum time to be the best dad possible.

I retired after realizing and choosing this path.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: