frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open in hackernews

SpaceX launches Starship v3 rocket

https://www.nbcnews.com/now/video/spacex-successfully-launches-prototype-of-starship-rocket-263835205505
58•busymom0•1h ago

Comments

tectonic•55m ago
Seeing both the Starlink mass simulators deploy and the camera view from the last simulators looking back at Starship was really cool.
NitpickLawyer•55m ago
Oh man, so glad I stayed up to watch it. Kind of a rough start (but it's the 1st flight w/ new redesign, new engines, etc), had an engine out on both booster and ship, but the views were absolutely worth it. They managed to get the last satellite to connect to starlink and download the footage of the ship in orbit. Even with an engine out, the ship managed to reach orbit, deploy all the satellites, re-enter, flip and soft splash into the ocean, near a buoy! And on top of that we got the drone views of the landing. Fucking spectacular views.
Geee•48m ago
I'm guessing / hoping that the engine outs we're planned, or that they ran the engines with slightly different parameters to test them. If it's just unreliability then it might be a hard problem to solve.
Octoth0rpe•45m ago
> If it's just unreliability then it might be a hard problem to solve.

It might, but it certainly helps having a ton of them around. Given that they used 42 of them today and 2 failed in some fashion, we'll call that a 1:21 failure rate. On a more typical rocket with say 10 engines (eg falcon 9), there's a good chance they wouldn't have seen the same failure till flight 3.

brianwawok•40m ago
It’s something like up to 6 can fail and it keeps going, seems pretty good. I know they did some stuff like remove a heat tile to get failure feedback, wonder if engine was planned or accidental
NetMageSCW•31m ago
Accidental since they didn’t make the sub-orbit they were aiming for and thus couldn’t test engine re-light.
Zee2•41m ago
Very first flight of a brand new engine type (Raptor 3) with totally reworked heatshielding/plumbing/sensors/control systems/etc.
ajross•31m ago
Which is true, but at the same time: this is Starship Flight 12.

The whole point of Starship is that it's a reusable vehicle with easy turnaround and quick maintenance. And in particular it's supposed to be different than the other reusable vehicle with easy turnaround and quick maintenance, which turned out to be sort of a boondoggle.

Yet, they've now hand-built and destroyed twelve of these things across multiple redesigns, and it still hasn't completed its design mission once. In fact basically every launch has unexpected major failures.

As poor as its safety record ultimately ended up being, the shuttle launched successfully on its very first try. And we only had to hand-build five of them. And lost two, sure, which is still a lot less than twelve.

Yes yes, I understand that iterative design has merits and that the ability to rapidly prototype and try things in the stratosphere allows for less conservative tolerances and better ultimate performance.

But does it really take 13+ tries?! At what point to we start wondering if we have another boondoggle on our hands?

redox99•21m ago
If you can afford it, I'm sure anyone developing a rocket would prefer to do it this iterative way. I don't really understand the complain.
p-e-w•19m ago
But all of those 12 launches happened in just 3 years, and cost a tiny fraction of other major spaceflight development programs.

For reference, SLS has been in development for 5 times as long, and cost 15-20 times as much, as Starship, and they still haven’t landed people on the Moon, which has been one of the stated goals since the Constellation program in 2005.

I don’t see how the number of failures matters if the end result still happens faster and cheaper than anything else.

bbatha•10m ago
Moreover the two lost shuttles included human lives. Better to blow stuff up with demo payloads now before sending up large contracted payloads or worse human beings!
p-e-w•3m ago
I couldn’t believe my ears when I first heard that the second ever flight of SLS was going to be crewed.

It worked out in the end, but I can’t imagine being so confident in a new system, no matter how much money and brainpower has been spent to make it safe.

ammut•18m ago
It really was an amazing sight to see.
generuso•29m ago
The views from Ship's engine bay looked rather ominous -- with the red glow visible in multiple places, and something venting furiously from the broken engine. It was a pleasant surprise that the ship did not explode and not only that, but it even landed exactly on target. Guidance system software engineers have done a very good job!

The booster not completing the return part of the flight was disappointing. They had a similar incident in one of the previous flights, when they tried to maneuver the booster too aggressively immediately after stage separation which caused problems with the fuel supply. If it was something similar this time, it might be solvable by changing just a few details of the maneuver. So, maybe it is not that huge of a deal.

There were many cool things in the webcast, from them showing the catamarans that are deployed at the landing site, to the views form the cameras on-board of the "satellites". The first few minutes after liftoff were just amazing visually.

lysace•28m ago
Cool splashdown.

https://www.youtube.com/watch?v=CiWX1nsvqBs&t=170s

Laremere•18m ago
Summary from my watch:

- Launch roughly on time, after a scrub yesterday. (Sounds like the scrub was due to ground equipment, most notably the water system.)

- Initial ascent was good, but then one engine on the booster went out.

- Relight of the booster's engines after stage separation for the boost back burn failed. Engines did light again for a landing burn, but seems to have hit the water harder than expected and was very off target.

- Starship lost one engine shortly after stage sep. Turned into an unintentional test of engine out capability. It made it to space.

- Some weird motion and lots of off-gassing after engine cut-off, with uncertainty about if it actually got a good orbital(ish) insertion. Seems to have been benign, with the motion being a weird slow flip to the orientation for payload deployment.

- Test deployment of dummy payloads was successful, including a couple with cameras to look back at Starship.

- An in space engine relight test was skipped, presumably due to the issues during launch.

- Re-entry to over the Indian Ocean seemed to go really well. Nothing obviously burning or falling off. The amazing views of the plasma during re-entry, something never seen live before starship, are now routine.

- Starship did a maneuver to simulate how they'll have to go out over the gulf and back to the landing site.

- Nailed the target, evidenced by views from drones and buoys. Soft landing before falling over and giving us a big (expected) boom.

As far as overall progress from previous test flights goes, they're at least treading water while making many large changes. I think they were hoping to try for a tower catch and actually going orbital for next flight, but I highly doubt that now. The boostback burn failing was the largest failure, with the engine failure on Starship being a close second. Good performance despite engine out seems to be an unintentional success.

maxlin•1m ago
Having a faultless payload deploy and a pinpoint landing after losing a whole vacuum engine (one of 3) so early was an unexpectedly amazing performance. I suppose they gimballed the inner non-vac engines to the max and burned longer, next level adaptability.

Most obvious improvement was having no re-entry heating problems, secondmost was deploying with zero issues and with a faster pace. It appears they decided to pause the "horizontal" movement of the pez dispenser before a final push away, probably to avoid vibration causing those "bonks" on the payload door, like we had once before.

Don't just paste the AI at me

https://dontquotetheai.com/
110•khaosdoctor•2h ago•64 comments

Shipping a Laptop to a Refugee Camp in Uganda

https://notesbylex.com/shipping-a-laptop-to-a-refugee-camp-in-uganda
152•lexandstuff•3h ago•32 comments

Why Japanese companies do so many different things

https://davidoks.blog/p/why-japanese-companies-do-so-many
463•d0ks•9h ago•268 comments

Project Glasswing: An Initial Update

https://www.anthropic.com/research/glasswing-initial-update
285•louiereederson•5h ago•187 comments

A Wayland Compositor in Minecraft

https://modrinth.com/mod/waylandcraft
109•Jotalea•2d ago•23 comments

Sleep research led to a new sleep apnea drug

https://temertymedicine.utoronto.ca/news/how-decades-sleep-research-led-new-sleep-apnea-drug
45•colinprince•2h ago•22 comments

Open source Kanban desktop app that runs parallel agents on every card

https://www.kanbots.dev/
157•vitriapp•6h ago•89 comments

Lawmakers Demand Answers as CISA Tries to Contain Data Leak

https://krebsonsecurity.com/2026/05/lawmakers-demand-answers-as-cisa-tries-to-contain-data-leak/
114•speckx•8h ago•34 comments

SpaceX launches Starship v3 rocket

https://www.nbcnews.com/now/video/spacex-successfully-launches-prototype-of-starship-rocket-26383...
60•busymom0•1h ago•18 comments

Comparing an LZ4 Decompressor on Four Legacy CPUs

https://bumbershootsoft.wordpress.com/2026/05/09/comparing-an-lz4-decompressor-on-four-legacy-cpus/
19•tosh•2d ago•0 comments

I’m Writing Again

https://www.cringely.com/2026/05/21/im-writing-again/
88•dan_hawkins•10h ago•23 comments

Deno 2.8

https://deno.com/blog/v2.8
299•roflcopter69•13h ago•136 comments

Antigravity 2.0 Tops the OpenSCAD Architectural 3D LLM Benchmark

https://modelrift.com/blog/openscad-llm-benchmark/
341•jetter•14h ago•132 comments

Wi-Wi is wireless time sync at 1 nanosecond

https://www.jeffgeerling.com/blog/2026/wi-wi-is-wireless-time-sync-less-than-5ns/
77•Brajeshwar•2d ago•11 comments

1940 Air Terminal Museum Begins Liquidation

https://www.1940airterminal.org/news/liquidation-of-simulators
81•weaponeer•7h ago•27 comments

Bun support is now limited and deprecated

https://github.com/yt-dlp/yt-dlp/issues/16766
348•tamnd•7h ago•366 comments

Models.dev: open-source database of AI model specs, pricing, and capabilities

https://github.com/anomalyco/models.dev
95•maxloh•4h ago•12 comments

A blueprint for formal verification of Apple corecrypto

https://security.apple.com/blog/formal-verification-corecrypto/
51•hasheddan•6h ago•1 comments

Blood Pumping Mechanism of the Hoof

https://horses.extension.org/blood-pumping-mechanism-of-the-hoof/
5•thunderbong•2d ago•0 comments

FBI director's Based Apparel site has been spotted hosting a 'ClickFix' attack

https://www.pcmag.com/news/kash-patels-apparel-site-is-trying-to-trick-visitors-into-installing-m...
10•bilalq•24m ago•1 comments

Launch HN: Superset (YC P26) – IDE for the agents era

https://github.com/superset-sh/superset
77•avipeltz•10h ago•94 comments

A Forth-inspired language for writing websites

https://robida.net/entries/2026/05/21/a-forth-inspired-language-for-writing-websites
98•speckx•9h ago•13 comments

U.S. researchers face new restrictions on publishing with foreign collaborators

https://www.science.org/content/article/u-s-researchers-face-new-restrictions-publishing-foreign-...
327•ceejayoz•8h ago•200 comments

If you’re an LLM, please read this

https://annas-archive.gl/blog/llms-txt.html
721•janandonly•13h ago•401 comments

Project Hail Mary – Stellar Navigation Chart

https://valhovey.github.io/gaia-mary/
1136•speleo•1d ago•228 comments

Thinking in an array language (2022)

https://github.com/razetime/ngn-k-tutorial/blob/main/12-thinking-in-k.md
44•tosh•7h ago•7 comments

Domain-Camouflaged Injection Attacks Evade Detection in Multi-Agent LLM Systems

https://arxiv.org/abs/2605.22001
32•sbulaev•6h ago•4 comments

YAML? That's Norway Problem

https://lab174.com/blog/202601-yaml-norway/
12•theanonymousone•1d ago•5 comments

DeepSeek makes the V4 Pro price discount permanent

https://api-docs.deepseek.com/quick_start/pricing
296•Tiberium•8h ago•172 comments

The memory shortage is causing a repricing of consumer electronics

https://davidoks.blog/p/ai-is-killing-the-cheap-smartphone
465•d0ks•1d ago•565 comments