Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jerf
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
51 ms
·
781.
▲
by
jerf
11mo ago
Also, if you are updating "right away" it is presumably because of some specific vulnerability (or set of them). But if you're in an "update right now" mode you have the most eyes on the source code in question at t
782.
▲
by
jerf
11mo ago
Elsewhere in thread is mentioned an Underworld remake. I do not have the same complaint about them as I do Ultima VII. A good remake could still be an interesting experience today, with little more than a graphical overhaul and modern contr
783.
▲
by
jerf
11mo ago
As someone who played these back in the day and enjoyed them, I don't think I could even recommend them to myself today. Ultima VII is everything the other comments say it is... but it's also one staggeringly large nested fetch qu
784.
▲
by
jerf
11mo ago
My crossover point for where I'd rather be using a static language than a dynamic one for exploration is about a week in the modern era. In 1999 I'd agree with you completely, but static languages have gotten a lot better. There a
785.
▲
by
jerf
11mo ago
I like to characterize it as "the slowest language of the fastest class of languages". In general other compiled languages are faster, though generally we're talking 2 or 3 times at the most (Go doesn't optimize very har
786.
▲
by
jerf
11mo ago
You can, without loss of generality, simply insert "holding the language constant" if you like into the essay without losing the point I am trying to make, where the question of what language to choose is mostly orthogonal to the
787.
▲
by
jerf
11mo ago
The problem with that context is that it is neither good, nor useful. For good, an example that perhaps I should lift into the essay itself is probably more useful than an explanation. A year or two or so back, there was some article about
788.
▲
by
jerf
11mo ago
Another thing about Go, and more generally, the statically-typed languages, is that these utility functions are generally safer to get a once-over and a commit into the code base than in dynamically-typed languages. Something that joins an
789.
▲
by
jerf
11mo ago
Nothing. But that's not the point.
790.
▲
by
jerf
11mo ago
Whether or not GC is a negligible portion of your runtime is a characteristic of your program, not your implementation language. For 99% of programs, probably more, yes. I have been working in GC languages for the last 25 years. The GC has
791.
▲
by
jerf
11mo ago
What a horrible technology to wrap around your neck for rebellion's sake. XSLT didn't succeed because it's fundamentally terrible and was a bad idea from the very beginning. But I suppose forcing one's self to use XSLT j
792.
▲
by
jerf
11mo ago
Because about 99% of the time the garbage collect is a negligible portion of your runtime at the benefit of a huge dollop of safety. People really need to stop acting like a garbage collector is some sort of cosmic horror that automatically
793.
▲
by
jerf
11mo ago
It looks like Boa has Unicode tables compiled inside of itself: https://github.com/boa-dev/boa/tree/main/core/icu_provider Brimstone does not appear to. That covers the vast bulk of the difference.
794.
▲
by
jerf
11mo ago
No, because the LSP is specifically about inheritance, or subtyping more generally. No inheritance/subtyping, no LSP. It is true that an interface defines certain requirements of things that claim to implement it, but merely having a
795.
▲
by
jerf
11mo ago
I think a lot of the pushiness is a frantic effort to keep the bubble inflated and keep the market out of the trough of disillusionment. It won't work. The trough of disillusionment is inevitable. There is no jumping straight from peak
796.
▲
by
jerf
11mo ago
The Microsoft Agent, available through ActiveX: https://en.wikipedia.org/wiki/Microsoft_Agent Which meant you could use it in Internet Explorer but not anywhere else. But it did make for some interesting web pages. I b
797.
▲
by
jerf
11mo ago
As much as the default LLMisms are annoying me, it's also a honeymoon period right now where you can even suspect whether something is AI generated based on the default LLM-isms. Word about how to fix their tone has been getting around
798.
▲
by
jerf
11mo ago
A non-"AI" template is probably getting filled in with numbers straight from some relevant source. AI may produce something more conversational today but as someone else observed, this is a high-hallucination point for them. Even
799.
▲
by
jerf
11mo ago
Yes. The nice thing about this is that it's one function, about 20-30 lines, rather than a "framework". I've been operating up to this point without this structure in a fairly similar manner, and it has worked fine in th
800.
▲
by
jerf
11mo ago
I'm still fiddling with this so I haven't seen it at scale yet, but in some code I'm writing now, I have a centralized repository for services that register themselves. There is a struct that will provide the union of all pos
801.
▲
by
jerf
11mo ago
Fair, I was sloppy there. The cobra isn't a scam itself, it's just a demonstration that it's already a hard place to navigate what with everything that is going on there. A deluge of AI garbage may not be a "scam" i
802.
▲
by
jerf
11mo ago
Yes, but observe how that for all three of the things that immediately came to your mind, you have respectively 1. a thing that still has a lot of scams in it (though it may be the best of the three) [1] 2. A thing so full of scams and fake
803.
▲
by
jerf
11mo ago
If we're going to take my obviously unserious suggestion seriously, I'd suggest a bigger problem is that his stack isn't in Python and the code for whether an email is pwned probably isn't remotely structured as a functi
804.
▲
by
jerf
11mo ago
This isn't an uncommon lament, despite what the author thinks. The problem is that running "studies" on what the author and others are asking for is effectively impossible. You can't get 25 teams of suitably-random profe
805.
▲
by
jerf
11mo ago
On the plus side, Troy can save a lot of DB space now. Instead of storing which emails have been compromised at this point he can replace that with just def email_compromised(email): return True
806.
▲
by
jerf
11mo ago
There's no need for research. The answer is simple: You can't run Erlang concurrency on a GPU. GPUs fundamentally get their advantage by running the same operations on a huge set of cores across different data. They aren't ju
807.
▲
by
jerf
11mo ago
Erlang operates on a higher level, with much, much larger chunks. Any sensible modern system will, for instance, have some sort of execution context (thread/green thread/continuation/task/whatever) associated with a sing
808.
▲
by
jerf
11mo ago
"Are there any good resources on optimizing python performance while keeping idiomatic?" It is essentially impossible, "essentially" here using not the modern sense of "mostly", but "essential" as in
809.
▲
by
jerf
11mo ago
There is no "LLM style". There is a "default LLM style", which is why I call it that. Or technically, one per LLM, but they seem to have converged pretty hard since they're all convergently evolving in the same en
810.
▲
by
jerf
11mo ago
I didn't make heavy use of it, but I did sometimes use "It's not X, it's Y" or some closely related variant. I've had to strike that from my writing, because whether or not it makes anyone else cringe, it'
More ›