Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dboon
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
121.
▲
by
dboon
10mo ago
I can't imagine being someone like Andrew, or any BDFL of a popular open source project, and having to deal with folks like this. Imagine posting a timed output of your compiler on a thread about a similar language's slow compiler
122.
▲
by
dboon
11mo ago
I have a copy. Send me an email and I’ll upload it somewhere for you. It’s not a great read, but it’s interesting in places. You can use rob.crimedoer at gmail.
123.
▲
by
dboon
11mo ago
MSVC is also completely different from Visual Studo. It’s OK to say you were wrong. You don’t have to be angry online. I promise!
124.
▲
by
dboon
11mo ago
It’s very easy to write a string library in C which makes string operations high level (both in API and memory management). Sure, you shouldn’t HAVE to do this. I get it. But anyone writing a parser is definitely skilled enough to maintain
125.
▲
by
dboon
11mo ago
It looks good! I may pick up a copy. Besides the convenience, why do you recommend your book over reading the WASM spec as you implement your basic compiler? I find that WASM has a beautifully readable spec. One of its best features! Either
126.
▲
This Ain't Yer Grandaddy's C (Tricks for Writing Gorgeous C)
(spader.zone)
3 points
by
dboon
11mo ago
|
0 comments
127.
▲
by
dboon
11mo ago
Yeah. I really like opencode, which provides an ACP.
128.
▲
by
dboon
11mo ago
It’s…a VSCode fork? Really? What has become of Google? Ten years ago, when I was getting into the world of software, there was still an aura about them. They built everything in this huge monorepo, and it worked. They were this deeply techn
129.
▲
by
dboon
11mo ago
Yes, of course. Unfortunately, sometimes you need to link to Windows binaries and therefore need to compile against the Windows ABI.
130.
▲
by
dboon
11mo ago
Nice, but if the intention is portability my experience has unfortunately been that you pretty much have to stick to C99. MSVC’s C compiler is rough, but pretty much necessary for actual cross platform. I have my own such header which has m
131.
▲
by
dboon
11mo ago
No name mangling by default, far simpler toolchain, no dependence on libstdc++, compiles faster, usable with TCC/chibicc (i.e. much more amenable to custom tooling, be it at the level of a lexer, parser, or full compiler). C’s simplici
132.
▲
by
dboon
11mo ago
The talk explicitly addresses this exact issue.
133.
▲
by
dboon
11mo ago
it sounds like you are
134.
▲
by
dboon
11mo ago
CLI tools are better about this IME. I use one called opencode which is very transparent about their prompts. They vendor the Anthropic prompts from CC; you can just snag them and tweak to your liking. Unfortunately the “user instructions”
135.
▲
by
dboon
11mo ago
It’s surprising to hear this get chalked up to “it’s the way our TUI library works”, while e.g. opencode is going to the lowest level and writing their own TUI backend. I get that we can’t expect everyone to reinvent the wheel, but it feels
136.
▲
by
dboon
11mo ago
Forking puts you in another hell as Google. Now you have to pay someone to maintain your fork! Maybe for a project that’s well and fully complete that’s OK. But something like FFmpeg is gonna get updated all the time, as the specs for video
137.
▲
by
dboon
11mo ago
to be clear that repo is simply a thin neovim plugin for the truly excellent agent TUI opencode I recommend using it directly instead of via the plugin
138.
▲
by
dboon
11mo ago
If you look at the script, this is indeed more or less what happens. Except the folks over there are very clever about ergonomics, so the script is quite long so it can detect your architecture, OS, and even libc to give you an appropriate
139.
▲
by
dboon
1y ago
well, the project in question is ghostty, which definitely qualifies
140.
▲
by
dboon
1y ago
C is really, really ripe for tooling and modern libraries. There are a lot of great ones already that don’t resemble what I’ll call university C in the slightest (i.e. the C most of us remember writing; awful, bug filled, segfaulting) I’ve
141.
▲
by
dboon
1y ago
Yeah I couldn't put it better myself. It's obscene how much more productive you become in new domains. And sure, you eventually hit a wall where you gotta understand it for real. But now you have a working example of your project,
142.
▲
by
dboon
1y ago
Same experience. I switched back to Linux a few months ago after a few years hiatus. Installed Arch and KDE Plasma. Literally didn’t even know I was using Wayland until I had to fiddle with something and realized X wasn’t even installed
143.
▲
by
dboon
1y ago
I meant that it’s bundled with the binary such that you don’t need to make sure some random version of eg Node is available
144.
▲
by
dboon
1y ago
I’ve had major Nissan Altima effect with this lately. A few weeks ago I set out to make a simple C and C++ package manager that just ignores dependency hell in favor of you explicitly specifying packages. And no binaries, just build from so
145.
▲
by
dboon
1y ago
Agree to disagree, then! Templates, smart pointers, and RAII have cost me far, far more than they’ve paid me back. You should write whatever feels good to you.
146.
▲
by
dboon
1y ago
Yeah lol I’m making a C package manager for exactly this. No transitive dependencies, no binaries served. Just pulling source code, building, and being smart about avoiding rebuilds.
147.
▲
by
dboon
1y ago
Opencode is a great model agnostic alternative which does not require a separate runtime
148.
▲
by
dboon
1y ago
Definitely, and I know this sounds like ignoring the problem, but in my experience the best solution is to just not use the bleeding edge. Write your code such that you can load it onto (for example) the oldest supported Ubuntu and compile
149.
▲
by
dboon
1y ago
That’s the first rule anyone writing portable binaries learns. Compile against an old libc, and stuff tends to just work.
150.
▲
by
dboon
1y ago
git submodule update —init
More ›