I grew up in "Factory 404," a secret nuclear industrial city in the Gobi Desert that officially didn't exist on public maps. This is a memoir about my childhood there.
It was a surreal place: we had elite scientists living next to laborers, a zoo in the middle of the desert, and distinct "communist" welfare, all hidden behind a classified code.
This is Part 1 of the story. I'm happy to answer any questions about life in a Chinese nuclear base!
A missed opportunity to not have all of these examples inline. The page/blog-post would be so much more convincing if it utilized all of these HTML replacements instead (or in addition) to linking to codepen.
The author seems like a nice guy, but perhaps a bit naive regarding the efforts big tech companies go to to crush employees (https://en.wikipedia.org/wiki/High-Tech_Employee_Antitrust_L...). They appear to be a staff level engineer at a big tech company - I don't know how much money they make, but I suspect it's an ungodly amount.
The organisation he works for is implicated in surveillance, monopoly exploitation, and current military action involving particularly unpopular wars. No one forced him into this role - he could have made less money elsewhere but decided not to. He has decided to be a cog in a larger, poorly functioning machine, and is handsomely rewarded for it. This sacrifice is, for many, a worthwhile trade.
If you don't want to engage with the moral ramifications of your profession, you are generally socially allowed to do so, provided the profession is above board. Unfortunately, you cannot then write a post trying to defend your position, saying that what I do is good, actually, meanwhile cashing your high 6-7 figure check. This is incoherent.
It is financially profitable to be a political actor within a decaying monopolist apparatus, but I don't need to accept that it's also a pathway to a well-lived life.
The neatnik calendar is very nice. Others are talking about enhancements they've done and I've done my own, creating a pretty faithful JavaScript implementation with enhancements:
As a lover of Rust, ooo boy does this sound like a bad idea. The Rust compiler is not guaranteed to always output safe code against malicious inputs given that there’s numerous known soundness bugs that allow exploiting this. Unless I’m missing something this is a security nightmare of an idea.
Also there’s reasons why eBPF programs aren’t allowed to run arbitrarily long and this just ignores that problem too.
I don't mind how Liquid Glass looks at all. It's just insane how buggy the system has become. Even Messages will bug out, like deleting my first word if I type too fast after opening a conversation or auto scrolling and not letting me scroll down until I exit and re-enter.
Unacceptable for the premium you pay for Apple software. Unacceptable for any software one is paying for. I hope they get their shit together and start fixing before they continue adding new stuff. 26.2 doesn't inspire me that they're on that trajectory.
The thing that amazes me most is that everyone on the teams responsible is probably using their Apple devices and running into these same bugs!
The submitted title is missing the salient keyword "finally" that motivates the blog post. The actual subtitle Raymond Chen wrote is: "C++ says “We have try…finally at home.”"
In other words, Raymond is saying... "We already have Java feature of 'finally' at home in the C++ refrigerator and it's called 'destructor'"
To continue the meme analogy, the kid's idea of <X> doesn't match mom's idea of <X> and disagrees that they're equivalent. E.g. "Mom, can we order pizza? No, we have leftover casserole in the fridge."
So some kids would complain that C++ destructors RAII philosophy require creating a whole "class X{public:~X()}" which is sometimes inconvenient so it doesn't exactly equal "finally".
> “This study shows that paternal exercise can confer benefits — enhanced endurance and metabolic health — to offspring,”
So good habits can be good for offspring.
> For instance, mouse fathers exposed to nicotine(opens a new tab) sire male pups with livers that are good at disarming not just nicotine but cocaine and other toxins as well.
So bad habits can be good for offspring.
> “We just don’t have really any understanding of how RNAs can do this, and that’s the hand-wavy part,”
It seems to me to all be the handwavy part. I'm happy to wait until the research is considerably further advanced, past the clickbait stage.
I'm deeply skeptical of CEOs being "built different" like some people are arguing here. If Elon can be CEO of three companies and the founder of a couple more while also finding time to tweet 50+ times a day, have a failed and embarrassing stint in trying to optimize the federal government, and get K-holed at parties then the demands of the job can't be that rigorous.
If anything, I would argue that the strategic decisions actually can be automated/performed via broader consensus. With that handled, all that's left is the cartel that CEOs have invented to justify their exhorbant pay packages.
I love posts that peel back the abstraction layer of "images." It really highlights that modern photography is just signal processing with better marketing.
A fun tangent on the "green cast" mentioned in the post: the reason the Bayer pattern is RGGB (50% green) isn't just about color balance, but spatial resolution. The human eye is most sensitive to green light, so that channel effectively carries the majority of the luminance (brightness/detail) data.
In many advanced demosaicing algorithms, the pipeline actually reconstructs the green channel first to get a high-resolution luminance map, and then interpolates the red/blue signals—which act more like "color difference" layers—on top of it. We can get away with this because the human visual system is much more forgiving of low-resolution color data than it is of low-resolution brightness data. It’s the same psycho-visual principle that justifies 4:2:0 chroma subsampling in video compression.
Also, for anyone interested in how deep the rabbit hole goes, looking at the source code for dcraw (or libraw) is a rite of passage. It’s impressive how many edge cases exist just to interpret the "raw" voltages from different sensor manufacturers.
And ~90% of google searches now gives you 10 videos as answers to any query rather than just the web pages that have been turned into videos because youtube makes them more money than regular ads. Assholes.
CSS rules for printing is one of my favorite features of the web. You get a powerful typesetter directly in your browser. For those wondering how it's done, I wrote about it [0] recently for my friends who frequently asked how I generated PDFs for my blogs.
That is no longer true! You can do it in CSS with a combination of `@starting-style` and `transition-behavior: allow-discrete`. [1]
Another gotcha you'll run into is animating the height. A couple other new features (`interpolate-size: allow-keywords` and `::details-content`) will let you get around that. [2]
I had the 2019 Macbook Pro i9, so I think a function to determine thermal throttling could be written very simply:
function isThermalThrottling() {
return true;
}
Seriously, I loved that computer for the most part but I was a little annoyed that I paid a lot of money for the i9 CPU just to get worse performance than the i7.
Initially I kept my ToDo in a text file and I'd just delete things when I did them. Nice clean list of what's remaining, but after a few weeks I felt AWFUL, the list grew faster than it shrank, and it felt like I never made headway.
Now I don't delete things. I put a little + at the start of the line for anything I did, a - for anything I decided not to do, and a / for anything I did partially but needs to be revisited. I write a new list each day, carrying-forward items that I feel are worth revisiting.
And what's huge is that I can scroll down and see previous lists, years worth, and read all the stuff I did. It's enormous compared to the remaining todos, and apparently that's psychologically important.
Any license that discriminates based on use case would not qualify as open source under the Open Source Initiative definition, nor as free software under the FSF definition. You also shouldn't expect for your project/code to be reused by or incorporated into any free or open-source projects, since your license would be incompatible.
You can release software under whatever license you want, though whether any restriction would be legally enforceable is another matter.
The people in this thread coming to the defense of their CEOs sound like Tom Smykowski in Office Space desperately trying to save his job:
“I already told you: I deal with the god damn customers so the engineers don't have to. I have people skills; I am good at dealing with people.”
I just hope that my current Mac keeps being usable long enough that Liquid Glass has been fixed or replaced entirely by the time I'm forced to upgrade to whatever's shipping on my next computer.
Yeah it's a huge mistake IMO. I see it fucking up titles so frequently, and it flies in the face of the "do not editorialise titles" rule:
[...] please use the original title, unless it is misleading or linkbait; don't editorialize.
It is much worse, I think, to regularly drastically change the meaning of a title automatically until a moderator happens to notice to change it back, than to allow the occasional somewhat exaggerated original post title.
As it stands, the HN title suggests that Raymond thinks the C++ 'try' keyword is a poor imitation of some other language's 'try'. In reality, the post is about a way to mimic Java's 'finally' in C++, which the original title clearly (if humorously) encapsulates. Raymond's words have been misrepresented here for over 4 hours at this point. I do not understand how this is an acceptable trade-off.
But does applying the same transfer function to each pixel (of a given colour anyway) count as "processing"?
What bothers me as an old-school photographer is this. When you really pushed it with film (e.g. overprocess 400ISO B&W film to 1600 ISO and even then maybe underexpose at the enlargement step) you got nasty grain. But that was uniform "noise" all over the picture. Nowadays, noise reduction is impressive, but at the cost of sometimes changing the picture. For example, the IP cameras I have, sometimes when I come home on the bike, part of the wheel is missing, having been deleted by the algorithm as it struggled with the "grainy" asphalt driveway underneath.
Smartphone and dedicated digital still cameras aren't as drastic, but when zoomed in, or in low light, faces have a "painted" kind of look. I'd prefer honest noise, or better yet an adjustable denoising algorithm from "none" (grainy but honest) to what is now the default.
You - and many other commentors in this thread - misunderstand the legal theory under which AI companies operate. In their view, training their models is allowed under fair use, which means it does not trigger copyright-based licenses at all. You cannot dissuade them with a license.
People seem to forget a healthcare system is an important part of a nations security apparatus. In a time of war, casualty numbers and information is very valuable, and so allowing access to this data to be controlled by a company (palantir) funded by a foreign nations security services (funding by In-Q-Tel, the CIA's VC fund) is short sighted.
Even if you think Palantir is a wonderful company, this should concern you for the reasons above.
> With that handled, all that's left is the cartel that CEOs have invented to justify their exhorbant pay packages.
CEO compensation is determined by board committees mostly made up of other CxOs. They write letters to each other's shareholders about how valuable CEOs are to build up the edifice.
I wish my compensation were determined by fellow engineers who "truly know my worth". I'd pay it forward if I were on a committee determining colleague's pay packets.
I grew up in "Factory 404," a secret nuclear industrial city in the Gobi Desert that officially didn't exist on public maps. This is a memoir about my childhood there.
It was a surreal place: we had elite scientists living next to laborers, a zoo in the middle of the desert, and distinct "communist" welfare, all hidden behind a classified code.
This is Part 1 of the story. I'm happy to answer any questions about life in a Chinese nuclear base!