One problem of having old WWDC content available is that it is confusing for a developer searching for how to do something to be shown deprecated approaches. It's hard enough finding the right way to do something in Swift with all the old versions of the language around.
It’s hard enough finding a way of doing something. Apple doesn’t document anything. Instead they point you at WWDC videos which they take down after 5 years (or even less) that hold critical information needed to develop for their platform. If they want people to do things “the right way”, then they should document it properly instead of just pulling things arbitrarily or putting all their documentation in the form of videos.
Old WWDC content has a lot of value. They cover a lot of core technologies that Apple has no interest in covering and documenting again (because they deprecated and are removing old documentation instead of improving them...). The channel in question helped me a lot while trying to understand aspects of early-Cocoa.
The argument you've presented is more related to the way Apple handles the evolution of its software than about having old content laying around. Their current approach is far from good unfortunately. During OS X Lion days, Xcode documentation was so rich that even core concepts of the OS were covered.
Having a structured way to keep those informations readily available is very important to help us preserve software history. And Apple is not helping...
It’s a combination of surface tension and buoyancy; the resulting minimum energy surface can be designed to whatever freeform shape you want by controlling the liquid density and the geometry of the frame.
thickness of the membrane, but this will cause fresnel lenses if annular, and complexity if a continuous curve, and also introduce (spherical?) aberration of its own due to non-linear effects on light through a varying sized medium before hitting the "lens" part inside the membrane
this is me thinking in terms of "what things about an inflatable structure change how spherical it becomes, when inflated" and adding in "what does it do to optics"
not an optician, a physicist or an inflatable toy clown.
I'm fairly sure that the medium within the ring-shaped mold is homogenous once cured--I don't think it's a cured surface membrane with a liquid interior?
Presumably that's the purpose of the heat-curing process described in their paper, as UV won't be able to penetrate arbitrarily deep into the polymer.
They inject a liquid polymer solution into the water+glycerol solution, in the area they want it to be. 'Immiscible' means they won't mix, it'll just form a homogenous bubble/blob in the water. And they carefully adjust the density of the water+glycerol ahead of time to match the density of the polymer, so the blob of polymer neither floats nor sinks. Surface tension affects the shape of the blob caught in the ring mold, which is created ahead of time to produce the shape they want. Then they cure it, 'freezing' the liquid polymer as it solidifies. There's no liquid inside when it's done.
Wow I'd completely misunderstood what was being initially UV cured, I thought it was a "skin" of material to form the shape much as a balloons final shape is influenced by the thickness of the rubber and was inflated. Talk about the bad effects of skim reading!
Same here. Sometimes I wish the web was simpler and the history API was not a thing. Or barring that, that the browser would pop up a permissions prompt when a page attempted to access the history API.
The back button in Chromium type browsers should ignore history entries added before a page receives a user gesture [0]. That did not seem to happen here!
You can try it yourself by loading a YouTube video via pasting into the URL box and letting it autoplay a few videos. The back button should take you to the new tab page. If you click anywhere on the page then those autoplay entries will not be skipped by the back button.
Anyone know how to run this on Big Sur? I've built the project and it runs but there's no terminal window and the New menu item is dim. I looked at all the forks but most are very old. I guess I need a CP/M disk image?
