Pinned Tweet
Hey, I'm HBoot 👋
I'm a frontend developer building products on my own.
I enjoy explaining how tech works, solving real problems, and building useful tools.
I've built AI apps, Chrome extensions, and open-source plugins.
Still figuring out how to turn all this into a sustainable business.
Here I share what I build, what breaks, and what I learn along the way.
现在 SSD 越来越便宜,1TB、2TB 的硬盘已经很常见了。
但很多软件还是默认把数据存在云端,连选择本地存储的选项都没有。
明明自己的电脑有足够的空间,却还要每个月为云存储付费。
如果有同样好用的本地版和云端版,你会选哪个?
1
1
52
有时候挺好奇,为什么现在很多网站的体积越来越大了?
打开一个简单的页面,浏览器可能要下载几 MB 的 JavaScript。
各种框架、组件库、依赖包,功能还没开始用,资源先加载了一堆。
作为前端开发者,我也经常在开发效率和性能之间纠结。
6
4
227
有时候觉得,浏览器已经快变成一个操作系统了。
写文档、剪视频、运行 AI、开发代码,甚至完整的 IDE 都能直接在网页里使用。
以前装软件是第一选择,现在很多事情打开一个网址就能完成。
6
3
235
A new Docker, but a familiar story.
Today we're introducing a new look, a new focus, and a refreshed Moby.
Same Docker you've trusted for over a decade, now built to run on trust in the agentic era. We can't wait to show you.
Read the full story: bit.ly/4iX61ek
hboot retweeted
Heads up, we’re starting to test dots with a small number of ChatGPT Plus users. Looking forward to the continued feedback as we expand and I’m recently seeing a lot more positives around how good the proactivity has been after many improvements.
We’re also bringing dots to all ChatGPT Business Standard users. Rollout will start today.
体检年年做,但想知道「我的胆固醇这几年怎么变了」,还是得把旧报告一份份翻出来。换一家医院,同一个指标可能连名字和单位都不一样。
最近发现一个开源项目,叫 Mirobody。它是 Theta Health 开源的健康数据引擎(Apache-2.0),做的就是把这些散在不同地方的数据对齐。
图里是官方网页 Demo 用合成数据展示的总胆固醇趋势。Mirobody 会把不同写法、不同单位的同一项指标整理到一起,还能回查每个数字来自哪份报告。开源版也支持自部署,可以把数据和模型留在自己的电脑上。
我觉得健康 AI 最值得做的一步,是先让过去几年的报告能放在一起看。模型以后随时可以换,但整理好、能查来源的记录,可以一直用下去。
感兴趣的可以去看看:github.com/thetahealth/mirob…
🤝 Paid partnership
支持
Replying to @AnthropicAI
Your AI hates Whites & Asians, especially Chinese, heterosexuals and men.
This is misanthropic and evil. Fix it.
Frankly, I don’t think there is anything you can do to escape the inevitable irony of Anthropic ending up being Misanthropic. You were doomed to this fate when you chose your name.
The Name of the Wind.
1
3
200
hboot retweeted
I took this to heart and spent the last few hours doing another deep dive on GPT-6.2 Astra
tl;dr - things are better than when I tested, but IMO still "directionally, very bad"
I'm going to keep using the same example I've hyperfixated on since the start: "why is creating a worktree so slow?"
I had a long thread trying to diagnose perf issues while using t3 code on a particular VPS. 2 of the 3 were fast, 1 was really slow.
I asked astra outright "why is this so slow?", and it said a bunch of gibberish. I followed up with "I feel like I'm going insane, can you just tell me the cause of the slowness?"
I'll give you the answer upfront: this VPS uses a virtual disk that is slow as shit, my other VPSs have physical NVME drives that are faster.
Image 1 is from before the fixes Tibo mentioned. It shows an unnecessary graph, focuses too much on pnpm and file systems, bolds irrelevant text, and brings up ram just as much as it (subtly) mentions drive speed.
Image 2 is of Opus asked same thing. It opened with the important part in bold: "Slow disk, made worse by VDO". Ideal!
Image 3 is 6.2 Astra post-fixes Tibo mentioned. Better? Absolutely. Much more concise. Sadly, it still focuses way too much on second-order problems that are a small % of the cause. "XFS over a compression and deduplication layer on a virtual disk." - so close, but still a miss.
I think this perfectly encapsulates the problem I have with 6.2 Astra. It doesn't miss anything. It's SO thorough. But in it's thoroughness, I find it misses the most important thing: the actual point.
It wants to know everything, and then it wants to share everything. It doesn't understand what is and isn't important.
Did it say anything wrong in my screenshots? Not really. But IMO, it still entirely failed to miss the point of my question, and gave an answer that was too focused on accuracy and not enough on clarity.
In the wise words of Michael Seibel: "Most aim for 100% accuracy, and they end up with 50% clarity. Aim for 100% clarity, 80% accuracy".
Silly way of putting it, but I genuinely wish OpenAI models would lie to me a LITTLE more so I could better understand the vibe, instead of having my time wasted by all these useless details.
One of the funny reasons for the difference in vibes between the influencers and the crowd today on 6.2 Sol/Astra is that we gave a few folks access a while ago and then made a lot of changes in the last 3-4 days and I'm pretty sure no re-testing was done within those days and the videos were produced last week.
Don't get me wrong, while the models are a hefty jump compared to their GPT predecessors, they are by no means perfect and there are a few things the teams are excited for the models to get better at in future iterations in terms of taste and niceness of use. Love all the feedback and we hear you!














