cma256
National average construction cost per square foot is $160. $160 * 2000 square feet is $320,000 sans the land which we can assume is 25% the cost of the home constructed on it. So we've magically hit the $400k number.
The only way home prices 'decline' is with population decline, coercion, a recession, or significant regulatory, cultural, and financial shifts.
I think an under-appreciated aspect of all this is the complete schadenfreude from everyone. The story goes tariffs only hurt yourself but then we see retaliatory tariffs in response. "Oh yeah I'm going to cut off my leg to show you whose boss!" Very funny.
And then you have people predisposed to higher-taxes who are contorting themselves over the economic cost of this tax while supporting significantly more economically destructive tax policies. Very funny.
And, of course, the opposite. Republicans in my state are campaigning on lowering taxes and inflation while also defending tariffs! Very funny.
Changing divorce laws to be less equitable, as far as I know, has never been a major platform of either party in the South. I'm not aware of any politician that advocates for it. I'm sure it exists but it must be an incredibly marginal view.
The overemphasis by critics on punctuation and "this not that" is tiring. I don't really know how to describe LLM writing but it has the same qualities as flat soda. Some authors you feel as though you fall through their work with little effort; unable to stop until gravity slams you into their conclusion. LLM writing can feel like an uphill hike to a sewage treatment plant. That is, its easy to convince yourself to stop at any time. There's a positive quality to that. I hope AI labs don't find a way to remove it.
I'm familiar with large-scale, commercial, client-server use cases for columnar analytics and graph traversal but what is the use case for an embedded server like this?
> The U.S. Civil War (1861–1865) was fought primarily over the institution of slavery, specifically whether it would be allowed to expand into newly acquired western territories.
> While you might hear people point to "states' rights" or economic differences as the causes, these issues were inextricably linked to slavery. The southern states wanted the "right" to maintain and expand slavery, while the northern states increasingly opposed its expansion.
Harvard University Professor of Economics everyone. When discussing new modes of transport the _hyperloop_ is the exemplar. A technology that does not work, can not work, and will never work.
And, of course, no mention of e-bikes which are cheap, proven, and have seen large adoption in my neighborhood at the least. But of course that might have undermined his point.
I would be interested to see a scientific discussion on what consciousness is biologically and if AI can fit that definition. But it would require someone with more credentials than a _media entrepreneur_ to pull off.
> Function signatures don’t change based on how they’re scheduled, and async/await become library functions rather than language keywords.
The functions have the same calling conventions regardless of IO implementation. Functions return data and not promises, callbacks, or futures. Dependency injection is not function coloring.
But there are categories of application where that is not acceptable. The presentation is a tightly controlled aspect of the application's functionality. If you're designing an application with leptos or sycamore my suspicion is you would fall into the latter category rather than the former.
For example, a "row" is not just a "<div>" tag. Its a div which horizontally fills its container. Centering contents with a "center" style attribute abstracts flex-box, browser compatibility, version compatibility, and the cascading behavior of CSS.
You move the incidental complexity of the web platform into the compiler which will always do the right thing. And in exchange you get the option to compile to a native or mobile app for "free".
In other words, elm-ui but for these WASM Rust apps. Building a mobile app, a desktop app, and a web app, in my mind, should be accomplish-able given the right primitives (without requiring a JavaScript runtime be bundled). Rust's multi-crate workspaces make it a really great candidate for solving these cross-platform problems. IMO of course.
1. https://thearp.org/blog/apportionment/2030-apportionment-for...
Federal power is shifting south. If you like the politics of New York and California that's a long-term problem that needs to be resolved.
Agree with everything else you said except this. In my opinion, this assumes code becomes more like a consumable as code-production costs reduce. But I don't think that's the case. Incorrect, but not visibly incorrect, code will sit in place for years.
In the US, you can buy a five-speed 4runner which is about the simplest engine available on the market. Has all the benefits enumerated above and its trivially repairable by DIYers. However, even the 4runner has annoying garbage which can fail.
Compare the newest 70 series Land Crusier in Japan to the US Land Cruiser (Prado). Difference is a v8 with no electronics and a 4 cylinder hybrid filled with electronics and a rats nest of tubes running across the top of the engine. Try working on that... Of course its get +20mpg compared to the Japanese version. I'm pretty sure the 70 series is 4 wheel drive always whereas the prado runs in 2 wheel drive but has a 4 wheel switch (more complexity -- better gas mileage).
Anyway, intangibles such as availability of parts and lower pricing makes scavenging more economical and increases life span.
Also, stability of the platform means there's lots of expertise that has developed over the past +30 years. Same design, same repairs, same parts. Makes things easy.