Well, interest rates are high right now, but you’d be surprised at how little down payment you need for purchasing a house or a condo. If you’re a tech worker with a stable career making that kind of money, most underwriters will just give you the loan.
I think people commonly underestimate how accessible this stuff is
It’s easy to make a 40 year forecast spreadsheet for retirement, including housing costs, property, taxes, maintenance. Include vacation, budget, food, general cost of living.
So you oblige yourself to an enormous long-term loan at high-interest, burn PMI on it because you have too little equity, secured against an overpriced-for-quality home whose value may already be at peak or plataeu, fixing yourself to one location, while all signs warn that you may be laid off at any time and facing a long period of unemployment.
I knew a lot of people who did almost exactly that ~18 years ago. It didn't go well for them.
And then it turned out that staying flexible as a renter and setting aside cash set me up to buy after a correction instead of before. That part went very well for me.
Be careful with the assumption coded into your "forecast spreadsheet"
Well yes, there are tradeoffs. On the other hand, go ahead and burn 3k a month on rent.
There is no one size fits all solution but i’m surprised at how many people here are inadvertently revealing to me that they haven’t even tried evaluating.
For example, you saying there’s nothing “affordable” when the baseline assumption is an income of $250k? Can tell you haven’t looked at what’s in your price range. Alright, good luck I guess!
I mentioned Lifestyle creep before but what is with everyone’s fried brains?
A small condo in a nice neighborhood in Santa Clara is below $500k. Yes, that’s a lot, and you certainly can get more bang for your buck if you’re willing to do a little commuting.
Btw a $1m house is accessible if you make $250k yr, although to be honest, I would highly recommend against it
The question I originally responded to was "why would you rent and save for a house at the same time?"
I said "because you need to have a downpayment".
You reply "downpayments aren't that high".
Unless you're getting loans zero down, you literally still need to save to have your downpayment. While you're renting.
So where is my brain fried?
Even on a $500k condo, you're putting 10% down, you still need to have that saved up. Noticeably more, in fact, because I'm sure you'd agree "lemme sink every saved cent I have into my house downpayment" wouldn't be wise.
There's no point doing that given the Responses API has to be ad-free unlike ChatGPT Web API for applications to function correctly (no way baking ads into responses sent to third party services using your language model just as a natural language processor), and you have to keep the Web API tiers that's more expensive than the same amount of tokens of equivalent Responses API use also ad-free becuase otherwise the "wrong way of payment" paradox would arise.
The KVM just uses a devboard that's also sold separately and just happens to have a microphone, given how cheap the mics are having one extra SKU would probably just cost them more than savings.
Also I wouldn't really consider it "server room" product. Pretty much any new server has KVM, this is more "a hobbyist needing KVM for their home server"
I can't recall seeing any server that includes KVM-over-IP, but instead they have some shitty remote access controller (e.g. Dell iDRAC) that is buggy as hell and requires a subscription to even get working.
...you need a password to log in onto it to change it. That's hardly unique.
You could say "but they could make random one that is displayed on display!", but they also sell headless version with no display at all so that's not an option
I think what's most likely to happen here is that:
* a developer that knew how it worked used it in code where he *wanted* to get the first line
* someone just starting up copied it over and assumed that's the way to get the content of command into a variable
It's essentially complaining about using feature wrong on purpose, because the person that made mistake never learned the language.
my($var1, $var2...) is a way to multi-assign variables from an array.
and that makes perfect sense when you look at it. Perl have no multiple returns, but if you need a function that returns 2 variables it is very easy to make it work with:
my ($bandwidth, $latency) = speedtest($host)
Perl's feature for returning different type depending on caller is definitely a confusing part but
my @lines = `fortune`
returning lines makes perfect sense for the use case (you call external commands to parse its output, and if you do that you generally want it in lines, because then you can just do
foreach my $line (`fortune`) {}
and it "just works".
Now you might ask "why make such shortcuts?". Well, one of big mistakes when making Perl is that it was also aimed as replacement for sed/awk for the oneliners, so language is peppered with "clever short ways to do stuff", and it's a pleasure to use in quick ad-hoc oneliners for CLI.... but then people try to use same cleverness in the actual code and it ends up with the unreadable mess people know Perl for.
the fact you can do
my ($first_line, $second_line, ...) = `fortune`
is just the feature being.... consistent in its use "when you give it array, it will fill it with lines from the executed command"
you gave it array, and it just did what it does with arrays.
Perl made a mistake, the language was invested in depth of expression and that, in a programming language, just leads to a 1000 ways to write same thing where like... 2 of them are actually nice to read.
Pyton was ("was" was used here on purpose) the opposite, the whole "one way to do a thing" and insisting on more clean code even if more verbose.
You could write nice looking Perl code but you had to choose to do it, while Python pushed you in that direction from the start.
As much as I dislike using whitespace as flow control it also does make sure the code is always indented reasonably even if it is a newbie just starting in the language.
It didn't help that Perl, just like other languages after (PHP, JS, Python too), had a "curse of the newbie language", with many people starting with it (as at the time it was kinda only sensible choice for webpages before mod_php did a revolution in how most webpages are hosted), with no training and just winging it, which in language that puts no limits on what user can do and no guidance on what they should do... leads to that ugly one liners and line noise as a code scripts.
There’s a whole lot of words popularly excised (as you just did) from that line of the Zen to create a false polar opposite to Perl’s TMTOWTDI that was never actually part of Python’s philosophy.
The actual line from the Zen of Python is: “There should be one—and preferably only one—obvious way to do it.” (omissions in italics).
That is the story that Python tells about itself. Meanwhile, folks who don’t use it every day are constantly learning that it’s only true within a single version of Python, but that over the years there will be multiple, incompatible ways to do niche wild rare stuff like … iterating over a map.
Python has never actually followed the Zen of Python, which is one of my gripes with it. For example, "explicit is better than implicit" is a bad joke given how Python implicitly treats non-boolean types as booleans.
reply