Feed aggregator

Tour Rio de Janeiro’s cultural archives on Google Arts & CultureTour Rio de Janeiro’s cultural archives on Google Arts & CultureMayor of Rio de Janeiro

GoogleBlog - Mon, 11/18/2024 - 09:00
A new collection from Google Arts & Culture and the General Archive of Rio de Janeiro City showcases the history of the city.A new collection from Google Arts & Culture and the General Archive of Rio de Janeiro City showcases the history of the city.
Categories: Technology

AI Investments Are Booming, but Venture-Firm Profits Are at a Historic Low

Slashdot.org - Mon, 11/18/2024 - 09:00
Silicon Valley's venture-capital firms are having an easy time finding promising startups to back. The hard part is cashing out. From a report: Last year, U.S. venture firms returned $26 billion worth of shares back to their investors, the lowest amount since 2011, according to the data provider PitchBook. Startup investors say 2024 has continued the trend, with high levels of investment and few acquisition deals or initial public offerings. "We've raised a lot of money, and we've given very little back," Thomas Laffont, co-founder of investment firm Coatue Management, said at a recent conference. "We are bleeding cash as an industry." Last year, U.S. venture firms invested $60 billion more than they collected, the highest such deficit in PitchBook's 26 years of data. As a result, the investors that back VC firms, such as university endowments and pension funds, aren't seeing the type of profits the industry has long delivered. The decline is particularly notable because the past three years have been the highest three on record for total VC firm investments since 1998 -- as far as back as the PitchBook data goes. Much of that money has recently gone to artificial-intelligence startups -- a white-hot space in which valuations are rising fast and companies quickly burn through cash to develop new technology.

Read more of this story at Slashdot.

The Rust Foundation Wants to Improve Rust and C++ Interoperability

Slashdot.org - Mon, 11/18/2024 - 07:34
The goal? "Make C++ and Rust interoperability easily accessible and approachable to the widest possible audience." And the Rust Foundation's "Interop Initiative" is specifically focused on the goal of interoperability "within the same executable," through either inline embedding that allows "integrated compilation", or foreign function interfaces. To that end, a statement addressing "the challenges and opportunities in C++ and Rust interoperability" was announced this week by the Rust Foundation. Pointing out that the "Interop Initiative" was launched in February 2024 with a $1M contribution from Google, it now "proposes a collaborative, problem-space approach engaging key stakeholders from both language communities. "Rather than prescribing specific solutions, this problem statement serves as a foundation for community input and participation in shaping both the strategic direction and tactical implementation of improved C++/Rust interoperability." Their official problem statement outlines three "key strategic approaches." - Improve existing tools and address tactical issues to reduce interoperability friction and risk in the short term. - Build consensus around long-term goals requiring changes to Rust itself and develop the tactical approaches to begin pursuing them. - Engage with the C++ community and committee to improve the quality of interoperation for both languages to help realize the mutual goals of safety and performance. And it argues that interoperability "is essential to pursuing safety and performance which is maintainable and scalable." A significant amount of development has gone into libraries to facilitate interoperability with both C and C++, but from the language and compiler level, the situation remains largely unchanged from the early days of Rust. As the desire to integrate Rust into more C++ codebases increases, the value of making C++/Rust interoperability safer, easier, and more efficient is rapidly increasing. While each language takes a different overall approach, both view safety as an essential concern in modern systems. Both Rust and C++ have language- and standard-library-level facilities to improve safety in seemingly compatible ways, but significant benefits are lost when transiting the foreign function interfaces (FFI) boundary using the C ABI... The consequence of this increased cost to interoperate means both C++ and Rust codebases are less able to access valuable code that already exists in the other language, and the ability to transition system components from one language to another is reduced outside of existing C-like interface boundaries. Ultimately, this reduction in freedom leads to worse outcomes for all users since technologists are less free to choose the most effective solutions.

Read more of this story at Slashdot.

Comment