dnautics

11 ms·

241.
by dnautics 4mo ago
> Power is not free. its ~free if you have home solar.
242.
by dnautics 4mo ago
I have been on $100/mo claude and it has been churning out quite good software for months now. like i estimate what would have taken me three ish years, assuming i didn't burn out from failure (i would have). i only hit limits w
243.
by dnautics 4mo ago
"flat or falling" let's be honest. The amount of "fall" in that graph is basically in the noise. It's been flat.
244.
by dnautics 4mo ago
US population has been basically stable (+10% over the past 10 years), so per capita (in terms of the paris agreement timeframe) is a reasonable proxy.
245.
by dnautics 4mo ago
In absolute terms, china's coal footprint is increasing, and will continue to increase in the short term, as of early 2026, they were still opening new coal plants.
246.
by dnautics 4mo ago
> US consumers and businesses buy almost all their stuff from China This is not really the case, China is the US' #3 trading partner, and trade-corrected GHGs are also down (see the graph further down the page), actually by an sligh
247.
by dnautics 4mo ago
public safety is downstream of distillation. If you can distill claude, then no amount of guardrails on claude will protect you from what someone can do with it.
248.
by dnautics 4mo ago
The US currently is at per capita GHG emissions approximately at the the same level as it was in 1910. https://ourworldindata.org/profile/co2/united-states Despite not being in the paris treaty, the us needs only
249.
by dnautics 4mo ago
one is implementable entirely in the parser. overloading (operator or otherwise) in general is a deeper compiler feature
250.
by dnautics 4mo ago
no, in general overloading is not syntactic sugar, it's a feature of the language (being able to (re-)define a function in place X and have it change the function in unrelated place Y).
251.
by dnautics 4mo ago
- Otzel, an OT library for elixir that is in some common cases 50x faster than the most widely deployed elixir OT library: https://github.com/ityonemo/otzel - Spector, a bare-bones CQRS library for elixir that composes
252.
by dnautics 4mo ago
gemini gave it the old college try
253.
by dnautics 4mo ago
how did they ever survive in the pre-EU/schengen/EEC era?
254.
by dnautics 4mo ago
you don't think the elixir type system is effective? I've never seen a bolted-on type system get so much acceptance from the hardcore "you can add types into my dead hands" crowd
255.
by dnautics 4mo ago
forced use of parens, or else syntax error.
256.
by dnautics 4mo ago
I have a sibling comment -- having thought about this for a very very long time, zig should really implement binary pseudo-operator syntactic sugar. I don't think this violate zig's spirit of 'no hidden function calls'
257.
by dnautics 4mo ago
you actually don't want "operator overloading", you want syntactic sugar. I once proposed just a special operator syntax at the parser level, but it got rejected, but if you REALLY wanted it, you could probably do this in ab
258.
by dnautics 4mo ago
> Linters are not exactly a new idea, and they can be pushed quite far. That's not an answer. There's a reason why you can't do it in C, and the reason is "the stdlib is poorly designed". No amount of linting c
259.
by dnautics 4mo ago
Point being, these two things aren't different (variable assignment and function calls); IIUC they go through the same analysis pathway, result location semantics. https://ziglang.org/documentation/master/#Res
260.
by dnautics 4mo ago
> Everything you do in Zig can be done almost in the same way in C or C++. Can you do this in C? https://github.com/ityonemo/clr
261.
by dnautics 4mo ago
that's not quite right. 1) It's var foo = Foo{...}; (no intervening dot) 2) I think parent commenter is referring to function call use case call_my_func(.{...})
262.
by dnautics 4mo ago
> And the compiler should be just a bit smarter to avoid the .{} thing when it is not strictly necessary. What's your plan for this? Rebuilding the C varargs mess from first principles?
263.
by dnautics 4mo ago
> Encapsulating arguments inside .{} seems superfluous and noisy. You don't do this? This is only for varargs or optionals. .{<stuff>} is just a shorthand for Type{<stuff>} (struct constructor) plus, "hey compiler,
264.
by dnautics 4mo ago
How crazy is it to have a language where combining two foundation traits is such a huge footgun that the linter has to warn you (but somehow you can't ban it within the language)
265.
by dnautics 4mo ago
I program in zig. I am not a current C/C++ programmer (last time I touched C++ was 2003; I can read C ~just fine... write, uh, I just hate make, okay?). Most recently I have used zig for: Linux USB driver for a proprietary industrial
266.
by dnautics 4mo ago
nah. zig doesn't have weird macros/dsls and most zig authors are reasonably good about sticking to conventions. easiest thing to do is to put a "reminder here is changelog" in the agents file
267.
by dnautics 4mo ago
claude and codex are pretty quick to figure out "oh that's not a thing anymore" and figure out what they need to do? i did a 0.15 -> 0.16 port of this library and most of it the LLM did https://github.com/E
268.
by dnautics 4mo ago
> before Zig gets properly established. zig is reasonably established. the llms write pretty good zig. see project linked below which is almost entirely llm-written > And it is going to be very hard to justify choosing Zig for your
269.
by dnautics 4mo ago
> but w/out that pedigree <shrug> no Lord or up and coming billionaire is going to syndicate sounds like an opportunity. as horse racing has a monetary reward associated with success one imagines a moneyball sort of play that
270.
by dnautics 4mo ago
no. red green tdd is great because you'll have tests when your llm breaks something later, or you're doing a massive refactor. i imagine studies are not done on codebases where the complexity gets that high. tdd has been invalua

More ›