Skip to main content

Second New Glenn Launch Slips Toward Fall As Program Leadership Departs

3 weeks 3 days ago
Blue Origin is falling far short of its goal to launch the New Glenn rocket eight times in 2025, with its second flight now delayed until at least mid-August. Key leadership changes were also announced, including the departure of the New Glenn program head, as the company faces pressure to increase launch cadence and compete with SpaceX for federal contracts and Amazon's Project Kuiper deployments. Ars Technica reports: The mission, with an undesignated payload, will be named "Never Tell Me the Odds," due to the attempt to land the booster. "One of our key mission objectives will be to land and recover the booster," [chief executive of Blue Origin, Dave Limp] wrote. "This will take a little bit of luck and a lot of excellent execution. We're on track to produce eight GS2s this year, and the one we'll fly on this second mission was hot-fired in April." In this comment, GS2 stands for "Glenn stage 2," or the second stage of the large rocket. It is telling that Limp commented on the company tracking toward producing eight second stages, which would match the original launch cadence planned for this year. This likely is a fig leaf offered to Bezos, who, two sources said, was rather upset that Blue Origin would not meet (or even approach) its original target of eight launches this year. One person familiar with the progress on the vehicle told Ars that even a launch date in August is unrealistic -- this too may have been set aggressively to appease Bezos -- and that September is probably the earliest the rocket is likely to be ready for launch. Blue Origin has not publicly stated what the payload will be, but this second flight is expected to carry the ESCAPADE mission for NASA. On May 28, a couple of days after Limp's all-hands meeting, the chief executive emailed his entire team to announce an "organizational update." As part of this, the company's senior vice president of engines, Linda Cova, was retiring. Multiple sources confirmed this retiring was expected and that the company's program to produce BE-4 rocket engines is going well. However, the other name in the email raised some eyebrows, coming so soon after the announcement that New Glenn's cadence would be significantly slower than expected. Jarrett Jones, the senior vice president running the New Glenn program, was said to be "stepping away from his role and taking a well deserved year off" starting on August 15. It is unclear whether this departure was linked to Bezos' displeasure with the rocket program. One company official said Jones' sabbatical had been planned, but the timing is curious. A search for internal and external candidates to fill his role is ongoing.

Read more of this story at Slashdot.

BeauHD

CodeSOD: The Pirate's Code

3 weeks 3 days ago

We've talked about ASP .Net WebForms in the past. In this style of development, everything was event driven: click a button, and the browser sends an HTTP request to the server which triggers a series of events, including a "Button Click" event, and renders a new page.

When ASP .Net launched, one of the "features" was a lazy repaint in browsers which supported it (aka, Internet Explorer), where you'd click the button, the page would render on the server, download, and then the browser would repaint only the changed areas, making it feel more like a desktop application, albeit a laggy one.

This model didn't translate super naturally to AJAX style calls, where JavaScript updated only portions of the page. The .Net team added some hooks for it- special "AJAX enabled" controls, as well as helper functions, like __doPostBack, in the UI to generate URLs for "postbacks" to trigger server side execution. A postback is just a POST request with .NET specific state data in the body.

All this said, Chris maintains a booking system for a boat rental company. Specifically, he's a developer at a company which the boat rental company hires to maintain their site. The original developer left behind a barnacle covered mess of tangled lines and rotting hull.

Let's start with the view ASPX definition:

<script> function btnSave_Click() { if (someCondition) { //Trimmed for your own sanity //PostBack to Save Data into the Database. javascript:<%#getPostBack()%>; } else { return false; } } </script> <html> <body> <input type="button" value=" Save Booking " id="btnSave" class="button" title="Save [Alt]" onclick="btnSave_Click()" /> </body> </html>

__doPostBack is the .NET method for generating URLs for performing postbacks, and specifically, it populates two request fields: __EVENTTARGET (the ID of the UI element triggering the event) and __EVENTARGUMENT, an arbitrary field for your use. I assume getPostBack() is a helper method which calls that. The code in btnSave_Click is as submitted, and I think our submitter may have mangled it a bit in "trimming", but I can see the goal is to ensure than when the onclick event fires, we perform a "postback" operation with some hard-coded values for __EVENTTARGET and __EVENTELEMENT.

Or maybe it isn't mangled, and this code just doesn't work?

I enjoy that the tool-tip "title" field specifies that it's "[Alt]" text, and that the name of the button includes extra whitespace to ensure that it's padded out to a good rendering size, instead of using CSS.

But we can skip past this into the real meat. How this gets handled on the server side:

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load '// Trimmed more garbage If Page.IsPostBack Then 'Check if save button has been Clicked. Dim eventArg As String = Request("__EVENTARGUMENT") Dim offset As Integer = eventArg.IndexOf("@@@@@") If (offset > -1) Then 'this is an event that we raised. so do whatever you need to here. Save() End If End If End Sub

From this, I conclude that getPostBack populates the __EVENTARGUMENT field with a pile of "@", and we use that to recognize that the save button was clicked. Except, and this is the important thing, if they populated the ID property with btnSave, then ASP .Net would automatically call btnSave_Click. The entire point of the __doPostBack functionality is that it hooks into the event handling pattern and acts just like any other postback, but lets you have JavaScript execute as part of sending the request.

The entire application is a boat with multiple holes in it; it's taking on water and going down, and like a good captain, Chris is absolutely not going down with it and looking for a lifeboat.

Chris writes:

The thing in its entirety is probably one of the biggest WTFs I've ever had to work with.
I've held off submitting because nothing was ever straight forward enough to be understood without posting the entire website.

Honestly, I'm still not sure I understand it, but I do hate it.

[Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!
Remy Porter