Future models know it now, assuming they suck in mastodon and/or hacker news.

Although I don't think they actually "know" it. This particular trick question will be in the bank just like the seahorse emoji or how many Rs in strawberry. Did they start reasoning and generalising better or did the publishing of the "trick" and the discourse around it paper over the gap?

I wonder if in the future we will trade these AI tells like 0days, keeping them secret so they don't get patched out at the next model update.

The answer can be “both”.

They won’t get this specific question wrong again; but also they generalise, once they have sufficient examples. Patching out a single failure doesn’t do it. Patch out ten equivalent ones, and the eleventh doesn’t happen.

Yeah, the interpolation works if there are enough close examples around it. Problem is that the dimensionality of the space you are trying to interpolate in is so incomprehensibly big that even training on all of the internet, you are always going to have stuff that just doesn't have samples close by.

The problem is that self hosted apps are rarely designed to be run serverless (why would they be?) and giving each app it’a own VPS or hosted container is going to price out the self-hosted crowd, to the point where you might as well be paying for some cloud software.

In particular, self hosted apps usually are using relational databases or SQLite which need persistent disk so can’t run serverless. They also sometimes require writing to physical disk instead of object storage like S3. Writing or rewriting apps to support serverless when they have no technical need to when self hosting would make things more complicated. Most CRUD frameworks used to write self-hosted apps do not work with NoSQL out of the box.

Thing is, almost every self hosted app supports docker now and so if you like, install portainer on a VPS or NUC or raspberry pi and you’ll be able to set up most self hosted apps easily without touching the command line.

> and giving each app it’a own VPS or hosted container is going to price out the self-hosted crowd,

As far as I know, myself and other self-hosters run these sort of applications/services on home infrastructure or VPSes/dedicated/bare-metal where multiple applications usually share one instance. This could be done with docker, or cgroups, or countless other ways. I'm not sure if that's what you mean with a "hosted container" though, don't think I've heard about that before.

Yes. But that is not what OP comment is asking for. They want one-click. And request based pricing. I was explaining why request based pricing is infeasible and one-click install would price people out (because it would imply a VPS per service).

And I said the same thing at the end of my comment about the way people would host things using docker on a VPS or home server.

> Thing is, almost every self hosted app supports docker now and so if you like, install portainer on a VPS or NUC or raspberry pi and you’ll be able to set up most self hosted apps easily without touching the command line.

Why would you use a new VPS for each application? Just dockerize and put all your apps on one VPS, which is what most self-hosters do.

Because that’s not one-click setup or priced per request, which was the comment I was responding to was seeking.

And I did say at the end of my comment:

> Thing is, almost every self hosted app supports docker now and so if you like, install portainer on a VPS or NUC or raspberry pi and you’ll be able to set up most self hosted apps easily without touching the command line.

Yet, this is also the tragedy of modern software. While a fancy SaaS POS system will be fast and easy to install, the legacy local database version is going to keep working throughout an internet blackout (with cash), a power outage (via backup power) or an outage of the remote server.

I doubt anybody is losing customers over a 1s delay in the till opening or a POS server syncing the day’s transaction after close. But having worked in retail - the one time you get a call from head office is when there’s “loss of trading” - it’s a bigger issue than theft.

I remember there being an entire tourist town that was suffering economically because during peak season, the mobile phone tower was saturated and merchants could not process card payments. You can’t even use click-clack machines anymore with modern credit cards.

Now… working offline is entirely doable in a modern tech stack too - but I somehow doubt most modern POS products support it well.

The modern SAAS versions all work without internet using the client app. As we are in Vietnam, I don't think any business would ever choose a POS solution that didn't work without internet or via battery power during an outage. So there's no loss of functionality there. There are power outages around once a month, scheduled or unscheduled, not to mention storm season which has more frequent outages, sometimes for several days. So this functionality gets well tested.

All banking solutions - as well as the POS system - can work on mobile data and that usually is fine during an outage. The only time mobile data failed in recent years was after a 3 day power outage following a typhoon, when I guess their batteries failed. By that time our business was pretty much shut down due to supply issues anyway.

So basically, as long as the battery or generator lasts, all of these POS solutions will perform equivalently.

Edit: and to further clarify, I don't think there are any features that the old schools apps have that the new ones don't. Unless you consider a local database or not using a web browser as features (which is valid but not my view). While the newer ones tend to have a much stronger focus on accessibility (probably because they are basically web apps) and translation.

I would argue there is limited/no market for Database as a Service where the database isn’t hosted on the same cloud provider and region as your application. Egress costs way too much for that.

So you’d assume most people are already dealing with the AWS behemoth.

And if the cloud provider is providing a competing Database as a Service then it’s almost impossible to compete.

Egress costs are only expensive if you're paying the artificially high mega cloud corp's inflated pricing. I've yet to pay for bandwidth for any servers on Hetzner or for Cloudflare's services.

Also Cloudflare just released the GA of Hyperdrive which makes it even more reasonable to use Postgres with them. Also it's free!

Almost every library that exists will have commercial usage.

Usage will likely be skewed to small companies and agencies though. Just like every framework that optimises for less complexity, the disadvantages start to outweigh the advantages when you have so many engineers you can afford to have backend/frontend specialisation and/or you need to support non-browser clients so you need to build services that transport JSON anyway.

Side note/rant: As professionals, we should understand the limitations of different approaches, communicate them to stakeholders and select something that is appropriate for the task.

The problem is, we seem to end up with evangelism where everything thinks their square peg fits in every hole at massive cost to the people they work with/for. Train yourself to recognise this and avoid becoming “that person” that isn’t able to pick the right tool for the task.

See also:

- RDBMS vs NoSQL for everything

- ORMs vs Raw SQL

- Everything is better in rust people

- anti-GC people

- functional programming zealots

- Citizens of the Kingdom of Nouns thumping GoF design patterns at every turn

- LLMs as a solution to everything

- the many flavours of anti JavaScript camp (including, vanilla JS only, HTML over wire, PyScript/ClojureScript)

- writing a SPA for your blog folks

- micro-services vs monolith

- the anti-cloud just give me a VM/cpanel traditionalists

- cloud maximalists provisioning masses of AWS services for a low traffic CRUD site

Picking fruit would have been incredibly meaningful if you had spent the year doing the variety of agricultural activities leading up to it. There’s a reason so many cultures had harvest festivals. But now rather than a whole area getting together to literally pick the fruits of their year-long labour and celebrate we’ve optimised the process by just bringing in some seasonal workers.

I think GP means that picking fruit has a direct, meaningful impact on consumers--fresh food--whereas the positive impact of the next saas thing is indirect and often dubious.

But yeah, harvesting as a community sounds more meaningful to workers than mass fruit production does.

I think you both overcomplicate things.

Haha, yeah. I have a side story about working in construction with my dad. He was a home builder and was helping to build out a line of new apartments. It was very straightforward work -- he did the tile in the kitchen and bathrooms. I was his helper. He was excellent at it. All the buzzwords inclusive of efficiency and quality. It was fulfilling work to me and I had a sense of pride working alongside my dad. I made $10/hour, $80 a day.

Now I work in FinTech. The fulfillment is different, sometimes it's good. But I reflect on this time often. I own a small home now and my dad comes around to help me fix or remodel stuff. I'm handier now because of those experiences -- I think I do find a little more fulfillment when working with my hands. I also find myself in my garden more often which brings a little more joy than my day job. Perhaps it's just balance.

So you want all of NYC to have harvest festivals?

Those traditions and rituals are alive and well in small communities. Modern agriculture is based on the need to feed millions and millions of people. That’s why it is the way it is.

For accessibility, consider representing closeness without colour or shade of colour, maybe through a little number or something?

I think there might be too much information given away by disclosing how far away the letter is though. A more difficult mode could be just having three states:

1. Amber: Closest guess(es) so far 2. Red: Wrong guess that is not the closest 3. Green: Correct guess

So you only get new information after the second guess, assuming you don’t hit a green on the first go, and you don’t immediately eliminate most of the keyboard as soon as you are within 2-3 (haven’t quite worked out when the shading starts) characters away.

The whole point of a personal recommendation is you're introducing people you know are good to people you know and trust you. What's the value-add by inserting a new app into the process, that charges one side?

LinkedIn works because you attract supply (e.g professionals) with the draw of getting the personal recommendations/network effects for free and then make money off demand (e.g employers/recruiters) by letting them pay to win and send you spam.

Two-sided marketplace businesses are supposedly the hardest to get off the ground. Especially if you're trying to charge for something that is currently offered for free.

Thanks for checking it out! The Pro Plan is only to have unlimited profile visits, and meant for hiring managers so i'm charging kinda like linkedin sales nav.

I think the value add is that you can traverse a network of recommendations (u -> your friend -> their recs etc).

So it's a limit on displaying other profiles, not a limit on how many times my own can be. Okay.

Yeah exactly – my bad I gotta make that clear!

Why would you ditch react because you don’t need SSR? You can still use vanilla React without SSR and serve it statically. It’s not as if you’re forced to use nextjs if you want to use React.

React used to be fine when next.js was a separate effort, now Vercel hijacked the project, and making things even more complex by mixing SSR and CSR, there is a learning cost associated when things and concepts getting larger unnecessarily.

how has vercel/ssr highjacked react?

at work, our backend is c++ and we use react without nextjs or any ssr. if we don't need it, we don't use it.

the newest react is now _strongly_ recommending you start a new react project using next.js, vercel hired many of the react developers for its SSR oriented business, etc.

ok, that makes sense (i also don't like the official recommendation to use next).