Curious: Can you expand a little bit on your usage? $700/month equates to 350,000 minutes. Are you just running a truck-load of different Actions, or are the Actions themselves long-lived (waiting on something to complete)?
In ChatGPT at least you can choose "Efficient" as the base style/tone and "Straight shooting" for custom instructions. And this seems to eliminate a lot of the fluff. I no longer get those cloyingly sweet outputs that play to my ego in cringey vernacular. Although it still won't go as far as criticizing my thoughts or ideas unless I explicitly ask it to (humans will happily do this without prompting. lol)
I am going to try the straight shooting custom instruction. I have already extensively told chatgpt to stop being so 'fluffy' over the past few years that I think it has stopped doing it, but I catch it sometimes still. I hope this helps it cease and desist with that inane conversation bs.
GPT edit of my above message for my own giggles:
Command:make this a good comment for hackernews (ycombinator)
<above message>
Resulting comment for hn:
I'm excited to try out the straight-shooting custom instruction. Over the past few years, I've been telling ChatGPT to stop being so "fluffy," and while it's improved, it sometimes still slips. Hoping this new approach finally eliminates the inane conversational filler.
If true, then this usage could violate its MIT License: "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."
The file seems to have been copied verbatim, more or less. But without the copyright info
Yeah I can’t find a reason why but I’m put off and uneasy reading all this for some reason . Also the detail in this “how we built the app” article is basically… too detailed? Like a new developer who comments every line of logic in their code. Perhaps it was also generated with AI with a prompt that was looking at the codebase?
I wish them all the best but perhaps this just isn’t for me.
A lot of react native apps do not feel native. Even more are just low quality. Many v0 users were asking us how exactly we did X or Y to make it feel so good, which is what this post is for.
I like it. This post is the perfect level of detail for people obsessed about UX minutiae.
Personally, I'm not a huge Vercel fan (IMO: lots of hype, business model encourages developer ecosystem lock-in), but this post gave me more trust in the design/UX care that goes into their products (which is a core Vercel strength).
You accumulate web frameworks and maintainers similar to the winning strategy at Monopoly, until you have implicit control over entire ecosystems. Whether you actually seize that control or not doesn’t even matter, because you are in a position to do so—by strategic neglect, or increased attention to whatever project supports your current business goals best.
No single entity should have that much power, especially no venture-capital backed one.
You might want to look at the comments in this thread [1], to get a feeling of the "accusations", as you want to call it... I'm not "accusing" anything, I really couldn't care less, I don't use Vercel/Next.js and never will, but maybe you should read the linked thread, too see how people (at least on HN) see your company.
I think the fact that OpenNext can exist speaks to the opposite
A Next.js project can be deployed to a Docker image very easily [1]. If you want to use a provider that has their own infrastructure setup, then yes you need to do some work (that OpenNext does for you). But that's true of practically any framework deploying to a host that does more than just serve the docker container.
Looks good, I appreciate the level of detail especially as bad UX can cause churn on mobile. Since it's React Native, are there plans for an Android version? I guess you guys wanted to get an iOS version out first instead of releasing both in parallel, for bug testing, improvements etc?
Overall, our focus right now is iOS, but we want to do Android at some point. Even though we used React Native, we also wrote a good amount of native Swift code under the hood to power native modules.
I clicked through to the app's website, linked immediately in the writeup [1]. It slowed my browser (Firefox) to a crawl for 10 seconds but ultimately had no information whatsoever. Clicked the FAQ at the bottom, where the first question is "What is this?", which seems silly to have to address in a FAQ. But to answer you: It's a coding copilot app. No idea why you'd use your phone for this.
I tried to look at the landing page and it crashed Mobile Safari... relaunched it, scrolled a bit down, scrolling smeared rows of pixels up my viewport rather than text. It eventually redrew and reset the viewport, I scrolled some more, then it crashed Safari again.
In the spirit of not just grumping emptily, I did just get TFA to load on desktop. I'm grateful, Fernando, for the detailed dev-to-dev style here—and I admire your commitment to a high level of polish!
I wonder, though: you point out in the article—
> Achieving native feel in this area was tedious and challenging with React Native. When v0 iOS was in public beta, Apple released iOS 26. Every time a new iOS beta version came out, our chat seemingly broke entirely. Each iOS release turned into a game of cat-and-mouse of reproducing tiny discrepancies and jitters.
This feels like a treadmill of tiny rough edges that won't be going away anytime soon, especially with your (rightfully) world-class standards. And on Apple's timetable, too: it seems like each iOS evolution will likely introduce new elements of roughness, and they'll be iterating the OS through its release cycle without regard to how it interacts with your needs or workarounds. (A mental image of the winter sport of curling comes to mind)
If you were to do it all over again, would you think about building on native technologies instead? Or do the React Native benefits outweigh the native iOS UI polish, even though "we decided to share types and helper functions, but not UI or state management"?
> If you were to do it all over again, would you think about building on native technologies instead?
Although it took a lot of effort, it was a new set of UI patterns for React Native, and it hadn't really been done well yet.
Where most RN teams go wrong is they never dip to native code. On the contrary, we wrote a lot of native code, both for our own packages and for updating RN core itself.
The benefits with React Native's composition model are hard to beat. For example, thanks to React's composition with hooks and components, we will likely be able to open source most of the problems we solved into an easy-to-consume library. Or at least that's the hope!
This sounds profound but really isn’t, how about if we have to ask what it is _in a forum already specialised to those who could be interested_ then it demonstrates a serious communication issue?
The author makes it seem like we have two choices:
1) enable memory, and use ChatGPT like a confessional booth. Flood it with all of your deepest, darkest humiliations going all the way back to childhood ...
2) disable memory
Perhaps my age is showing. But memory or no memory, I would never tell ChatGPT anything compromising about myself. Nor would I tweet such things, write them in an email, or put them into a Slack message. This is just basic digital hygiene.
I've noticed a lot of people treat ChatGPT like a close confidant, which I find pretty interesting. Particularly the younger folks. I understand the allure – LLMs are the "friend" that never gets bored of listening, never judges you, and always says the right thing. Because of this people end up sharing even MORE than they would to their closest human friends.
My thoughts exactly. And even if there is some need to use the LLM for something sensitive, most platforms have some sort of incognito mode. Not that it's going to stop the government, etc. from accessing the chat, but useful for the same things you would use a browser's incognito mode for: something you don't want accessible with a basic history search
No, they wouldn’t — that’s the point of this entire thread. A catalog with 100x the pages and items would be useless, impossible to organize, and expensive to stock. The creators of those catalogs, who lest we forget, were at the forefront of their own tech revolution, were keenly aware of the limitations and possibilities of their tools.
> Framing it in gigawatts is very interesting given the controversy
Exactly. When I saw the headline I assumed it would contain some sort of ambitious green energy build-out, or at least a commitment to acquire X% of the energy from renewable sources. That's the only reason I can think to brag about energy consumption
Or this brings power and prestige to the country that hosts it. And it gives clout precisely because it is seemingly wasteful. Finding the energy is a problem for the civilian government who either go "drill baby drill" or throw wind/solar/nuclear at the problem.
