As long as the Obj-C and Swift are in separate source or binary targets, SPM supports them being in the same package.
There was a Swift Evolution proposal at one point to go all the way and bring in support for mixed Obj-C and Swift targets [1] but it was returned for revision. It talks about the multiple target workarounds:
> Distribute binary frameworks via binary targets. Drawbacks include that the package will be less portable as it can only support platforms that the binaries support, binary dependencies are only available on Apple platforms, customers cannot view or easily debug the source in their project workspace, and tooling is required to generate the binaries for release.
> Separate a target’s implementation into sub-targets based on language type, adding dependencies where necessary. For example, a target Foo may have Swift-only sources that can call into an underlying target FooObjc that contains Clang-only sources. Drawbacks include needing to depend on the public API surfaces between the targets, increasing the complexity of the package’s manifest and organization for both maintainers and clients, and preventing package developers from incrementally migrating internal implementation from one language to another (e.g. Objective-C to Swift) since there is still a separation across targets based on language.
The upshot is that SPM has a better interoperability story with Swift and C++ [2] and maybe that can serve as a foundation for getting to the same level of interop for Obj-C.
TIL autism has been linked to environmental factors like metabolic syndrome during the first trimester of pregnancy, air pollution, and pesticide exposure. Some of these frequently co-occur with specific gene mutations. [1][2] There's a good argument that everyone has more exposure to everything on that list nowadays. Increased diagnoses would then make a lot of sense.
Teasing out the specifics of how much each of these contribute and separating that out from possible confounders like greater screening and others does seem like a tough study to design.
Exempt or lighten planning requirements for affordable housing construction. California is going in this direction now.
There are other levers like subsidized financing for developers building homes targeting a certain price range as well as favorable tax treatment of those profits.
A lot of these have would probably have some bipartisan support.
Is there a plausible experiment that can falsify dark matter? The study here used observational data and it didn't do that. (Deducing that non-existence of dark matter is plausible given what else was observed isn't the same thing.)
> “There are several papers that question the existence of dark matter, but mine is the first one, to my knowledge, that eliminates its cosmological existence while being consistent with key cosmological observations that we have had time to confirm,” Gupta confidently concludes.
> In the United Kingdom, he was called "Slater the Traitor" and "Sam the Slate" because he brought British textile technology to the United States, modifying it for American use. He memorized the textile factory machinery designs as an apprentice to a pioneer in the British industry before migrating to the U.S. at the age of 21.
> I confirm that oncology knowledge has grown dramatically. The total length of NCCN Guidelines, a “complete library” of cancer guidelines (NCCN, 2023b), has grown from 1,129 pages in 2002 to 5,825 pages in 2020. This growth in guideline length appears closely tied to growth in the scientific literature about how to manage cancer. This growth in guideline length also occurs in a period with large increases in the number of available therapies: the total number of approved cancer drugs rose from 90 in 2002 to 243 in 2020.
> Would open address data create privacy risks?
No. Unlike opening up more sensitive datasets such as personal location, releasing address data - a list of the physical places recognised by the government - carries few new legal or ethical risks. Many other countries are doing this, including those with strong privacy regimes. Open address data could only create new risks if it were linked and used with other datasets, and these risks should be managed in that context. The harms created by the lack of access to address data are more pressing.
> Although bisphenol A (BPA) has since been replaced by other bisphenols such as bisphenol S in BPA-free plastics, all bisphenols are endocrine-disrupting chemicals that can alter steroid signaling and metabolism.
There is some awareness of BPAs role in affecting the endocrine system. As the paper mentions merely being BPA-free doesn't mean one is out of the woods. All bisphenols are to some extent as disruptive as BPA is. Hadn't known that.
That said, Medicare and other entitlements is where my mind went too as I was reading. Negotiating drug prices is a good step in this direction by the current administration.
> With hawthorns suddenly scarce on the landscape, though, parsing out which species are real is next to impossible. “That’s the root of the problem,” Lance said. “They’re gone.”
Would population-scale (of those that can still be found) genetic sequencing help point the way to an answer? It's relatively cheap now, compared to before, and odds are will be more so.
There was a Swift Evolution proposal at one point to go all the way and bring in support for mixed Obj-C and Swift targets [1] but it was returned for revision. It talks about the multiple target workarounds:
> Distribute binary frameworks via binary targets. Drawbacks include that the package will be less portable as it can only support platforms that the binaries support, binary dependencies are only available on Apple platforms, customers cannot view or easily debug the source in their project workspace, and tooling is required to generate the binaries for release.
> Separate a target’s implementation into sub-targets based on language type, adding dependencies where necessary. For example, a target Foo may have Swift-only sources that can call into an underlying target FooObjc that contains Clang-only sources. Drawbacks include needing to depend on the public API surfaces between the targets, increasing the complexity of the package’s manifest and organization for both maintainers and clients, and preventing package developers from incrementally migrating internal implementation from one language to another (e.g. Objective-C to Swift) since there is still a separation across targets based on language.
The upshot is that SPM has a better interoperability story with Swift and C++ [2] and maybe that can serve as a foundation for getting to the same level of interop for Obj-C.
[1]: https://github.com/swiftlang/swift-evolution/blob/main/propo...
[2]: https://www.swift.org/documentation/cxx-interop/