Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
titzer
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
31 ms
·
571.
▲
by
titzer
2y ago
> Those are incredibly difficult problems, and each one keeps getting worse. Indeed, so hard that it took until 1957 for the US to master them.... Not trivialize the effort of making such rockets and reentry vehicles, but the North Korea
572.
▲
by
titzer
2y ago
Cost. Same reason you don't deliver UPS packages with B-2 bombers.
573.
▲
by
titzer
2y ago
Here are some tips; 1. When you cross your eyes, gradually let them return to uncrossed. Try to do it as slow as possible. Along the way, try to line up any structures that you see in the image that are repeated from left/right half. 2
574.
▲
by
titzer
2y ago
Diverging is definitely harder, and might be out of focus. To keep in focus I found it easier to focus on the right image and then cross my eyes, rather than staring in the center and then staring through the screen into the distance while
575.
▲
by
titzer
2y ago
And no one stops to ask how the internet sustained itself from the years 1995 to 2005. Or big search engines, for that matter. The answer is that they were smaller and their revenue was based on selling real things, not constant hassle and
576.
▲
by
titzer
2y ago
Yes, but now the ads watch us.
577.
▲
by
titzer
2y ago
The article might have been updated since you read it, but this is in there: > We try to vectorize the following C++ procedure. The procedure cannot assume anything about dividends, especially if they are all equal. Thus, it is not possi
578.
▲
by
titzer
2y ago
Meh, you know people are just going to throw LLMs at it and they'll be fine with it hallucinating correctish code by the ton-load. But I agree that they are going to have tough time making idiomatic Rust from random C. Like I said, cor
579.
▲
by
titzer
2y ago
> Concurrency should always be studied I disagree. If we want people to understand , then we should teach computer systems bottom-up and thus understand the bottom-level behaviors before being surprised that our bad (i.e. wrong) abstrac
580.
▲
by
titzer
2y ago
> The article explicitly mentions problems with interleaving of instructions between two processes (aka threads) which is the fundamental problem of concurrency. Again, with weak memory models, writes from another thread can be observed
581.
▲
by
titzer
2y ago
It's not just I/O, it's data pipelining. Threads can be used to do a lot of different kinds of compute in parallel. For example, one could pipeline a multi-step computation, like a compiler: make one thread for parsing, one
582.
▲
by
titzer
2y ago
The problem with this article, though it presents model checking and state space exploration well, is that it doesn't present weak memory models[1], which are the reality on all multiprocessor/multicore systems these days. Thus is
583.
▲
by
titzer
2y ago
SIMD and thread-level parallelism solve completely different problems.
584.
▲
by
titzer
2y ago
The problem with this article is that it doesn't present weak memory models[1], which are the reality on all multiprocessor/multicore systems these days. Thus is perpetuates misconceptions about concurrent programming. This is a p
585.
▲
by
titzer
2y ago
> More generally, the information throughput of human behavior is about 10 bits/s. I'm sorry, I just can't take this article seriously. They make a fundamental mistake of encoding and assume that information is discretized
586.
▲
by
titzer
2y ago
Strong plus one here. Not only that, but it uses gobs of energy in total. Google has reneged on all of its carbon promises to stay in the running for AI domination and to head off disruption to search ads business. Since I've unconsc
587.
▲
by
titzer
2y ago
As only a cursory user of said tools (but strong opinions) I felt the immediate desire to get an editable (2D) scene that I could rearrange. For example I often have a specific vantage point or composition in mind, which is fine to start fr
588.
▲
by
titzer
2y ago
It also seems intuitively wrong that there are different sizes of infinity, yet Cantor discovered exactly that.
589.
▲
by
titzer
2y ago
Look, we need more than just promises. C++ is charting a future to the past in the most torturously slow process possible, primarily because of absolutely intrasigent performance obsession that won't even admit the possibility of a 1%
590.
▲
by
titzer
2y ago
Replace C++ with asbestos (no, I'm serious, not just stark), and we're basically having exactly the same conversation that's gone on over decades in the meatspace world, with analogous players, sunk cost/investment cal
591.
▲
by
titzer
2y ago
> well defined deterministic execution model would mitigate some of these unpredictable state transitions. The problem here is that giving a program access to high-resolution (non-virtualized) timers violates deterministic execution. Eve
592.
▲
by
titzer
2y ago
I've written 7 compilers. If you don't know you're writing a compiler from the beginning and you've never written before, it is basically guaranteed to be a hot mess in the end, unless you accidentally make exactly the
593.
▲
by
titzer
2y ago
Well the targeting angle could be low to the horizon, aiming into oncoming debris, reducing its orbital velocity, so that it deorbits faster. The vertical component of the vector would be minimized. A low angle reduces laser efficiency due
594.
▲
by
titzer
2y ago
From the Oxford dictionary: conflict of interest, n: a situation in which the concerns or aims of two different parties are incompatible. "the conflict of interest between elected officials and corporate lobbyists"
595.
▲
by
titzer
2y ago
As if Google didn't take anything from us. Google makes money selling your attention and brainpower to the highest bidder. Hands down. They are the biggest entity in the attention economy and their real customers are advertisers. Googl
596.
▲
by
titzer
2y ago
The conflict of interest between owning search , being a provider of user identity/login , and effectively owning the entire internet ads marketplace , and being a provider of the "user agent" (remember when people thought
597.
▲
by
titzer
2y ago
> We’ve begun by enabling hardened libc++, which adds bounds checking to standard C++ data structures, eliminating a significant class of spatial safety bugs. Well, it's 2024 and remember arguing this 20+ years ago. Programs have bu
598.
▲
by
titzer
2y ago
Exactly, a stable language-agnostic binary ABI is the proper layering choice.
599.
▲
by
titzer
2y ago
I'm 100% with Linus on this one.
600.
▲
by
titzer
2y ago
You can still randomize heap allocations (but not with as much entropy), as usually the heap segment is quite large. But you don't get randomization of, e.g. the code. ASLR is a weak defense. It's akin to randomizing which of the
More ›