Thanks for the detailed reply. This still seems ridiculous to me though:
> [..] generally, when a mechanics lien is filed after the sale of the property, a mechanics lien may still be able to attach to the project property as long as the other requirements for the lien claim were still followed.
Just why? The whole point of a lien is to be able to sell the house to raise money to pay the debt. The house is sold so now he can pay the debt. If he had so many debts that he's still underwater then the lien wouldn't have made a difference anyway, as the older debts would have to be paid first.
The way I understand this, the homeowner entered a contract with a mechanic allowing the mechanic to put a lien on the property to secure the debt for the mechanic's work. Then he sold the property before they did so. It seems to me there are now a couple reasonable courses of action:
Force the homeowner to pay the debt as it is no longer secured, or they could offer up something else as collateral for the debt.
It makes no sense to make the new homeowners pay for the repairs for some stranger's car. That's just wrong. The only way it could possibly make sense is if they explicitly agreed to take over the debt as part of the sale. Clearly this isn't how it works in the real world, I'm just baffled at how stupid the real world is. This seems so easy to fix. The only explanation I can come up with is the insurance companies lobby to keep it this way because they make a fortune selling title insurance that doesn't even need to exist.
Yeah I don't have a problem with liens, I have a problem with unregistered liens. There needs to be a system for registering and searching liens, it needs to be publicly accessible and the lien needs to be registered before it's valid. In order to register a lien on a car you need the owner's signature, that can't work when the owner has changed. Mechanic needs to get the contract signed then report the new lien to wherever it should be reported, and once that's all in order they can start working on the vehicle.
If they try to register their lien once the owner of the vehicle has changed, it can not be accepted. You can't secure debt with a vehicle you no longer own. The lender needs to make sure the person owns the car and register the debt while they still own the car. And if they sell the car then they have money to pay the debt, and since they no longer own the car then their debt is no longer secured so that should trigger a requirement to pay the debt per the loan contract. Debt should be owned by people not objects.
The whole concept of debt that's attached to objects is silly. It can make sense in certain situations like a housing association that's taking up a shared loan and paying it down as part of shared monthly expenses, but for a car repair or similar it makes no sense. The person who takes the debt is responsible for the debt. If they sell the car then they pay the debt with the money from the sale, if the sale doesn't cover the debt then they still owe the rest.
It does not need to be any more complicated than this. In order for anyone to take over responsibility for debt in relation to a purchase, there needs to be explicit written and signed consent. So - I can buy a house including some debt if I know and agree to it, but I can't unwittingly buy a landmine. If the owner fails to resolve their debts when they sell that should be their problem not the buyer's. It's up to the bank to collect their debts from the person they have a contract with.
It's crazy how this isn't simple. Surely all they have to do is to tally up the debts secured by the apartment, then sell the apartment and use the money to pay as much of the debts as possible. Any remaining debt is the lender's loss, that's the risk they take when giving out loans.
If any debt does need to be tied to the apartment rather than the person, then it simply needs to be registered in a publicly (easily) accessible way. If someone fails to register their debt in a timely manner then it should be forfeit. It should be registered at the time it takes effect. Lender should be responsible for making sure the registration is complete before giving out the debt, if someone takes out a loan then sells it before the debt has been registered that's the lender's problem. They can't retroactively add a lien to my property because the previous owner took a loan when it was their property. That's not reasonable. If the lien is not registered then it doesn't exist, it should be that simple.
> In practice, maybe some roofer/plumber/landscaper forgot to do that and now you have a problem you didn't know you had
Seems to me like this should be the contractor's problem. If they did the job 2 weeks ago fine, but if they come along 6+ months later after the house is sold demanding payment from the new owner that seems ridiculous to me. Surely if these Liens are supposed to be public there needs to be a requirement that they are registered as soon as possible.
Otherwise it seems to me like this is a ripe opportunity for scams. Buy house, have contractors refurbish it, sell it for a much higher value, then the contractors register their debts and now the new buyers or their insurance is on the hook for the refurbishment.
To me it looks like they've been pretty plateaued for a good while already? Sure they do marginally better on benchmarks or whatever, but to me as a user there's really not much difference between chatgpt today and chatgpt a couple years ago. Main difference is just added capabilities like web search, image recognition etc.
For coding you still need to be in control if you want a good result.
I think simplicity is good engineering. Bending over backwards to support pointless usecases isn't good engineering. Almost nobody would use this and the ones who would don't need to. Why put in the effort?
A 15x improvement over mammoth (spot on by the way) is still many times more capture plants than we have power plants. And there's limits to the efficiency of these facilities in terms of how much air they can consume per day. Not to mention the carbon costs of building and operating them.
Maybe I'm wrong, I'm certainly not an expert. It just seems like a hopeless case to me. Even if they make one significantly more effective than this Stratos you mentioned, we're still talking about tens of thousands of them to have a real impact.
Not really. In C# I use a parsing library for which I just write a class and then the library automatically serializes the JSON into an instance of that class.
I can do the same thing with XML. Of course it doesn't necessarily go that smoothly with all xml, but as long as the xml is fairly simple like a JSON document would be it's totally fine. It's only when you start to use all the features of xml that don't fit neatly into a class model that it starts to get annoying. But if JSON serves your needs then simple xml does as well. I wouldn't use it because JSON works just fine but it's not as bad as people make it seem, unless people make it really bad.
Your question betrays the fact that you simply don't understand the scale of what's happening.
Imagine a line chart. It displays average global temperature over millions of years. It goes up a little, it goes down a little, it fluctuates over time. That's the natural change. It occurs over thousands and millions of years.
Looking at the last few decades on that chart, you'll see a wall. It's going almost straight up compared to the rest that just meanders lazily. You can see a few other similar peaks on the chart many millions of years in the past, they generally correspond with things like apocalyptic meteorite impacts etc. And even then the change occurs much more slowly than what we're seeing now.
It's honestly insane to me that we're watching the world end and half of people are like "but are we sure this isn't normal?"
Yes we're sure. We double checked. Just look at any "global average temperature" chart and try to predict where it's going. This isn't the stock market it won't just randomly start doing something else. The movement we're seeing is directly correlated to our ghg emissions, and there's a lag - the effects of current emissions won't be fully seen until up to two decades from now. So even if we stopped right now it would continue warming for decades.
Warming also releases more GHGs. As poles and permafrost thaws, enormous amounts of methane are released that was previously trapped, further accelerating warming and acting as a positive feedback loop on top of our steadily rising emissions.
In short were fucked, we know it, and anyone who doesn't know is not paying attention.
If you actually look at the numbers of carbon capture its entirely obvious that it can't work. It's honestly strange to me that they even waste money on it, personally I think it's a distraction - "look we're working on a fix, now let us just pump up the rest of this oil in the mean time and we'll definitely fix it later".
In order to just offset our current emissions, we would need around a million carbon capture facilities equivalent to the largest one we currently have. For comparison, the number of power plants in the entire world is a few tens of thousands. So we'd need maybe like 50 times as many capture plants as we currently have power plants.
Like it's not even in the neighbourhood of realistic, it's just completely infeasible and I am sure engineers know that. You basically need to suck the whole atmosphere through facilities, and there's a lot of atmosphere.
Maybe it's different in other languages, but if I ever see hand-rolled serialization in a C# project I'm putting replacing it at the top of my to-do list. There is pretty much no reason to do that ever, serialization is a solved problem. It's flat out stupid to spend extra time hand-rolling a solution that most likely ends up buggy and requires even more work in the future etc. I also often see people waste hours or days writing custom serialization logic for a serialization library, when they could have just written a new class in the shape of the data and been done in 5 minutes.
I did work on such a project once. There was a CMS web app which needed to sync data from a third party api to rebuild some pages every night. To do this they had a client library that pulled the data twice daily and stored it in a db, then the CMS app pulled the data through the client library. The API used XML and significant parts of this library were a hand-rolled xml serializer. It worked so I didn't touch it, then it stopped working. Spent days trying to fix it but the more I studied it the more I realized it was entirely pointless. Spent about 1 day replacing the whole thing with a simple little function that just calls the api, deserializes the data using a library and builds the pages. Remove the pointless DB, remove the giant legacy quagmire integration library, this project probably took months to write and I replaced it in a day, making it orders of magnitude smaller and faster.
In the end my solution wasn't used because of office politics, apparently they'd paid a significant amount of money to use this pile of trash and replacing it that easily would make someone look bad or something. So I ended up fixing the pile of crap in the end, even though I had a replacement ready to go.
Probably because there is some mildly decent reason (or very good, I don't know) to avoid them and it really doesn't matter enough to worry about getting around it.
Why would you want emojis in your password? It's a piece of text not meant to be seen, emojis are meant to be seen. Just randomly generate some characters and get on with your life. I don't understand why you care about this at all, it's such a pointless thing to complain about.
I recently learned that you should add detergent for the pre-wash rinse as well. May dishwashers have a separate pocket next to the detergent pocket, often there isn't even a lid on it or the lid has openings so the detergent falls out as soon as you close the door. If they don't have the symbolic pocket you can just pour some extra detergent anywhere, like just spill some outside the main pocket or pour it into the bottom.
This allows the pre-wash cycle to get rid of most of the grease and stuff before the main cycle so the main cycle is more effective and the water is cleaner so the final rinse works better too.