Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
glouwbug
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
151.
▲
by
glouwbug
10mo ago
These tools do two things: 1. Rob one’s understanding of the design and implementation 2. Give the unqualified enough confidence to contribute
152.
▲
by
glouwbug
11mo ago
Sometimes the real deliverable is a happy team
153.
▲
by
glouwbug
11mo ago
Things really felt great 2023-2024
154.
▲
by
glouwbug
11mo ago
Django also missed a couple fingers ;)
155.
▲
by
glouwbug
1y ago
I’m writing my own internal combustion engine simulator with some applied CFD. Nothing public yet but the sound is nice in my opinion: https://glouw.com/2025/10/12/Ensim4.html
156.
▲
by
glouwbug
1y ago
If you'd like to define the backend like this, it's the easiest way to compile to C; we're just repurposing C as a general-purpose assembler: https://glouw.com/2023/11/07/Switch.html I believe
157.
▲
by
glouwbug
1y ago
I believe MIT Scheme compiled directly to C by intermingling switch statements and gotos to emulate its call stack. Problem was, as programs grew, compile times weren't linear. I gave it a shot once, it was a somewhat spiritual experie
158.
▲
by
glouwbug
1y ago
I mean, neither is gonna generate money
159.
▲
by
glouwbug
1y ago
The stamp is legally binding. The company you work for isn't gonna protect you financially if the bridge you stamped falls. This is how they protect their profession https://en.wikipedia.org/wiki/List_of_data_breac
160.
▲
by
glouwbug
1y ago
It is in many fields. They're Professional Engineers, and they build nearly everything that's important to a society. Software is overrun by literally anyone and everyone because it's not a protected field of engineering
161.
▲
by
glouwbug
1y ago
This is funny, because my personal view is that AI’s biggest pitfall is that it allows the unqualified to build what they think they’re qualified for
162.
▲
by
glouwbug
1y ago
The Practice of Programming by Kernighan and Pike had a really elegant Markov: https://github.com/Heatwave/the-practice-of-programming/blob...
163.
▲
by
glouwbug
1y ago
I think this is the most apt summary of LLMs I’ve seen to date
164.
▲
by
glouwbug
1y ago
High interest rates bring layoffs. Layoffs require performance, or at least perceived performance
165.
▲
by
glouwbug
1y ago
In the age of high interest rates everyone is pushing quantity over quality
166.
▲
by
glouwbug
1y ago
The massive productivity gains I’ve seen come from multidisciplinary approaches, where you’d be applying science and engineering from fields like chemistry, physics, thermodynamics, fluids, etc, to speedy compiled languages. The output is i
167.
▲
by
glouwbug
1y ago
Data structures like maps and vectors from the standard library are still incredibly useful and make a fantastic addition to C if your focus relies on POD types, though if real time performance with heap cohesion is a problem then you’re ri
168.
▲
by
glouwbug
1y ago
Very cool. Thanks for the link. I like to print physical copies of neat finds like this, and will be doing just that
169.
▲
by
glouwbug
1y ago
Yeah Navier stokes accounts for continuity over Burgers' which elevates you from what might be conventional game-dev like water to ANSYS grade CFD. Although, realistic CFD has its tradeoffs too. Solvers like LF, HLLE, and HLLC all offe
170.
▲
by
glouwbug
1y ago
Curious if you can get away with Burgers on a CPU: https://youtu.be/oxzfY-hPt2k
171.
▲
by
glouwbug
1y ago
Use what you need to solve your problem. Learning frameworks never made sense to me
172.
▲
by
glouwbug
1y ago
But I'm not writing code. It's research with iteration. Punching out manual CFD is time consuming
173.
▲
by
glouwbug
1y ago
My approach has always been to consult 3 different models to get my understanding on the right path and then do the rest myself. Are we really just doing blind copy pastes? As an example, I recently was able to prototype several different o
174.
▲
by
glouwbug
1y ago
Which kills my iteration interests ;)
175.
▲
by
glouwbug
1y ago
I can't really afford the link time optimization losses
176.
▲
by
glouwbug
1y ago
I think the main appeal is subset lock-down and compile times. ~5000 lines in C gets me sub second iteration times, while ~5000 lines in C++ hits the 10 second mark. Including both iostream and format in C++ gets any project up into the ~1.
177.
▲
by
glouwbug
1y ago
I've been thinking of maybe doing CTL2 with this. Maybe if #def makes it in.
178.
▲
by
glouwbug
1y ago
Combined with C23's auto (see vec_for) you can technically backport the entirety of C++'s STL (of course with skeeto's limitation in his last paragraph in mind). gcc -std=c23. It is a _very_ useful feature for even the mundan
179.
▲
by
glouwbug
1y ago
I’d triple the estimates, really. For example a game boy emulator is not trivial; there are far too many edge cases with a zilog. Chip8 would better fit for that time frame.
180.
▲
by
glouwbug
1y ago
Being in Vancouver everyone's made the "It was filmed on East Hastings" line
More ›