1,278 karma · joined October 1, 2021
> What does [dead] mean?
> The post was killed by software, user flags, or moderators.
> Dead posts aren't displayed by default, but you can see them all by turning on 'showdead' in your profile.
Even if it's true that a few large businesses own most rentals, that kind of oligopolistic behavior should be undercut by new people entering the market by building more apartments - unless there's a big barrier to entry, like the difficulty in building things when there's restrictive zoning!
> There's no federal zoning laws, so why would everywhere from California to Idaho see the same drastic spikes in home prices?
The incentives that produce NIMBYs - wanting to keep supply low so that housing prices stay high, and not wanting to deal with any of the annoyances of increased density - are the same everywhere.
> Why are existing units that have existed since at least 2010 (and I believe back to 2005) commanding $400 premiums over what inflation would dictate? Do you think back in 2010 they were losing money renting to me?
No, but now there are more people who want to live there and they haven't built enough housing to keep up, so the bidding is more intense.
> The court voted unanimously to reverse the Ninth Circuit, but split 5–4 on the rationale. The majority opinion, by Alito, introduced a new test to define wetlands, which reversed five decades of EPA rule-making and limited the scope of the Clean Water Act's authority to regulate waters of the United States. Justice Brett Kavanaugh joined the three liberal justices in agreeing that the CWA did not apply to the Sacketts' property, but argued that the majority's new definition was incorrect and will have significant effects on regulated waters.
https://old.reddit.com/r/apolloapp/comments/144f6xm/apollo_w... ("Why not just increase the price of Apollo" section)
...huh? "Don't use store membership cards that track your specific purchases" is one thing, but in what world does your credit card processor get info about the individual goods on your receipt?
What are you talking about? Meta stock is up 14% from a year ago, down 26% from two years ago. It was last at a third of its current price eight years ago.
Edit: Oh, I get it. You're selectively measuring from its low point six months ago - when it had fallen 75% from its 2021 peak.
> A better approach is to use an AI-powered service automatically determine the best way to optimize PostgreSQL. This is what OtterTune does. We’ll cover more about what we can do in our next article. Or you can sign-up for a free trial and try it yourself.
That was removed after the article was posted to HN, at dang's suggestion - he posted about it elsewhere in these comments.
The maintainer said this three months ago in a comment on that issue:
> Express 5 is pretty much completed at this point, and we're just finishing up the last code merges in upstream modules in order to bump the dependencies finally in the 5.0 branch.
> Starting with Express 5, route handlers and middleware that return a Promise will call next(value) automatically when they reject or throw an error. For example:
> app.get('/user/:id', async (req, res, next) => { const user = await getUserById(req.params.id); res.send(user) })
> If getUserById throws an error or rejects, next will be called with either the thrown error or the rejected value. If no rejected value is provided, next will be called with a default Error object provided by the Express router.
A chart of filibuster usage over the past ~century speaks for itself: https://bit.ly/3mL6IOU
And that's not even fully up to date: the 2019-20 session ended with 298 cloture votes and the 2021-22 session with 289, per https://www.senate.gov/legislative/cloture/clotureCounts.htm .
> the first filibuster was 11 years after the Constitution was ratified
Sure, whatever - your citation is "wikipedia.org/wiki/Filibuster_in_the_United States_Senate" and mine is "wikipedia.org/wiki/Filibuster#Senate". The exact details don't matter: the relevant points are that it's not a mechanism created by the Constitution, was not common in the lifetime of the Constitution's drafters, and has massively different effects on the governance of the country now than it did in the 20th century, much less the 19th or 18th.
2. Filibusters are not in the Constitution, weren't possible for decades after it was signed, weren't used for half a century after it was signed, and didn't become the "sixty votes required for anything" tool they are today until 10-15 years ago. The founders had nothing to do with it.
This seems like a very dubious claim - the "golden hour" is obvious to everyone, and there's an intuitive mechanism for sunlight being "warmer" in the morning and evening (blue gets scattered in proportion to the amount of air it travels through). Do you have a citation for this?
This is not to say that there's nothing else weird going on in Javascript, but the things people show off most as "wow, isn't this weird?!" aren't that consequential.
Most people's use of technology is heavily punctuated with inscrutable, unfixable issues. If that's your experience, are you going to want to use a tool that you have to invest time and effort in before actually using it productively for the first time?
Edit: One such article for illustrative purposes: https://www.popehat.com/2013/02/05/crime-whale-sushi-sentenc... . In this case, the news-headline number is "up to 77 years" and the plausible range Popehat calculates is 2-2.5 years.
Besides, that's barely pertinent to my point, which is that if you see bugs, you can probably blame them on engineers, but if you see design and product choices you don't like, attributing it to "noob" programming is bizarre.
Popular web pages being choked with ads and modal banners is the result of business decisions to put those there. Jira being notoriously laggy and confusing is the result of prioritizing feature breadth over UX. Apps being built in heavy frameworks is the result of founders and CTOs deciding that they can ship faster and be more likely to make it to the next funding round if they color within the lines than if they focus on speed. Major company products often being poorly designed is the result of organizational fragmentation and lack of a global perspective.
Does everybody always do the best job they could within the constraints they have? Obviously not. Are the problems with technology in general primarily the result of _bad engineers making implementation mistakes_? Absolutely not!