It’s so refreshing to read an “old fashioned” dev blog post written by a human with a passion for the topic. This is what got me hooked onto HN back in the day, not the endless posts about AI written by AI. I’m only half joking when I say this was a balm for my nerd soul.
In my experience having the agent explain the code doesn’t work very well for real world apps, even the parts written by humans. For example we tried using to generate diagrams, class hierarchies, etc as part of documentation. If you don’t know the code it looks great. If you do, it’s focusing on all the wrong things, missing the mental model, and ignoring lots of important bits. And Claude tends to be extremely verbose to the point of muddling things.
All these trackers (rings, watches, wrist bands) seem so… useless. Do you really need to know your heartbeat every minute of the day? What does sleep tracking tell you, can’t you just tell if you’re tired? For athletes there are garmin type watches, which I understand during a workout. But the lifestyle trackers I don’t get the point.
I get this point of view totally, so I'll give you a different one. I pretty much wear one (cheap Fitbit) as a gentile constant reminder to do my workouts, keep active, and to increase my fitness. I also noticed that if the readiness score is very low, like single digits, I tire extremely quickly during a workout and it feels very frustrating so in that case I will give myself some extra rest. I cannot even a little tell the difference between high readiness and low readiness by the way I feel waking up or going through the day, but I also have anemia due to a genetic defect and am going through perimenopause, so not being able to tell is likely a "me" thing.
Sleep tracking isn't useful as far as trying to improve it for me, because, again, I'm in perimenopause, so my sleep is all over the place and my body just does whatever it wants. But I'm sure it is part of the readiness score or whatever.
Many of these are extremely useful/lifesaving for people who are at risk for medical reasons (cardiovascular conditions, fall detection for elders, etc.) and the lifestyle tracking features are basically extras to market the device to a wider audience and bring the price down.
I love my whoop band. Has noticeably made my day to day life happier than before I owned it. The insights pushed me to sleep much better, which makes each day brighter and less overwhelming. The insights also pushed me to up my cardio fitness metrics in general, which has made me overall more athletic and capable on strenuous hikes, trips, and activities.
YMMV but for me it might be my favorite product I own
I have my Galaxy watch linked to myfitnesspal so that calories from workouts get added to my total calorie budget for the day. It is pretty convenient.
What’s the story for Rust-C++ interoperability these days? That’s what kills adoption. Most C++ devs I know like the idea of Rust, but no one is going to go rewrite 30 years of working code. It needs to be something you can incorporate gradually.
There's an interop initiative by the Rust Foundation, there is a project goal to map the problem space, there was an effort to introduce an attribute (`#[rustc_splat]`) to allow calling overloaded functions, and there are various community-generated tools for more or less automated bindings generation.
There's a huge push for this from the big companies adopting Rust. Google has been developing https://github.com/google/crubit. The older cbdingen is still usable if more limited (it's what Firefox uses for some pretty involved interop).
Rust's raison d'être is to improve the confidence of the security-critical parts of your system. You don't need to rewrite all 30M lines of code to benefit from it, you just need to identify the 1% of your codebase with the greatest attack surface (e.g. any internet-facing string parser), cordon that part of the codebase off with a C ABI, and then convert that part to Rust. This is similar to how Firefox incorporates bits of Rust into its own C++ codebase over time (e.g. for parsing URLs).
To be fair to the committee, upgrading C++ compilers is already a chore, even with the changes as small as they are. Would you rather spend time updating your lambdas because they changed how capture works (a real breakage not long ago), or doing something of actual value? The only reason we finally updated from Python 2.7 to 3 was that the OS vendors dropped it, but it was effectively a waste of time.
That aside, I don’t understand why ABI breakage is a big deal. There’s probably a good reason, but ABIs are already so fragile, you can’t mix and match different compiler versions anyway, or even the same compiler with different flags. Why does it matter if setting -std29 or whatever breaks ABI when -fno-rtti does the same?
The C++ committee should really stop adding esoteric features for library writers and focus on stuff for normies. Tooling is one as the article says, or how about finally getting Networking TS? This is probably the only mainstream language left that doesn’t have even basic networking support.
> Why does it matter if setting -std29 or whatever breaks ABI when -fno-rtti does the same?
I think it's the distinction between can and must. Right now you can preserve ABI across compiler versions if you want to (and that is indeed a desirable quality for some users). The pushback is against changes to the standard that would require an ABI break.
I spent quite a while trying to learn Common Lisp and I really wanted to like it, but I’m not sure I’d recommend it. The first problem is finding good learning materials, as most are out of print. On the language side people complain about the parens, which turns out is no big deal. There’s a lot of other weird or needlessly tricky stuff though. The function names are convoluted (e.g. there’s map, but also mapc, mapcan, mapl, maplist). Image based development was interesting, but you might waste an hour debugging because your image diverged from the actual code. Building an actual executable is more complicated than you’d expect, and there’s a lot of magic with packages. There’s some elegance there if you squint, but other lisps are probably better.
I now generate ALL of my hobby projects in CL (SBCL on windows). I tell the LLM to 'over-comment' the code, so I get to learn as I read the output. It has been glorious. I generally use the web browser on an unused port on localhost for user IO (beautiful pages), and the app just hooks to Hunchentoot to serve.
Any 'real' programming language (meaning, one that is truly general purpose: numeric stacks, Web front and back ends, system code, utilities, etc) will always have some cruft. In CL, at least you can understand why some cruft exists. And you get used to it, because it's not like e.g. C where there are some very dark corners indeed. Check out Peter's book!
CL lets you build real apps, for real. No toys. This has value.
CL was recommended to me here. I had only played with Scheme over the years (SICP and Little Schemer - which, I used to recommend to every engineer that answered to me). I quickly bought Practical Common Lisp in hardcover (used). The language has a LOT to love. But it's caused me to go back and revisit Scheme(s). I put down my CL book to look at The Scheme Programming language and Chez Scheme. Going through all of this without an LLM has restored some joy. But I can understand reluctance to use this unless I could assemble a team with a ton of knowledge. Prompting for Lisp sounds like fun. But not having the deep understanding means I'd be blindly accepting its suggestions. I can't say what Lisp would be better. Clojure maybe?
Common Lisp is unfortunately a merge of multiple competing Lisps from the time period, much like Unix (SysV and BSD stuff). It was probably reasoned that a messy, imperfect standard is better than no standard or a restricted standard that is useless without proprietary extensions and requires constant revisions by a standing committee. There are good reasons to deviate from it and come up with a cleaner Lisp, but people better learn all the lessons Common Lisp has to offer before they do so.
Yeah, one of my learnings that took a bit is that as much fun as learning the classic lispisms like car/cdr/cadr/cadar/caadr/etc was, with their long history and particular "early punchcards typing efficiency" at some point it is useful to learn the newer sides of the language that could afford entire-words and cool modern DSLs like loop.
My push into Common Lisp was a current revision of a classic AI textbook that mixed up usage of nearly the complete history of lisp because some of the examples presumably dated to the 1960s/1970s with moderate adjustments to make sure that they still compiled in SBCL or the like, so it was a natural lesson from that textbook. Maybe not the best way to learn Common Lisp, but that was an interesting semester for me. (I and the few other people in the class that semester decided to learn Lisp by choice for the class and I think I was the only one to also decide "I'll do every assignment with implementation language choice in Common Lisp this semester", which was most of my classes, just to keep grad school interesting.)
reply