I've looked at this a bunch of times, from a pure return perspective, yeah equities usually win. But there's enough benefits to homeownership outside of that lens that I think either side can make a pretty compelling argument (I say this as someone who rents). It also highly depends on which market we're talking about.
yes - I often think about what I would do if I "won the lottery" or similarly got a significant amount of cash. Even though I have a low mortgage rate (refied in the middle of COVID), I'd probably still pay off my house. I know it makes absolutely no rational economic sense, but not having a mortgage payment and knowing that I own my house would give me a piece of mind that as you say is hard to put a dollar amount on.
I know there are people out there that like maximize returns with leverage and all of that - and the math all makes sense! - but I'd prefer the simplicity of not dealing with it.
Timing is huge part of it .. the real estate market goes in long term cycles, and if you buy at a good time you may do well over 10+ year timeframe, but if you buy at the peak then it may take that long just to break even if you sell (just in terms of house price, forgetting taxes/etc, and real-estate fees - 5-10% of price !).
Then of course you have all the expenses of home ownership, starting with real estate taxes ($20K/yr by me), maintenance (incl. costly items such as roof replacement), etc.
Deliberately investing in real estate, where you can choose the city/market, type of dwelling, need for renovation, etc, may have a higher chance of being profitable, although even there obviously buying at bottom vs top of the market makes a big difference. For people just buying a house to live in, conventional wisdom is not to expect it to be financially preferable (all told) than renting, even if sometimes - depending on timing - it may turn out to be.
The article loses impact due to the way the author keeps self-conciously mentioning how the "PHP haters" are wrong instead of just explaining the possible usecase for PHP better.
I've never really used it but it would have been somewhat useful to know why anyone would choose this language for a greenfield project in 2025, given the choices available. The reasons given are pretty unconvincing to me.
I often wish it weren't the case as much. There's a massive cassum the size of the Grand Canyon between the majority of JS devs and good JS devs that understand the language, and have a good grasp of software craftsmanship. And that doesn't mean stuffing JS based projects with "Enterprise" patterns that don't make sense in the platform being used.
JS devs who started around or just after covid are everywhere. JS devs with 10+ years of experience are a small fraction of the market at this point. JS devs with any number of years of experience who also understand JS (or even just CS in general) well are a minute fraction of JS devs.
What do you mean by access? APIs to program against or fully open sourcing the rendering engine? Because you can mix SwiftUI with a few different rendering frameworks at varying abstraction levels that it itself renders to (AppKit, UIKit, Core Graphics, Metal etc.)
Basically I want an API available to build my own SwiftUI. Definitely not on the Core Graphics level :)
But good point, I actually think AppKit might be a good abstraction level. I'll play with it a bit and see if I can abstract it behind a good component model.
Because politicians have made it their mission to chip away at the NHS over decades. This doesn’t say anything about the efficacy of statutory healthcare.
But it’s quite relevant to the question of whether you can just assume that some country will foot the bill for your health care needs at old age, and therefore you don’t need to worry about health expenses if you retire early. Rising costs of health care systems are a serious problem in most developed countries. “Eh, I’ll just move to Europe in old age” is not really a comprehensive plan to ensure you get good healthcare far in the future.
It does. In every public-healthcare country, this happens. Because incentives are stacked against delivering to the patient and for increasing spendings. It’s the tragedy of the commons.
I wouldn't use the Netherlands as a great example either. The family doctor model is slowly disappearing, replaced by private clinics. It is relatively difficult to get appropriate treatment for anything, and there are long waiting queues even for intake appointments. It has only been getting worse in the past decade.
> Public healthcare isn't a free for all, its regulated, actively managed and budgeted.
Not what I mean. It’s racist. Public jobs are being reassigned in a racist way to help whoever the currently-elected leader wants to favoritize, and, as the NHS ad says: “This is us, now”, clearly demonstrating a no-whites ideal (NHS’s intentions, not mine).
Public health funnels money from people who paid to get coverage, to, on one part, those would be rejected in a normal system (non-insured people) because it’s easier to say yes when it’s diluted; to to, for the second part, people self-selected by the group of currently-employed people, ie in the UK it means that normal people are selected with all criteria but protected classes (the legal term, “protected classes”, I mean) have priority for those jobs.
You may pretend the NHS is not racist, but the NHS actions speak for themselves.
Yes and no, our app is considerably larger than 130k LoC. While we’ve migrated some modules there are some parts that do a lot of multithreaded work that we probably will never migrate because they’d need to essentially be rewritten and the tradeoff isn’t really worth it for us.
Its kind of a trap, we allow people in interviews to do the same and some of them waste so much time accepting wrong LLM completions and then changing them than if they'd just written the code themselves.
The launcher UI is AppKit while the extension APIs allow third-party developers to write them in TS and a React subset. They have a custom renderer for React that turns that into AppKit primatives. So similar in concept but custom and specific to their usecase.
reply