You can't deliver a payload to orbit if you're not planning on going to orbit. They have a launch licence for a particular mission plan.
The license for Falcon 9 and Falcon Heavy specifically says “Authorization: SpaceX is authorized to conduct flights of
launch vehicles: […] (c) Transporting Dragon 2 to low Earth orbit or a payload
to orbit;”
The license for Starship/Super Heavy Launch Vehicle does not include such an authorization.
"The payload is data." Elon
The data they get from the test and they focus on getting the most and most valuable data.
This is an explicit choice.
A physical payload at this stage would reduce the overall value that they are able to get from a flight.
How is self-driving a 2D problem when you navigate a 3D world? (please do visit hilly San Francisco sometime) not to mention additional dimensions like depth, velocity vectors among others.
The visual input and sensory input to the self driving function are of the 3D world but the car is still constrained to move along a 2D topological surface, it’s not moving up and down other than by following the curvature of that
So based on your argument they actually operate in 1D since roads go in one direction and lanes and intersections are constrained to a predetermined curly line.
The point is clearly that they don’t have a vertical axis of control, they can’t make the car fly up in the air unless they’re driving crazy taxi style
1. Given millions of things that are perfect it takes one of them for HN to lose its mind, power button happened to be it this time, Cook didn't decide that.
2. How often do people exactly have to turn off and on a mac that consumes less than a pi for them to constantly be reaching out to that power button?
It's not like Tim Cook personally decided to put the button there, but saying over many years he's aligned the company to be one that would leave the button there rather than bite the cost of putting it somewhere more ergonomic is something I can buy into. Seems like a way to improve margins generation over generation, which is the kind of thing he's obsessed with.
This is also the same Apple that made the G4 Cube: that felt like this in reverse, with Jobs driving them to make a capacitive touch button because of an obsession with a seamless surface.
Yes that's it. Jobs's annoyances were always about achieving a better product, a higher level of refinement or something of the sort. It was mostly about, "it can be better this way" and he was very often right even though sometimes not.
On the other hand, with Cook, it's always about cost cutting and corner cutting and the likes. It feels cheap (especially considering the pricing and brand aspirations) but also primitive and unrefined.
Which is why their price escalation was unjustified, if you want to charge a lot you need to figure out a no compromise product and, in my opinion, they have not been there a lot recently...
I often choose 144p for low bandwidth scenarios. It is very similar to a good quality audio-only stream in terms of size, but you get the added benefit of looking at the speaker even if that's a glance every 45 mins. Same for battery life, you save that too.
Also 144p is somehow so peaceful and relaxing to watch, you don't get distracted with all the shiny colors and intricate details in the video and can just listen and not have your mind focus on some random stuff.
Why do you need webgpu? It's unfortunate that people use technology that is "state-of-the-art techniques to run simulations at interactive speeds" without fully understanding what it's for. General compute on GPU is what webgpu is for.. To simulate basic waves like in this demo you absolutely do not need that, in fact it's an indication the author implemented the solution in a non-optimal way. WebGL is fully supported by all browsers fully supported by well-maintained libs like 3js, yet here we are people writing a sin function with basic interference patterns, one of the most elementary 3D primitives, in webgpu and argue that's using the "state-of-the-art" techniques.
Good question! This is actually a numerical solver for a few coupled partial differential equations - the method in this context (electromagnetism) is called FDTD. It's implemented as a WebGPU compute shader.
You absolutely could do this using WebGL2 compute shaders too, but I thought it would be fun to try this newer API.
and then a bunch of other GPU code. You can find this with little effort from the bundle, if you care, by base64-decoding the Pt("xxx") parts.
Though I do imagine it indeed could be implementable with WebGL shaders, but I also wouldn't start a new compute-based on it, unless I had a particular need to support older systems. And this I say as a Firefox user..
The flights could deliver cheap payload for example.
reply