szvsw

10 ms·

61.
by szvsw 2y ago
Have you thought about how autodiff can be baked into the lang? Given that it is already seemingly all representing computation with graphs of operations, building AD into it seems like a natural extension that could open up some pretty use
62.
by szvsw 2y ago
Yeah cooling towers seems like the obvious choice, thanks for confirming! I’m sure there are some other more exciting designs that hook datacenters up to prosumer/mesh topology ambient-temp district heating/cooling loops - or ther
63.
by szvsw 2y ago
What about heat transfer? At least in a moderate, dry climate (whereas SP is hot/humid) there’s a natural benefit to having a high surface area to volume ratio, favoring wide/flat spaces, from the perspective of heat rejection. I’
64.
by szvsw 2y ago
> You cited the exploiting as the one and only reason that cheating is interesting here As far as I can tell, I did not… this is what I said: > it’s very interesting to see how a practice that is fundamentally about exploiting general
65.
by szvsw 2y ago
Runners on 2B are allowed to try to steal signs if they can crack whatever set the pitcher and catcher have switched to (well they use pitch com now); the astros used live video feeds to pick up the signs even with no one on base as well as
66.
by szvsw 2y ago
> This is not at all the same thing as the Astros scandal. Astros didn’t break the agreed upon rules. Sheesh, didn’t expect to re-litigate WS‘17 on HN today… I concede that there was at least some gray area in the codified official rules
67.
by szvsw 2y ago
> It's not a particularly complex or surprising "ethics" though Yes, you are mostly right, but it’s still interesting (and positive!) that the community landed on an “anything goes so long as you are honest” set of norms.
68.
by szvsw 2y ago
> Speed running communities generally don't care what exploits you use, as long as you are up-front and honest about it. That is, precisely, a set of ethics! > There really isn't an "ethics" of what exploits are al
69.
by szvsw 2y ago
As someone with absolutely no knowledge of speedrunning community norms, it’s very interesting to see how a practice that is fundamentally about exploiting generally unintended mechanisms within a system design still develops its own notion
70.
by szvsw 2y ago
Doom is not quite the right word, at least in the apocalyptic connotation… it is too eventful, punctual, eschatological, teleological, suggesting a particular point of no return. Especially when combined with the word horizon, which sugge
71.
by szvsw 2y ago
Right, I guess that’s my point: If Typst wants to compete with LaTeX, IMO it needs some sort of mechanism by which journals will deem a Typst submission acceptable, along with readily available templates for said submissions. That’s a big
72.
by szvsw 2y ago
> I think one of the best ways to overcome the enormous momentum of TeX is to point out its limitations (while still keeping an eye on Typst's limitations), and explain how Typst overcomes them. One of the other easy ways to overcom
73.
by szvsw 2y ago
It’s an interactive slide show, but it also has forced the user into the CLI context, where they are likely to already bring a different type of attention and focus than if they were reading the exact same set of instructions in a markdown
74.
by szvsw 2y ago
> the average person on the street will confuse Deepseek with Deep Research. That’s probably a feature not a bug (from OpenAI’s perspective…).
75.
by szvsw 2y ago
The point made by a commenter a few levels up questioned whether 98% reliability for adding two 100-digit numbers together should be considered noteworthy/acceptable etc. My point is that assessing 98% reliability qualitatively depends
76.
by szvsw 2y ago
At pace though? What would your throughput be to maintain 98% reliability? How long do you think one execution would take? my guess would be between 30s-1m for a single summation of two 100 digit numbers? So let’s say you want a sample size
77.
by szvsw 2y ago
Can you add 100 digit numbers reliably in a short amount of time over a large sample size? How about without a piece of paper and a pen? Can you even remember a 100 digit number? It’s likely quite difficult… This is not about comparing to r
78.
by szvsw 2y ago
Arguably that’s a separate (obviously critical) concern. I think it’s worth it to abstract that away as just a step that exists in the pipeline with its own set of concerns/challenges/methods etc that really requires its own deepe
79.
by szvsw 2y ago
AWS GovCloud already exists FYI (as you hinted) and it is absolutely used by the DoD extensively already.
80.
by szvsw 2y ago
A lot of what you said is intuitively/directionally correct, but misses a lot of important physics related to heat transfer in buildings and operational questions of space heating equipment. This is your most accurate/relevant poi
81.
by szvsw 2y ago
Daubechies wavelets are such incredibly strange and beautiful objects, particularly for how deviant they are compared to everything you are typically familiar with when you are starting your signal processing journey… if it’s possible for
82.
by szvsw 2y ago
Yep, this makes a lot of sense. In general, we already have plenty of mechanisms for specifying interfaces/api specs, tests, relationships, etc in a declarative but more formal manner than natural language which probably all work , and
83.
by szvsw 2y ago
Do you have any repos or examples you can share? Would love to see an example of that in action!
84.
by szvsw 2y ago
Highlight related to an analemma: the figure the sun traces if you make a parametric plot of its position in the sky at fixed time T as a function of the day of the year d, ie f_T(d) = (azimuth,elevation). https://solar-center.st
85.
by szvsw 2y ago
I mostly agree with what you were saying, but I don’t think I was advocating for “no code” entirely, and certainly not the elimination of engineers entirely. I was trying to articulate the idea that code generation tools will become incre
86.
by szvsw 2y ago
> without a human going through the necessary thought processes and problem solving steps to build the theory of the software as described in this paper We might not be there yet (well we definitely are not) but it does not seem out of t
87.
by szvsw 2y ago
> It seems to me that one consequence of the "Theory Building View" is that: instead of focusing on delivering the artifact or the documentation of said artifact, one should instead focus on documenting how the artifact can be
88.
by szvsw 2y ago
I agree that typing probably is not the limiting factor in most cases and for most people, and so the conversation might seem a little silly… But that’s precisely because typing is fast. Once you know what you are doing, you start typing an
89.
by szvsw 2y ago
It really really depends on what your goals are and what type of design domain you are working in, eg jewelry, architecture (and what within architecture), fabrication, experimental sculpture, etc. At the end of the day though… play. Lots
90.
by szvsw 2y ago
Yeah good points. You can easily imagine composing graph based/data flow programming languages with just your mouth, ie “create node:<type>:<name>; connect node:<name>:<outlet> to node:<name>:<inlet>

More ›