Personally, I find warp a bit disorienting, but it is indeed a more integrated approach.
4,833 karma · joined July 12, 2012
firetiger.com, previously twitch/aws, i like woodworking
s@spencerwnelson.com
Personally, I find warp a bit disorienting, but it is indeed a more integrated approach.
I suppose the insight is that schema documents are programs, just in a weird language, and compiled programs are fast.
Anything published on your integrator and its modifications?
One nice feature of ASSIST (from what I remember, its been a while) was that I could add in more perturbers and crank up the gravitational harmonics if I wanted to. It sounds like you support that too at least for perturbers?
Matt Holman's ASSIST (https://github.com/matthewholman/assist) struck me as a breath of fresh air, coming from openorb and its kin.
This reminds me of classics like "worse is better," for today's age (https://www.dreamsongs.com/RiseOfWorseIsBetter.html)
All speculation, but I'd be curious to see it evaluated - does the LLM do better edits on egregiously commented code?
Am I correct in thinking that this would require a fork of the main Go implementation, in order to make a deterministic (and controllable) goroutine scheduler and network stack?
Does one also need to run on a particularly predictable OS?
> They solve query parallelism by allowing you to perform computations on the edge, enabling horizontal scaling the compute layer.
Hmm, I don't understand this one. How do you horizontally scale a query that scans all data to do `select count(*), col from huge_table group by col`, for example? In a traditional map-reduce engine, that turns into parallel execution over chunks of data, which get later merged for the final result. In DuckDB, doesn't that necessarily get done by a single node which has to inspect every row all by itself?
If the thesis here is that most datasets are small, fair enough - but then why use a lake instead of big postgres, yknow?
I use emacs. The emacs LSP mode starts up a language server process for a language like Python or Go. If I use Nix to manage development dependencies like my compiler, linting tools, and even language-specific dependencies, then how do I get the LSP and emacs to use the correct Nix-y set of dependencies? To make things extra complex, note that I often work on multiple interdependent projects concurrently; I imagine that makes things even gnarlier.
Is there a sane way to manage this sort of thing? Do I end up managing a per-project installation of emacs??
I propose that different goods have different trajectories. Lighting is better and cheaper than 100 years ago. Boots maybe aren't.
1. Neighbors and friends are notified in advance. "If you see my daughter and she looks lost, please help her, she is doing an errand."
2. The destination is usually notified. "My daughter is coming to buy rice, let me know if she isnt there in two hours."
3. This practice is somewhat old-fashioned and rural. Many parents wouldnt consider it today.
Remember, the show was aired to a Japanese audience. If it were universal, it would not be worth televising.
A very readable explanation is here: https://gpuopen.com/download/publications/Introduction_to_GP...
It turns out that radix sort can be implemented in a way that is very straightforward to parallelize. It's a beautiful and elegant approach and worth knowing about!
This is very common. GRK, Spax, Axis (a local brand to the Seattle area), and many more. Yes, they are better!
These companies are very, very risky. If they weren’t, you would see more competition!
The MPC has many observations of unidentified moving object candidates. These are called “tracklets” and come from pairs of observations of the same patch of the sky by the same observatory, separated (typically) by a few minutes.
The “isolated tracklet file”, or ITF, is a catalog of all of these unidentified moving objects.
When an identification is made and submitted to the MPC, the MPC back-projects the orbit and checks the ITF for any past observations which might have actually been of this newly identified object.
Then, the designation’s timestamp is of the first matching observation. So in this case the ITF had an observation from back in 2018.
Occasionally, two “objects” turn out to be the same actual physical object, but we learn late. In this case, the MPC does maintain a list of “aliases” of the object, so you might get that “aka” list. But that is not quite what happened here.
Sometimes when you look at old things, it can be shocking how “sloppy” the workmanship is, but you have to realize that they were not trying to get perfect paint jobs or smooth castings. They were trying to make money.
I agreed until here. Obviously, lying isn't the only way to make money. I make furniture and fix windows in old houses for a living. Am I grifting?
When you stretch into hyperbole, you lose the ability to convince people in the middle.
The point of Terence Tao’s original post is that you just cannot think of rejection as humiliation. Rejection is not a catastrophe.