• 0 Posts
  • 59 Comments
Joined 3 years ago
cake
Cake day: August 14th, 2023

help-circle
  • To be clear, women’s work before World War II was more than just the dishes. If you look at the guidebooks published for housewives back then, you’ll see that they were expected to have quite a few skills that most households now generally outsourc to external businesses:

    • Feeding the family. This was more than just cooking. They were expected to process foods from a much less processed state (much more butchery of meats and cleaning and processing of vegetable products, dairy products, baked goods), and then preserve foods for out-of-season consumption (pickling, preserving in jams/jellies, home canning, drying, and in some cultures smoking). Much of this work is now done by the industrial food processing industry so that we can buy cans or jars or boxes of the stuff that’s already processed or partially processed. Even our fresh foods have been cleaned and sorted and trimmed to mainly just the edible parts.
    • Making and maintaining textiles. We see bits of this surviving into knitting and crocheting as hobbies, but back before the rise of cheap apparel it was important to be able to clean and repair clothes that we’d now just take to our local dry cleaner.
    • Maintaining the house itself. Home improvement is masculine coded today, but a lot of the stuff that qualifies as home maintenance was traditionally the work of a homemaker. Plus things like heating the house required active involvement of keeping fires burning and fuel on hand.
    • Making household consumables. Homemakers were making their own soap, their own candles, and all sorts of little tools.

    The economic shifts that come from women leaving the home for the paid workforce are all over, and some of them are pretty pronounced. But it’s important to remember that women worked hard before they ever got paid for it. Life was toil.



  • Makes me wonder about the wheel’s rotational inertia, too. In theory, a hubless wheel could be lower mass overall without the need for a center axle/hub and spokes connecting the outside to the center. But that’s all weight saved in the center of the wheel with lower effect on overall rotational inertia. Visually, the picture that makes the thumbnail in this post shows that the brake disc has to be further from the center of the wheel, which I imagine adds a lot more weight (more material necessary for the overall brake disc being a larger circle) and a lot more rotational inertia (further from the center).

    Maybe the whole design itself can save weight in certain places that make up for the weight added in other places. But I just have a ton of questions, and am overall pretty skeptical of the long term potential of this design.

    Looks cool, though, I guess.





  • No, LCOE is an aggregated sum of all the cash flows, with the proper discount rates applied based on when that cash flow happens, complete with the cost of borrowing (that is, interest) and the changes in prices (that is, inflation). The rates charged to the ratepayers (approved by state PUCs) are going to go up over time, with inflation, but the effect of that on the overall economics will also be blunted by the time value of money and the interest paid on the up-front costs in the meantime.

    When you have to pay up front for the construction of a power plant, you have to pay interest on those borrowed funds for the entire life cycle, so that steadily increasing prices over time is part of the overall cost modeling.


  • My problem with nuclear is both the high cost and, somewhat counterintuitively, the very long life cycles to spread that high cost. The economics only make sense if the plant runs for 75 years, which represents an opportunity cost of displacing whatever might be available in 25 or 50 years.

    A solar plant planned in 2025 might be online in 2027, and decommissioned in 2047, replaced with whatever technology/economics are available then. But a new nuclear reactor bakes in the costs for 80+ years, to be paid by ratepayers who haven’t been born yet.

    So if in 2050 a 2030-constructed nuclear plant is still imposing costs of $66/MWh on ratepayers, to finance the interest and construction costs from 25 years earlier, will that be competitive with the state of solar/wind/batteries/hydrothermal at that time? Given the past trend lines, it seems economically foolish to lock in today’s prices for the next 80 years.






  • But the other misleading part is they looked at 20 years which is close to the life cycle for solar/batteries and not even half the life of nuclear

    I think Lazard’s LCOE methodology looks at the entire life cycle of the power plant, specific to that power plant. So they amortize solar startup/decommissioning costs across the 20 year life cycle of solar, but when calculating LCOE for nuclear, they spread the costs across the 80 year life cycle of a nuclear plant.

    Nuclear is just really, really expensive. Even if plants required no operating costs, the up front costs are so high that it represents a significant portion of the overall operating costs for any given year.

    The Vogtle debacle in Georgia cost $35 billion to add 2 MW 2GW (edit to fix error) of capacity. They’re now projecting that over the entire 75 year lifespan the cost of the electricity will come out to be about $0.17 to $0.18 per kilowatt hour.



  • just spitting the information back out, without paying the copyright source

    The court made its ruling under the factual assumption that it isn’t possible for a user to retrieve copyrighted text from that LLM, and explained that if a copyright holder does develop evidence that it is possible to get entire significant chunks of their copyrighted text out of that LLM, then they’d be able to sue then under those facts and that evidence.

    It relies heavily on the analogy to Google Books, which scans in entire copyrighted books to build the database, but where users of the service simply cannot retrieve more than a few snippets from any given book. That way, Google cannot be said to be redistributing entire books to its users without the publisher’s permission.


  • What does an LLM application (or training processes associated with an LLM application) have to do with the concept of learning?

    No, you’re framing the issue incorrectly.

    The law concerns itself with copying. When humans learn, they inevitably copy things. They may memorize portions of copyrighted material, and then retrieve those memories in doing something new with them, or just by recreating it.

    If the argument is that the mere act of copying for training an LLM is illegal copying, then what would we say about the use of copyrighted text for teaching children? They will memorize portions of what they read. They will later write some of them down. And if there is a person who memorizes an entire poem (or song) and then writes it down for someone else, that’s actually a copyright violation. But if they memorize that poem or song and reuse it in creating something new and different, but with links and connections to that previous copyrighted work, then that kind of copying and processing is generally allowed.

    The judge here is analyzing what exact types of copying are permitted under the law, and for that, the copyright holders’ argument would sweep too broadly and prohibit all sorts of methods that humans use to learn.


  • specifically about the training itself.

    It’s two issues being ruled on.

    Yes, as you mention, the act of training an LLM was ruled to be fair use, assuming that the digital training data was legally obtained.

    The other part of the ruling, which I think is really, really important for everyone, not just AI/LLM companies or developers, is that it is legal to buy printed books and digitize them into a central library with indexed metadata. Anthropic has to go to trial on the pirated books they just downloaded from the internet, but has fully won the portion of the case about the physical books they bought and digitized.


  • No. The court made its ruling with the explicit understanding that the software was configured not to recite more than a few snippets from any copyrighted work, and would never produce an entire copyrighted work (or even a significant portion of a copyrighted work) in its output.

    And the judge specifically reserved that question, saying if the authors could develop evidence that it was possible for a user to retrieve significant copyrighted material out of the LLM, they’d have a different case and would be able to sue under those facts.


  • The law says this is ok now, right?

    No.

    The judge accepted the fact that Anthropic prevents users from obtaining the underlying copyrighted text through interaction with its LLM, and that there are safeguards in the software that prevent a user from being able to get an entire copyrighted work out of that LLM. It discusses the Google Books arrangement, where the books are scanned in the entirety, but where a user searching in Google Books can’t actually retrieve more than a few snippets from any given book.

    Anthropic get to keep the copy of the entire book. It doesn’t get to transmit the contents of that book to someone else, even through the LLM service.

    The judge also explicitly stated that if the authors can put together evidence that it is possible for a user to retrieve their entire copyrighted work out of the LLM, they’d have a different case and could sue over it at that time.


  • The court’s ruling explicitly depended on the fact that Anthropic does not allow users to retrieve significant chunks of copyrighted text. It used the entire copyrighted work to train the weights of the LLMs, but is configured not to actually copy those works out to the public user. The ruling says that if the copyright holders later develop evidence that it is possible to retrieve entire copyrighted works, or significant portions of a work, then they will have the right sue over those facts.

    But the facts before the court were that Anthropic’s LLMs have safeguards against distributing copies of identifiable copyrighted works to its users.