6,062 karma · joined September 29, 2011
He is making his future defense lawyer's job very difficult by committing to a story. The lawyer will be severely constrained from suggesting alternate explanations of the facts to the jury because SBF has already negated so many possible interpretations. Every time SBF overstates an explanation, the prosecutors get that into the record. Every time SBF provably misstates or misleads in an interview, the prosecutors get to say "take a look at this slime ball."
When under investigation, you shut up. It's the only smart thing to do.
Congrats on the baby!
DOS was still popular because it was so much cheaper than a workstation. Single-tasking means exiting your editor to do code check-ins and having to reload your context a lot. Networking was definitely an after-thought that many didn't have access to.
The bigger issue was the device you were programming. Small memory. Pointer sizes that might not be what you expect. Integers that overflow if you fail to think about their sizes. Pointers that cannot reliably be compared without normalizing them first. No threads. An operating system that does nothing other than provide access to files.
I've used C++ for my entire career. CFront 1.2 was a very different language than modern C++. Sometimes people wonder why I use stdio.h instead of iostreams: it's because stdio.h is basically unchanged since cfront and that code still works while and iostreams have changed significantly multiple times requiring re-writes.
One thing I miss is some of the color schemes in the Turbo Pascal/C IDEs. Yellow on Magenta and Yellow on Cyan were fantastic. I'm not sure why those color schemes don't work in GUIs -- I suspect it's because the geometry of fonts is so much different than text-mode graphics. Text mode had super thicc and clear fonts made out of so very few pixels.
This article is much like the "rich get vastly richer this year" stories that come out when the stock market rises. For some reason the opposite stories do not get written when the stock market craters because that's not "fun."
Expect "California falls to 5th place in the World's economy" articles if the exchange rate trend reverses.
Absorption spectrums have never let us down, and are used all the time.
For this one place in the universe to have an exotic particle with an adsorption spectrum is pretty much impossible. To have an adsorption spectrum that is an exact mach for Barium is just adding a second impossible on top of the first.
Given the choice between something surprising and a doubly-impossible phenomena, the choice is clear.
But the 2022 version suffers from a number of issues that Google and Apple are both suffering from recently: a lack of focus on who this map is for. Is this map ornamental? Or is it for driving? Walking? Finding tourist locations? What is it for?
One of the obvious changes in OSM between 2012 and 2022 is the addition of building footprints at the cost of removing a lot of street names. At this scale, do footprints really help? Am I planning a walk and need to know the street name where I will turn? When you are close to a destination, yes the footprints help one identify the correct building. But not here.
Here's a Google Maps example: if you put Canada's Yukon Territory into frame, does it show you the major roads? No. Does it show you any roads? No. Even if you select "traffic" it doesn't get the hint that you care about driving. It just wants to show you a map of geography.
And now an Apple Maps example: put California into frame. Freeways and two-lane roads are shown as thin lines that are nearly invisible. Good luck planning a route with this map! Want to go from Point A to B? It can do it! But want to consider side trips or general routing yourself? Nope.
There's still no adequate substitute for a AAA map for driving. I suspect hikers, bikers, and walkers are also poorly served by these non-specialized maps too.
But I think it is more important to encourage good moderators to moderate more than it is to punish poor moderation.
Let's put this another way: every orbit is an ellipse. If you do not alter your orbit, you will only travel on the ellipse. The moment you stop interacting with the atmosphere, you are on a fixed ellipse. The problem is just behind you on the ellipse is the atmosphere, and if you continue forward on the ellipse you will inevitably come back to the part of the ellipse that is still in the atmosphere.
My comment about solid rockets is due to the fact that they include fully combustable fuel in a ready-to-use mix. Solid rockets don't require much input to get them to combust. I assume no one is considering solid rockets for this application; I only mention it as part of assuming they would need a liquid rocket so I could explain the problem with liquid rockets which rely on pumps and pipes.
Did you perhaps mean to respond to a different comment?
Instead, you have to fire a rocket motor to alter the initial orbit into one that doesn't intersect the ground. Now you have a new problem: you have to design a rocket motor which can withstand the launch. A solid rocket almost certainly will spontaneously RUD when heavy acceleration is applied. A liquid rocket has pumps and pipes which are likely can't survive the acceleration.
This is the reason spin launch is nonsense: you've traded a solved problem (make big rocket motor) for an unsolvable problem: make a rocket motor which can withstand absurd acceleration.
The other red flag with spin launch is that genuinely new approaches to problems do not come from unqualified randos thinking about a problem. For example, if a company has a crazy new idea for blood testing, it's really bad if the crazy new idea came from someone with zero experience and zero domain knowledge.
I dislike climate models for my own personal reasons... but they do predict continued acceleration. For example, in 2019 the IPCC predicted that by 2100 (80 years) the level would rise an additional 0.6-1.0 meters.
So the prediction is accelerated rise, and is backed up by observed recent acceleration.
A 3' increase in max high tides would probably cause some issues.
That said, there's no real standard blanket vendor recommendation so long as the "Enterprise" criteria is met.