This feels like a fairly uncharitable take. The author conveniently left out all of the things needed to understand that JavaScript version, including async/await, promises, modules, string interpolation, lambda syntax, not to mention the runtime that is running this, etc.
You also don’t have to start with a program that invokes 20 concepts at once, every one of those rust concepts can have its own hello world, introducing one concept at a time. Frankly several of them are just fundamental CS concepts.
> The author conveniently left out all of the things needed to understand that JavaScript version, including async/await, promises, modules, string interpolation, lambda syntax, not to mention the runtime that is running this, etc.
I think I disagree that you can have a Rust program that doesn't use all these concepts, at least outside of very basic tutorial material. You will very very quickly run into compiler errors that mention them the second you write your own program.
> The author conveniently left out all of the things needed to understand that JavaScript version, including async/await, promises, modules, string interpolation, [...] not to mention the runtime that is running this, etc.
I mean both languages (and programs) have modules, string interpolation, lambda syntax, and a compiler/interpreter. The only thing they really left out is Promises. And you're iterating over an array so there's no understanding of iterators needed. You can write Python for a long time without ever learning about __iter__. In the example Rust program the iterator is exposed. I think if the Rust version only used the for syntax you could say you don't need to know about iterators.
Javascript has exceptions (the article even mentions them, but seems to assume that they're somehow intuitive?) whereas Rust doesn't. And the Javascript "first-class function" syntax isn't really objectively simpler than the Rust lambda syntax, which the article seems to assume.
As I read it,
the author is making a point about explicit vs implicit knowledge.
In the Rust version the compiler will ~yell at you~ politely point out where your code won't work,
while the js version will ... just run, but maybe not work?
Not really, he explicitly makes the point that it's easier to write useful simple programs in Javascript without the extra stuff, whereas in Rust you need to know about a whole lot of things to make the equivalent simple program.
You should try building one for yourself, I did [1] and it’s easier than you’d think. I made mine just a basic numpad but I really like the idea of turning it into a tool to enter math symbols.. guess I know what my next project is, thanks for the inspiration!
I released two apps built in dart on flutter. I loved it at the time, but I ran into this issue headlong with both of them. Release v1.0, move on to other things, come back in a year with a new computer to fix a minor bug and I can’t even compile the original release anymore, and had to spend forever rejiggering everything to get it back to the state it was when I left it. I really loved dart, and even flutter, building in it was a breeze. But the churn made the js ecosystem look slow.
Plasma can be used outside of prophylactics as well, I don't think this is accounted for in the article (human plasma is used in cosmetics for example).
A lot of plasma is also separated out of whole-blood donations and manufactured into all sorts of things. I don't know all of the end-user financial ramifications of this, but hospitals absolutely do pay (sometimes quite a pretty penny depending on rarity of antigens and antibodies) for RBCs and platelets (and plasma) from suppliers like the American Red Cross.
Purely anecdotally, I have heard stories of some donors being compensated extremely handsomely for their regular donations because of the rarity of their blood attributes - even being flown across the country and wined and dined to obtain their blood on top of thousands of dollars per donation.
Everything is Tuberculosis [1] answers just that. Essentially it boils down to staggering wealth inequality and the aftershocks of colonialism
. The west “cured” TB 70 years ago then stopped caring about it. There isn’t a enough profit in preventing a million deaths a year in the rest of the world, so we just.. don’t.
Oh yes, the billions of dollars and decades of work specifically for the 3rd world to fight TB never happened and the cash was burned in a big bonfire.
The premise sounds interesting, but it seems a bit reductionist if it boils down to that, no? Is the book looking at it through the lens of government actions or private charities? I'm not aware of any evidence that suggests charities simply stopped operating because of capitalism.
The book includes privates charities and governments, but looks at TB through many more lenses than just those. There is a reason it’s a whole book and not just a comment on an Internet forum. I just finished the book and highly recommend the read, if only to learn about something that I suspect most of us (myself at least, certainly), is known only as _history_, not the raging health crisis that is continues to be.
I made my own distributed render orchestrator that supports Cycles + custom plugins. It uses Modal’s cloud compute APIs to spawn jobs on up to 20x containers with an L40S GPU (like 80% as fast as a 4090 with tons more VRAM) each. It ain’t cheap but it’s absurdly fast, and much easier in terms of cash flow than outright buying the equivalent GPUs.
Another YouTube cooking personality I really like is Internet Shaquille (https://m.youtube.com/@internetshaquille). His videos are very informationally dense without engaging in many of the typical YouTuber nonsense. And the ads are always at the end.
Yes, I love this guy's stuff. His style is very unique, expertly knowledgeable while still completely casual and humble. Like a very smart friend teaching you, rather than being in a class.
It took me a bit to warm up to them, but now I find myself relying on them to more quickly spot errors, so yes it ends up faster. Somewhat counterintuitively, I find the ligature characters easier to process at a glance and see if there's a problem or not (I suspect its something along the lines of my brain looks at "<=" as two separate characters, one after the other, and has to process each in serial then combine them into the concept of "less than or equal to", whereas the ≤ is a single character that goes straight to the "less than or equal to" concept in the same way its easier to remember the number "six hundred ninety-three" than "six, nine, three". I also find it way easier to spot the "≡" vs the "===" in JS land, which surprised me but here I am.
I wouldn't say its harder to go back, but it does make me do a double take. Overall I would say the effect is quite minor and I'm just fine without the ligatures, but given the option I would enable / prefer them.
You also don’t have to start with a program that invokes 20 concepts at once, every one of those rust concepts can have its own hello world, introducing one concept at a time. Frankly several of them are just fundamental CS concepts.