Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
martinhath
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
24 ms
·
1.
▲
by
martinhath
1mo ago
> Jevons paradox occurs when a more efficient use of a resource leads to an increase in its use I think these are the same, because efficiency is value over cost. In the original formulation of the paradox, a more efficient steam engine
2.
▲
Reverse Jevons Paradox
(mht.wtf)
62 points
by
martinhath
2mo ago
|
58 comments
3.
▲
Four months of Ruby Central moving Ruby backward
(andre.arko.net)
15 points
by
martinhath
7mo ago
|
5 comments
4.
▲
Trillion Dollar Elephants
(dbushell.com)
4 points
by
martinhath
1y ago
|
0 comments
5.
▲
Building a Better Web Takes a Village
(blog.kagi.com)
4 points
by
martinhath
1y ago
|
0 comments
6.
▲
Navigate Gates
(mht.wtf)
9 points
by
martinhath
1y ago
|
0 comments
7.
▲
The Rise of Fluid Teams
(blog.pwkf.org)
2 points
by
martinhath
1y ago
|
0 comments
8.
▲
AIcohol
(mht.wtf)
7 points
by
martinhath
1y ago
|
0 comments
9.
▲
Armin Ronacher – Claude Code Fixes Two MiniJinja Issues [video]
(youtube.com)
1 points
by
martinhath
1y ago
|
1 comments
10.
▲
by
martinhath
2y ago
This is from C.A.R Hoare's "Prospects for a better programming language" (1972) [0]: > It is on production runs that the security is most required, since it is the results of production runs that will actually be trusted a
11.
▲
Comments are gray and it's weird
(mht.wtf)
4 points
by
martinhath
2y ago
|
4 comments
12.
▲
Simplicity as a Value
(mht.wtf)
2 points
by
martinhath
3y ago
|
0 comments
13.
▲
Finitecurve.com: TSP art on a CPU budget
(vidarholen.net)
1 points
by
martinhath
3y ago
|
0 comments
14.
▲
Eisenhower Vectors
(thesquareplanet.com)
3 points
by
martinhath
3y ago
|
0 comments
15.
▲
Searching High and Flow
(mht.wtf)
1 points
by
martinhath
3y ago
|
0 comments
16.
▲
by
martinhath
3y ago
How would errdefer work in the general union setting? Having errors as a first class construct in the language allows things like errdefer to be very simple and easy to use. It looks needlessly specialised at first, but I think it’s actuall
17.
▲
by
martinhath
3y ago
I’m pretty sure it’s intentionally a dark pattern.
18.
▲
by
martinhath
3y ago
Not just in theory, they can, and do, fail in practice.
19.
▲
Expanding TeX's \Newif (2021)
(mht.wtf)
45 points
by
martinhath
3y ago
|
5 comments
20.
▲
by
martinhath
4y ago
> Clean code / readable code / whatever you want to call it is often at odds with performance. I disagree; or rather, I'd put it the other way around by saying that often you can get both clean code (by some metric) and re
21.
▲
by
martinhath
4y ago
> At some point in my programmer career I figured out that optimizing for human comprehension, a.k.a. "clean code", is a valid goal. Nobody is arguing against comprehensible code. Caseys video is not about clean code in general
22.
▲
by
martinhath
4y ago
OnShape is pretty nice, but their language, FeatureScript, is a disaster.
23.
▲
by
martinhath
4y ago
> Who is the author arguing against? This is addressed in the third paragraph: > The problem with this saying is that many people wrongly interpret it as “early optimization is the root of all evil.” In fact, writing fast software fro
24.
▲
by
martinhath
4y ago
I sat down and read the original paper a few years back with the same intent as the author here, and afterwards I listed a couple of quotes that I found interesting [0]. It didn't really get any traction [1], but maybe someone here wil
25.
▲
Languages, Performance, and Intent
(mht.wtf)
6 points
by
martinhath
4y ago
|
0 comments
26.
▲
Efficient simulation through linear algebra
(mht.wtf)
138 points
by
martinhath
4y ago
|
6 comments
27.
▲
by
martinhath
4y ago
> This is perhaps too big a burden on a user. Some might say they rather not have the compositionality unless it's guaranteed to be correct. I think this is it. Or rather, I think to some people, myself included, compositionality sh
28.
▲
by
martinhath
4y ago
That's not what this is, and if you'd bothered to look for more than a second, you'd seen that too. All the claims listed are very concrete claims that are possible to falsify, unlike "Thing good!", and the research
29.
▲
Building Zig structs at compile time
(mht.wtf)
4 points
by
martinhath
4y ago
|
0 comments
30.
▲
by
martinhath
4y ago
The very first line in the post is "Imagine ...". Was it not clear that what followed what hypothetical, or was the post edited after you commented?
More ›