Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
fl0ki
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
30 ms
·
271.
▲
by
fl0ki
3y ago
An even simpler explanation is return to mean. They were going to get better in a few days anyway, with or without antibiotics. But if they keep getting antibiotics each time, they're always going to think that they helped. Confirmatio
272.
▲
by
fl0ki
3y ago
I apologize in advance for criticism you only half deserve. I know this is HN, but not every single topic needs to be compared to LLMs or Blockchain. Concepts like fitness functions, selective pressures, feedback mechanisms, etc. -- as appl
273.
▲
by
fl0ki
3y ago
That's just the thing, Scala and its ecosystem had these problems right at the height of its popularity, meaning that the situation was the worst right when the most people were around to experience it, and understandably many never lo
274.
▲
by
fl0ki
3y ago
I think people forget just how bad compatibility was a decade ago. The compiler promised no ABI compatibility even between minor versions, which on its own could have been fine; Go and Rust don't promise ABI compatibility either. The p
275.
▲
by
fl0ki
3y ago
[Foreword: I agree that it would make no sense for any language to automatically parallelize loops, especially over filesystem mutations. However I am very happy manually doing it with one function so it's explicit when it happens and
276.
▲
by
fl0ki
3y ago
Skimming isn't really possible for people that rely on screen readers. I think effective summarization would be useful for them. Whether this is an effective implementation, however, remains to be seen.
277.
▲
by
fl0ki
3y ago
I am very curious about what pre-1970 hardware and software you posted this from.
278.
▲
by
fl0ki
3y ago
> Personally, in my early 40s, I feel my brain is back in 20s. Software like GPT should be a tool, not a crutch. There is a lot that people can do to maintain their mental acuity over the decades, and I know first-hand the difference bet
279.
▲
by
fl0ki
3y ago
Go's GC isn't compacting, and might never be, because it made the short-sighted decision that Go pointers can be handed directly to asm or C code. It's also stuck on an old fork of tcmalloc which isn't anywhere near the
280.
▲
by
fl0ki
3y ago
He's an author, not a game dev. The game devs licensed his IP. All of this is explained in the article. You might also be surprised to learn that Andrei Tarkovsky, director of the film Stalker (1979), didn't personally learn C++ a
281.
▲
by
fl0ki
3y ago
Go already faces a subset of this type system challenge in an arguably much worse way: interfaces are implicitly implemented by any type with the corresponding set of method signatures, unlike Rust where traits are implemented explicitly.
282.
▲
by
fl0ki
3y ago
It is much faster for CPU-bound work. In my experience, 2x-5x is the most common range I get. There are many reasons besides just memory allocation and LLVM that Rust code ends up faster. Let me just focus on one very commonly used data s
283.
▲
by
fl0ki
3y ago
Huge missed opportunity to make a Snellings Museum of Smelling
284.
▲
by
fl0ki
3y ago
Sure, but in any case where the patches were independent enough to automatically apply in any order, `git rebase --interactive` would have worked just as well and has done for about two decades. It can reorder, drop, squash, amend, etc. all
285.
▲
by
fl0ki
3y ago
Pro tip, the footer link https://doc.rust-lang.org/src/core/slice/mod.rs.html#2520 is not a permalink because it doesn't include a commit ID. It looks like it's already linking to the wrong thing no
286.
▲
by
fl0ki
3y ago
This is not a dig, just a concerned citizen: I would encourage you to check whether your microdose schedule has crept up from the standard 10-25µg into what looks like 50-75µg. It's one of those things that other people suspect long be
287.
▲
by
fl0ki
3y ago
Serious question though, why use "JSON" at all then? You can just admit it's JWCC, which is fine, at least that's a distinct term -- but even that's not a spec, it's just a blog post that very few people even k
288.
▲
by
fl0ki
3y ago
When can we put the "don't rewrite old code" myth to rest? People cite Joel's essay in many situations where it can be reasonably believed to be applicable, but they also cite to people who are in a much better position
289.
▲
by
fl0ki
3y ago
The configuration examples are not valid JSON, due to trailing commas. Not a great first impression. https://github.com/runreveal/kawa#getting-started I see it's because they use their own config loader library th
290.
▲
by
fl0ki
5y ago
This is true, but people focusing on only these benefits often miss the fact that they still have to update the image contents and re-deploy as soon as security patches are available. This is like updating the direct dependencies of your se
291.
▲
by
fl0ki
5y ago
Not sure if you're in on the joke, but for those who didn't go to the repo itself: https://github.com/golang-jvm/golang-jvm It's just a copy-paste of JRuby on April 1st and the readme now includes a rick
292.
▲
by
fl0ki
5y ago
My experience with fx has been very mixed and I don't think it's a safe default recommendation. It can often outperform fnv and wyhash because it does so little, but it can also greatly underperform once it's used in a hash t