Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cwp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
42 ms
·
451.
▲
by
cwp
11y ago
Actually, the issue there is terrain. Llamas are very agile and can carry loads to areas that neither horses nor carts can reach. Smaller loads, of course, but still much more than a person can carry. Even today, horses aren't really a
452.
▲
by
cwp
11y ago
Really? The spies release a graph database where edges can have statistics attached, like oh, say, counts? We're being trolled. Edit: Looking for forward to the release of RingTone, a system for processing very high volumes of call det
453.
▲
by
cwp
11y ago
Yeah, interesting. I'll just point out that my argument is not that AI can't affect the physical world. Clearly it can. It's that AI is still embodied in the physical world, and still subject to the laws of physics. We'r
454.
▲
by
cwp
11y ago
> Solar panels can collect more energy than photosynthesis. Planes can fly faster than any bird. Guns are far more effective than any animal's weapons. Steam engines can run more efficiently than biological digestion. And we can ge
455.
▲
by
cwp
11y ago
That's my point. The laws of physics are a bitch. We like to think of the internet as a place of pure platonic ideals, where code and data are all that matter. But that ethereal realm is still grounded in matter and ruled by physics. A
456.
▲
by
cwp
11y ago
Physics. You're right that ecosystems are brutal. That's exactly why I'm not worried about AI as an existential threat to humanity. A few years back Bill Joy was sounding the alarm on nanotechnology. He sounded a lot like Elo
457.
▲
by
cwp
11y ago
Except for that bit at the end.
458.
▲
by
cwp
11y ago
Yeah, I've done something like this as well. It's wrapper around nixpkgs that provides: * baseline nixpkgs at a specific version * customized overrides of specific packages * a library of functions to aid packaging our own
459.
▲
by
cwp
11y ago
You might want to look into Nix for Haskell development. Nix a pure, lazy, functional DSL for describing packages and dependencies, and thus naturally attractive to Haskellers. As a result, there's good support for Haskell in the nixpk
460.
▲
by
cwp
11y ago
Yeah. This is what I meant by "better hardware utilization".
461.
▲
by
cwp
11y ago
The point is better hardware utilization. Part of the "isolation" that containers provide is resource allocation. You assign limits to the CPU cycles, RAM, disk IO, network IO etc that each container can use. Without any kind of v
462.
▲
Bread Is Broken
(nytimes.com)
2 points
by
cwp
11y ago
|
0 comments
463.
▲
by
cwp
11y ago
For anyone wondering if that ellipses is at all misleading, here's the full quote: "We make these choices, bit by bit. I stopped ordering from Sprig back in the spring, because (a) I don’t like that future and (b) they sent me a t
464.
▲
by
cwp
11y ago
Also, there are a lot of species that went extinct because they encountered a predator they couldn't deal with - people. Is that a "natural process" just because it happened before recorded history?
465.
▲
by
cwp
11y ago
Ah. An academic. Of course.
466.
▲
by
cwp
11y ago
As a matter of fact, they do. Unlike Java IDEs, Smalltalk dev tools are implemented via reflection on the running program. Between information available from the runtime data structures in the program and the fact that Smalltalk uses single
467.
▲
by
cwp
11y ago
> Yes, but very few of those are automated. Which is not surprising since the absence of types in Smalltalk can lead to refactorings that break your code, so user supervision is necessary. This is just not true. Go download a copy of Vis
468.
▲
by
cwp
11y ago
I don't assume there's been no innovation. HotSpot today is faster than Strongtalk ever was. Java has lots more libraries than Smalltalk today. For a broad range purposes, it's a better choice than Smalltalk today. But a lot
469.
▲
by
cwp
11y ago
Alas, Java advocates always fail to entertain. HotSpot was a Smalltalk VM that was bought by Sun and adapted to Java. Automatic refactorings were first implemented in Smalltalk IDEs, and all major Smalltalk dialects have them today. Java&#x
470.
▲
by
cwp
11y ago
I see two opposing forces: Self driving cars could encourage sprawl by making commuting long distances more practical. If you could be working during your commute instead of driving, and didn't need to find parking once you arrive, a 2
471.
▲
by
cwp
11y ago
I've noticed the same thing geographically. Twice now, I've taken a "sabbatical" and moved to Quito, Ecuador for a year to be near family. Both times, I lost weight when I arrived, stabilized at a leaner equilibrium, the
472.
▲
by
cwp
11y ago
The term is usually used by people that don't know what compilers are. Snark aside, I think this is actually the case. I bet there are a LOT of CoffeeScript/Javascript developers who have never worked in a compiled language.
473.
▲
by
cwp
11y ago
That's exactly the point. So my question remains: if threads are the right answer today, either the C10K folks were wrong or something has changed since then. What?
474.
▲
by
cwp
11y ago
Isn't this a rehash of the C10K problem[1] from a decade ago? That was pretty much resolved in favour of single-threading and asynchronous IO, with Nginx and Node.js replacing Apache and Ruby as the platforms that the cool kids use. So
475.
▲
by
cwp
11y ago
You've got it backwards. It's the author of the dancing baby video that has to show monetary loss. That is, Lenz cannot sue Universal unless she can show that taking down her video caused her monetary loss.
476.
▲
by
cwp
11y ago
He's on to something here, but I think the asset/liability duality isn't a matter of your point of view. Code really is a liability, even from the high-level view in the boardroom. The asset is functionality. If you can get
477.
▲
by
cwp
11y ago
Can you expand on that? I've got a mature API that's based around HATEOS, json-schema and HTTP content negotiation. It works really well, but client-side developers always need some time to get used to it, as they expect "RES
478.
▲
by
cwp
11y ago
Given that Apple is writing compilers and designing chips, on-the-fly recompilation shouldn't be a big problem for them.
479.
▲
by
cwp
11y ago
Read more closely. Durability was NOT a requirement. Since we've decided to scope out access to historical logs from the problem we were trying to solve and focus only on real-time log consolidation, that feature of Kaf
480.
▲
by
cwp
11y ago
> The only thing that can kill bitcoin is a technological advancement that makes its security weak or vulnerable If by "bitcoin" you mean "cryptocurrencies" then yeah, security is the only real killer. But the thing t
More ›