5,805 karma · joined September 23, 2013
Both objects desugar to a sequence of segments (lines).
The result is that you can freely mix expression/assignment blocks & statements. Things like switch-case blocks & macro tables are suddenly trivial to format in 2d.
Because comments are handled as right floating, all comments nicely align.
I vibe coded the base layer in an hour. I'm using with autogenerated code, so output is manually coded based on my input. The tricky bit would be "discovering" tables & block. I'd jus use a combo of an LSP and direct observation of sequential statements.
If we want to build housing, we'll need a stabilizing force for that. I don't see a way to make that happen outside of govt intervention.
Our "sister" lab over in computational biology had a few PD's, but was 2x as big, and had easily 5x the funding.
It wouldn't surprise me if our industry is also labor constrained? I know my brother had a machine shop to make aftermarket titanium parts for (motor)bikes, some cars, etc. He had a policy of nonstop looking for new machinists, even if he was fully staffed, because a machinist could just wander off at any time. With only 4 employees, he could find himself at at 25–50% loss of ship time in just a few days, at any time. It's not even like the machinists were getting more money. They'd just leave, because the new shop was 5m closer than his.
Fixing the labor pool issue is a decades long issue. More money in that pool won't fix things. I don't even know what's going on. Maybe I can just blame modern financialization for the issue? That seems easy, if wrong.
But, for sure, the complete lack of social safety net for labor can't be helping. Maybe if we guaranteed child care, 100% round-the-year safe spaces (we could use the fantastically expensive schools which are empty 75% of the time?), 3-free-meals-per-child, and free education through an associates degree? None of those are particularly expensive, even at the national scale.
I guess the journals could turn around and pay the PI? But, then what? The "reviewers" still aren't being paid; just the PI? The incentive then is for the PI to have as many grad students as possible just reviewing papers. (FREE. MONEY.) If there was ever a dynamic I've been in where one agent doesn't need MORE power, it's the PI-grad-student one.
And, I've not even considered (in depth) the Bad Actors™ in such a situation. I'm just thinking about basic humans humaning along...
I don't know how submission works for non-Western subsidized countries; but, just wading through the pre-AI submission process was a 50+-hour a week job for one, tiny, niche conference. Making the cost $1000 cuts that down by at least 2 orders of magnitude.
On the flip side ... paying the reviewers just seems like a bad idea? Reviewers need to be skeptical AF. Even the best scientists can throw out turds every now and then.
This was a 5 year play by my dad. Shout out.
But! Notice that abatement doesn't get us to 0. It merely slows the process. The remainder absolutely needs ACC. The output stream needs to be dirt cheap, the thermals need to be 100°C and not 900°C. Those sorts of things would bring ACC down to "hundreds of billions" rather than a trillion.
For larger projects (the exe), the shebang points to a C build file, which when compiled, knows the root path; that C build script then looks for a manifest, builds, links, and fork()s. A good a/m timestamp library with direct ccache support can spin up as fast as a script even on big projects.
Again, this is all a bad idea bc it's hard to control your environment.
I guess we were doing all this in the mid 2000s? When did TCC come out?
I've got 10 full time senior engineers on a project heading in to its 15th year. We rewrite even extremely low level code like std::vector or malloc to make sure it matches our requirements.
UNIX was written by a couple of dudes.
I mean... the whole field of typographic ad copy is about 2D writing?
So, the killer cost is at compile time, not runtime, which is fundamental to the underlying autograd operation.
On the flip side, it's 2025, not 2006, so pro modern algorithms & heuristics can change this story quite a bit.
All of this is spelled out in Griewank's work (the book).
We had all these issues back in 2006 when my group was implementing autograd for C++ and, later, a computer algebra system called Axiom. We knew it'd be ideal for NN; I was trying to build this out for my brother who was porting AI models to GPUs. (This did not work in 2006 for both HW & math reasons.)
You can do the same thing with binary trees and other structures. It's more fiddly, and there's definitely places where single-ownership allows mutability "under the hood" for real performance gains, but that's the basic idea.