On the contrary, you can solve the tree problem with money. There are nurseries that sell mature trees -- most people though will not choose to spend $20k on a tree.

This is nitpicking his point.

But anyhow, you can buy large-ish burlapped trees but they aren’t as healthy, often die, and nothing close to a 100+ yr old estate oak tree or a decades old rose garden. You just can’t make it faster, transplanting plants that old will kill them.

You're moving the goalposts on his poor analogy :)

Most of the trees do just fine, and these nurseries will typically provide a warranty.

Besides nitpicking, even your original point isn't even true. You cannot transplant a 100 year old tree (which has not been constrained in size dramatically) and expect it to survive for any reasonable length of time.

You won't find a 50 year old American Chestnut in a nursery, lol.

And forget about 20k. If you find someone willing to sell their tree you're looking at at least 10x that for the logistics of moving a 20 ton root system.

You won't find a 50 year old American Chestnut anywhere lol, they were wiped out almost entirely.

You'll find it if you look hard enough. Whether the owner will let you dig up their entire yard is another matter.

It's a strategy that's only really available to the ultra wealthy, because the banks are willing to give them a bespoke loan with a much lower interest rate that's payable after they die. There's also a complex trust setup to pass the asset to their heirs.

These laws are the way they are so that if a kid has their parents die they aren't facing an immediate giant tax bill on cap gains. It applies to basically anyone inheriting even a normal house. The difference in cost basis could be 90% of the value.

You only pay cap gains if you realize gains, so you would only face a huge tax bill if you had a pile of cash dumped on you. E.g if you inherit a $1M house and sell it, and the IRS thinks you own 20% taxes on $900,000 of gains, then you have $1M of cash on hand to pay $180K in taxes.

(Also, if you live in the house for 2 years and then sell it, you can exclude $250K-$500K in gains, but that has nothing to do with inheritance).

It would depend... elsewhere on thread, someone says Canada treats death as disposition, and capital gains tax is due for a transfer on death.

Family farms are the sympathetic example of choice. Let's say your parent's family farm, that they started from nothing in the 1950s is now worth $20M. If you have to sell it to pay the taxes, because the estate doesn't have $4M to pay capital gains tax, plus $2M for estate taxes, then another family farm goes corporate.

Maybe you can inherit the capital property at the original owner's basis... then you'd only owe the cap gains tax if you sold it, and you'd have money to pay it because you sold it. That could work... although one nice thing about the step-up in basis on death is that nobody has to dig through to find the old records to establish basis when there's a clearly established death instead.

Its not like there can't be exceptions or carveouts. Its disastrous to treat that as representative of every dynastic transfer of accumulated wealth

Another tangent that I didn't see in the thread is that the Supreme Court just confirmed a ruling that LLM created art isn't copyrightable since the author must be human for copyright to apply.

If the new code was generated entirely by an LLM, can it be licensed at all? Or is it automatically in the public domain?

The US supreme court declined to hear a challenge to the claim that if you explicitly disclaim any human input to make a point then the art isn't copyrightable in the US. The copyrightability of "actually I had some design input" is still up in the air in the US, and copyrightability in general is still up in the air in probably the entire rest of the world as well as every court in the US outside of the DC circuit (because the supreme court declining to hear a case does not constitute an endorsement of the lower courts ruling or create precedent).

There's absolutely nothing stopping you granting a license to public domain work... granting a license is just waiving rights that the author might have to sue for copyright infringement under certain circumstances...

Personally I'd be unwilling to use this work without the license, because I would not be confident that it was public domain.

It would be in the public domain. Wouldn't really matter all that much if the end goal was to get it included in the Python standard library, but the whole "Copyright (c) 2024 Dan Blanchard" in the license file would just be BS.

The big question is whether or not is it a derivative work of an LGPL project. If it is, then it's just an outright copyright violation.

I'm working on a language learning framework based on the ideas of comprehensible input and spaced repetition learning.

The idea is you take a book you want to read, and it gets translated but also rewritten to match your current learning level. And as you read/listen it introduces new words to learn, reinforced by spaced repetition.

We're taking a trip to France this summer and I'm hoping to have something usable for at least a couple months before we go.

Currently working on the mechanics of extracting content from ebooks.

That sounds really interesting. I have a similar project, albiet pretty small. I want to generate comprehsnible input stories for the user say with 98% known words and 2% unknown words. Instead of rewriting stories though, I thought of having compiled list of books with say a book's top 1000 common but unique words, then you can add it to your desk and have those be generated in stories. That way once you complete the deck, it will be a lot easier to read your target book. I was looking into using numPy for that, not sure if you are using Python but it might be worth looking into.

Same in Oregon. Snowpack way below normal.

Canned beans are already cooked, so add them at the end to heat through. Or, start from dried beans, but it takes experimentation to get them to the desired texture.

Starting with red beans from scratch is on my list. I was hoping to get 80% of the taste with 20% of the effort -- seems like a simple enough dish, after all -- but last night I was watching a video of a guy making his own coconut oil (not just milk) from fresh coconuts, and it's clear I'm going off the deep end.

If you have GitHub copilot you can create github issues and assign them to copilot. All you need is a browser.

A lot of backwards looping is a remnant of efficient loops in programming days of yore - you compare your iterator to 0 each time, which is slightly more efficient than comparing to another variable.

We've been using Dato for 5 years or so - a bit of a weird use case probably, we're driving configuration of our internal EHR with it. But it is very nice for creating a structured set of data models and then you've got a nice UI to input the data and a nice API for grabbing the data, all of which the engineering team didn't need to build.

It's been rock solid for us.

As an actual customer, I have the opposite reaction. They are doing well and that gives me peace of mind.

Also a customer here, DatoCMS is fantastic product. We run hundreds of sites on their platform. Their team also works with you on pricing as you scale.

Not in my experience at all. Very solid product but incredibly frustrating trying to negotiate / get a bit of wiggle room in regards to pricing.

My plan auto-renewed for 2026 but it's become a priority to move everything off of Dato to another CMS for 2027.