HNHacker News
TopNewBestAskShowJobs

jwpapi

874 karma · joined May 31, 2022

submissionscomments
jwpapi··on Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
Thank you put my gut feeling that I had in my top comment here in words. I didn’t have the full explanation ready, why this threw me off.
jwpapi··on Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
Jarreds Twitter is a Claude Code Billboard
jwpapi··on Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
> I am so tired of worrying about & spending lots of time fixing memory leaks and crashes and stability issues

There are legit reasons to rewrite a program in a better fitting language, but as a runtime to be "tired of worrying about & spending lots of time fixing memory leaks and crashes and stability" is really borderline to me.

Also there are way more things to it than just compile time and tests: you reset mental model and will lose contributers. There is philosophy, developer skill and more attached to a language.

In this case both compile via LLVM the same and there is no performance benefit given the code is written exactly the same, so it’s developer preference, where the current head seemed to prioritize his own DX over everyone else’s.

But again this is mainly my gut feeling. I’m not the first dev that doesn’t like the way bun changes : https://news.ycombinator.com/item?id=48011184

jwpapi··on Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc
Completely unbased, but I don’t want to have to do anything with bun anymore. It’s just a gut feeling, but I don’t trust them and support them.

They fork Zig to utilize LLM rewrites and build something the Zig team clearly disregarded (non-deterministic compiling)

And now like a whiny baby they LLM rewrite to Rust. There is a very real chance that Zig design philosophy got them to the point where they are now by enforcing to make the tough but precise decisions and the Rust rewrite is the start of the downfall.

It’s purely politics-based not technical, but it seems like bun is full on pampered by Claude. So much that I wouldn’t wonder that the next marketing piece of Anthropic is. Claude Mythos rewrote leading 950k LOC JS Runtime to Rust.

jwpapi··on Cloudflare to cut about 20% workforce
a new level of ad hominem
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
You getting swindled into over-engineering.
jwpapi··on Building for the Future
https://polymarket.com/event/another-critical-cloudflare-inc...
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
I had Ulnar Nerve issue, but I’ve changed my setup and it really helped. I don’t have any problems anymore.

It took quite some time to figure out what works and what triggers it. However I don’t know it’s the same for RSI.

I’m grateful for the ability to use speaking as a second option, but utilizing both I can’t cope that speaking is even remotely close to typing :/

jwpapi··on The bottleneck was never the code
Most of the time it can’t it can write 1000s, but its not good in finding the best 10s.
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
Average speaking speed for english speakers is 100-120 wpm for complex topic. I type 130wpm peak and I have the most common coding characters on my home row using neo layout.
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
I use AI to look things up and I try to learn. That part is speed up, but once I know how X works I’m faster doing it myself. My assumption is that most people seeing things differently, compare their performance of not knowing how X works with Claude, but not with someone who’s really good at X. Which makes a lot of sense given LLMS are prediction generators. My take is that the best use of AI is to get you to the point where you are really good with X and then naturally your AI usage will go down.
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
Ad hominem
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
Yeah I can and I’ve done it and for fun project it’s fun and cool. But its like using templates to build your website. You’ll be annoyed and at one point your project goes in the endless graveyary of abandoned projects
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
Till it has explored the codebase, asked me follow up questions, suggested the code change, incorporating my fixes after losing time on context switch + the extra time I need when somebody requests a change in 3 months to learn the mental model. I’m way faster to just write it myself (mental model included)
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
I use Jetbrains features for that usually, it has great tools for that.

Lets say on that JSON API I want to extract part of the logic in a repositiory file i CTRL + W the function then I have almost all of my shortcuts with left alt + two character shortcuts. So once marked i do LAlt + E + M for Extract Method then it puts me in a step in between to rename the function and then LAlt + M+V for MoVe and then it puts me in an interface to name the function.

Once you used to it its like a gamer doing APMS and its deterministic and fast. I also have R+N (rename), G+V (generate vitest) Q+C(query console), Q+H(Query history) and many more. Really useful. Probably also doable with other editors.

jwpapi··on The bottleneck was never the code
Needing focus to think is not the same as needing focus to write code..

It can take a whole day to find 10 good lines to write.

jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
I don’t want every verb implemented, I also dont want an IETF standard. I want as little as possible, so I have to worry about as little as possible in the future.

Use-cases differ, you described a complete REST API, which can be as much of a problem as a too little.

jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
Like writing code to me is not slower than writing text?

When I write code every character I type in my computer has less ambiguity than when I write it in human language? I also have the help of LSPs, Linters and Auto-completes.

jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
I hate code and I want as little of it as possible in my codebase.
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
You are speaking out of my soul. Thank you. Great example. I have grinded AI extensively 14 hours a day on my own project for months. I’ve been using AI since GPT-2.

I maxxed out Claude Max $200 subscription and before I justified spending $100/day.

And it was worth it, but not because it wrote me so good code, but because I learnt the lessons of software engineering fast. I had the exact ride you are describing. My software was incredible broken.

Now I see all the cracks, lies and "barking the wrong tree" issues clearly.

NOW i treat it as an untrustworyth search engine for domains I’m behind at. I also use predict next edit and auto-complete, but I don’t let AI do any edit on my codebase anymore.

jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
I deleted 75000 lines of code of my codebase in the last 2 months and that was tremendously more useful to by business than the 75000 AI has written the 2 months before...
jwpapi··on Vibe coding and agentic engineering are getting closer than I'd like
> I know full well that if you ask Claude Code to build a JSON API endpoint that runs a SQL query and outputs the results as JSON, it’s just going to do it right. It’s not going to mess that up. You have it add automated tests, you have it add documentation, you know it’s going to be good.

I feel like this is just not true. An JSON API endpoint also needs several decisions made.

- How should the endpoint be named

- What options do I offer

- How are the properties named

- How do I verify the response

- How do I handle errors

- What parts are common in the codebase and should be re-used.

- How will it potentially be changed in the future.

- How is the query running, is the query optimized.

…

If I know the answer to all these questions, wiring it together takes me LESS time than passing it to Claude Code.

If I don’t know the answer the fastest way to find the answer is to start writing the code.

Additionally, whilst writing it I usually realize additional edge cases, optimizations, better logging, observability and what else.

The author clearly stated the context for this quote is production code.

I don’t see any benefits in passing it to Claude Code. It’s not that I need 1000s of JSON API endpoints.

jwpapi··on Agents can now create Cloudflare accounts, buy domains, and deploy
Best thing is that they finally have an API for that, which they’ve never exposed before.
jwpapi··on Let's talk about LLMs
Its the biggest swindle...

You could fetch some unfinished github repos or download free templates. It’s actually faster than LLMs, still no body would do it.

I don’t start my project with the ecommerce nextjs starter repo. I build it from scratch, because it’s faster...

jwpapi··on I am worried about Bun
I think the motion that Claude Code and Anthropic has is trying to force-hide stuff from you. Some hopefully remember the shitstorm that happened, when they changed. Reading xxx.yy to reading 1 file or reading 2 files.

More changes like this came and they were not or very hard to configure. I understand the business idea behind it. Make them to use AI as much as possible, get the human out of the loop. More training data. More Token Usage JUHUU.

However I think that made Claude Code so much worse and so much more untrusthworthy. It’s a sneaky attempt to take away the driving wheel from you. And if you follow that logic, way more and way more things seem reasonable.

But mainly for now it just generated a lot of distrust for me

jwpapi··on Specsmaxxing – On overcoming AI psychosis, and why I write specs in YAML
And once you’ve written all these specs you realize it became so slow that it’s faster to do it yourself in editor
jwpapi··on Opus 4.7 knows the real Kelsey
Could this be just memory? Not clear it actually isn’t
jwpapi··on LinkedIn is scanning browser extensions
I’m pretty sure it’s not 99% you would wonder how many differences there are along with user-agent resolution and ip range...

I think 99% are identifiable

jwpapi··on Google plans to invest up to $40B in Anthropic
His success measurement is PRs. The success measurement I mean is increased likelihood of company succeeding.
jwpapi··on Trump fires NSF's oversight board
Thanks
← PreviousPage 7 of 15Next →