> Rewriting critical software infrastructure (infostructure) to more reliable typed languages
Instagram (and Threads) is still using Django, which is even slower than Rails. Once you get to unicorn scale, your app is going to bespoke, with some microservices, and super custom stuff. If you can go faster in a gradually typed language, that can be a very good reason to choose one.
> untyped languages are not performant
Typing generally slows down languages, not speed them up because of all the additional checks that must be done. The dynamic stuff is part of what slows down languages like Python and makes them tricky to optimize.
> Typing generally slows down languages, not speed them up because of all the additional checks that must be done.
Source? You seem to be talking about compile-time versus runtime, and I've not even heard of compile times being significantly slowed by type checking.
> The dynamic stuff is part of what slows down languages like Python and makes them tricky to optimize.
That seems to harm rather than help your previous claim. In untyped languages, in principle every object has to be treated as dynamic.
> You seem to be talking about compile-time versus runtime
Yes 100%! I was talking runtime in reference to Ruby and later Python.
> That seems to harm rather than help your previous claim. In untyped languages, in principle every object has to be treated as dynamic.
It is rather confusing and even counterintuitive, but being dynamic does not mean a language must also be untyped. For example, Python is both strongly typed and dynamically typed at once. [1] It's objects have a definitive type, but you can swap out objects of any type out at any time (a=1 ... a="foo") using the same variable. That makes optimization rather tricky as you can imagine.
> Thus the treatment had provided them a median life extension of about 3/4 years. The lucky ones probably have got more than an extra year.
The 'median' patient in this trial lived ~6.6m longer if they received daraxonrasib. It's worth noting that the performance of the chemotherapy arms was stronger in this trial than previous trials of second-line chemotherapy; whether this reflects better care or a prognostically-superior trial population remains to be seen.
I have quoted exactly the numbers that were written in the abstract of the article yesterday, at the same link that you have used.
What is very weird is that the abstract of the article has been changed, and now it is as you say.
So the numbers from today are worse than those from yesterday.
Perhaps the abstract of yesterday corresponded with a preliminary version of the study report, but meanwhile more patients have died, which has been taken into account in the final version, lowering both the median values for overall survival and for progression-free survival.
No offense intended. I guess someone in the RevMed Scientific Comms team had a more stressful day than they'd envisaged.
> Perhaps the abstract of yesterday corresponded with a preliminary version of the study report, but meanwhile more patients have died, which has been taken into account in the final version, lowering both the median values for overall survival and for progression-free survival.
No. The 'data cut' that these numbers are based on will have been taken (at least) weeks ago. You don't get (anything close to) real-time updates in the manner that you're implying. It was probably just a simple snafu somewhere along the line.
> I don’t want to defend the cure administration, but it’s very common and normal for a country to require a person to leave to change status.
This new policy is different than the "flag poling" you've described. The new guidance requires immigrants to return to their country of origin, then apply for the change in status, and wait in their country of origin while the change in status is being processed/considered which can take many years. If the status changed is approved, they can move back to the US.
Because the words temporary amd nonimmigrant don't carry the meaning that you're imbuing into them. Fiance visas operate very similarly to these dual intent H1 visas. You're granted a temporary nonimmigrant status while you pursue a permanent one. The words nonimmigrant and temporary doesn't exclude pursuing a permanent status at all.
In the case of a K-1, it is assumed you will transition from a temporary nonimmigrant status to a permanent status. [1] Requiring folks to move to the U.S., and then go back out of the country to get a green card, only to return again, is absurd. That absurd dance for both K1 and H1 w/dual intents is the reason the laws and guidance provided to agents changed starting in the 50's through the 90's. These changes in guidance to agents are nothing more than a thinly veiled attempt to suppress people coming to the U.S. lawfully, which is absurd and deeply anti-American.
The K1 visa is even more temporary! It’s only for 90 days, and under the section 1255(d), the government doesn’t even have the power to convert a K1 visa into permanent residency. It’s like a tourist visa. The visa itself is not a pathway to anything.
People who come here on a K1 get permanent residency once they get married through a different statutory route: 8 USC 1154. But that has nothing to with the K1 itself. That route is available to anyone married to a US citizen, including illegal immigrants under certain conditions, or aliens who get married abroad. The K1 visa isn’t a stepping stone to permanent status. It’s just a convenience that allows people to have the wedding in the U.S. instead of the spouse’s home country.
> It’s like a tourist visa. The visa itself is not a pathway to anything.
> ...
> People who come here on a K1 get permanent residency once they get married through a different statutory route: 8 USC 1154. But that has nothing to with the K1 itself.
The UCIS explicitly links the K-1 (which has the words temporary and non-immigrant visa scattered throughout) to a de facto path to permanent status (see below). The fact that the two are different statutes is moving the goal posts (i.e., a logical fallacy). The government clearly sees them as a linked pathway to permanent status.
> "If you are a U.S. citizen who wants to bring your foreign fiancé(e) to the United States in order to get married"
> The K1 visa isn’t a stepping stone to permanent status. It’s just a convenience that allows people to have the wedding in the U.S. instead of the spouse’s home country.
There's a reason they require a medical exam to be filed with the consulate as a part of the K-1 application, they expect you to be in the U.S. for a long time. K style visas are a lot more than a convenience, they are the law of the land and have been so for nearly 75 years.
> There is a reason the US Navy fled the Persian Gulf on Feb 26 and has not returned since.
Two US Arleigh Burke Class Destroyers transited Hormuz a couple of weeks ago without damage and are still there last I heard. The Iranians were really upset, but couldn't do anything to stop it.
In Gulf War II, the US had three carrier groups inside the gulf. In between wars, the US fifth fleet was unchallenged in those waters, with its headquarters at the massive naval complex in Bahrain.
In the last 4 months, they have completely evacuated the gulf. They have attempted to run the strait twice and left immediately. The naval base has been severely damaged, and their long range radars destroyed. Even if the radars were somehow restored, it is unclear they would have the munitions to defend their fleet or bases for longer than a few days/weeks.
It is impossible to overstate what a strategic disaster this has been for the US military. In their wildest dreams, Iran couldn't have imagined this situation unfolding the way it did.
I had not heard about that transit, thanks for sharing! The ships mentioned in our two links match up, so it certainly sounds like they spent a some number days in the Persian Gulf and transited back. There was also a transit that occurred in April which mentioned other ships joining the operation in the future, not sure if that happened or not.
Transiting by themselves is a lot different than escorting merchant vessels. By themselves warships are free to maneuver at any time and do so at military speeds. Convoy duty with merchant vessels requires repeatedly moving slowly along a predictable route for sustained periods. Mobility and speed are two of a warship's main strengths.
The extreme narrowness of the strait right next to so much enemy-controlled shoreline is a unique problem. All of the destroyers and frigates from all the world's navies combined couldn't sustain protecting the massive number of merchant vessels wishing to transit the Strait of Hormuz on a daily basis.
> Transiting by themselves is a lot different than escorting merchant vessels
The second crossing was conformed to be such an escort mission. They shot down everything Iran threw at them, but the cost assymetry still holds.
> All of the destroyers and frigates from all the world's navies combined couldn't sustain protecting the massive number of merchant vessels wishing to transit the Strait of Hormuz on a daily basis.
My point exactly: the argument that the "US Navy isn't as large as it used to be" is moot
Ships don’t need escort services because you don’t give command of oil tankers to risk taking thrill seekers. And insurance isn’t enough when the captain is literally on the ship, potentially getting killed.
Warships vs. insurers willing to underwrite a policy for merchant vessels to transit are definitely two very different things. The Iranian Government has a much higher pain threshold/resolve than Trump, but they're also in a lot more pain with the Gulf of Oman closed. Both sides are losing, who will get tired of it first?
China hasn't seen 10% GDP growth for 15 years. It will likely fall in the 4-5% range this year as it was last year. China has a self-inflicted population decline problem that the U.S. doesn't, which will weigh on China's future growth prospects.
This is brilliant, I was not aware of ITCSS. Thank you for sharing! The link you shared fits my brain a lot better than pure BEM/CUBE, which works but always felt weird and uncertain to my style. Sprinkling a bit of BEM on top of ITCSS feels just right. shame.scss is the snarky cherry on top. Thanks again, you have enlightened at least on person today! :)
Iran cannot get their oil out of their country fast enough. Iran's oil storage facilities are filling up, as evidenced by them bringing in derelict tankers just to temporarily store oil. If they have to start capping wells, they will almost certainly never produce at the same rate again, if they can start the flow at all since capping typically damages the well to some extent. If it comes to that, Iran will be permanently diminished. Hard to see how Iran will come out of this a winner as the article projects. You need money to pay for a war.
> I think the fact that they reached 2B/mo in revenue by dogfooding cc is all the proof that one needs that this thing actually works.
That's a notable achievement, but let's have some balance... It's also responsible for the biggest self-own in software industry history by leaking their 1) crown jewels (i.e., source code) 2) the existence of their next model Mythos, and 3) their roadmap in a highly competitive market.
Eh... I personally think that having the keypads to enter a DC running on DNS served by that same DC is a bit more self-owning than leaking the source code of an app, but I get your point. It's obviously not perfect, but it's also obviously working.
Let's put this in perspective. Imagine it's 3 years ago, April 2023. Chatgpt has been launched for 4 months. We've all been using it, and writing poems in parrot talk or whatever. Someone tells you "In 2 years time there will be an app that lets you use LLMs to write code. It will be coded by humans for 3 weeks, then by humans + LLMs for 6 months, and then by LLMs mostly unsupervised. One year after that, they'll be making 2B/mo out of that app". Would you believe them? Not even the most maximalist, overhypers, AI singularity frenzied crazy people would have said that. And yet... it happened.
> Audio quality is decent here too. Listening to "Fast Car" now, and the quality is solid. :)
Fast Car was terrific, thanks for sharing! It is especially amazing considering this recording was made in 1988, just one month and one day (how poetic!) after Fast Car was released as a single.
"Talkin' Bout A Revolution" is in there as well, and some stuff marked as "unreleased".
The entire Tracy Chapman recording there is actually really well put together. The volunteers who did the work to transfer it from cassette and clean it up, did an outstanding job on this one.
Instagram (and Threads) is still using Django, which is even slower than Rails. Once you get to unicorn scale, your app is going to bespoke, with some microservices, and super custom stuff. If you can go faster in a gradually typed language, that can be a very good reason to choose one.
> untyped languages are not performant
Typing generally slows down languages, not speed them up because of all the additional checks that must be done. The dynamic stuff is part of what slows down languages like Python and makes them tricky to optimize.
reply