• 1 Post
  • 343 Comments
Joined 9 months ago
cake
Cake day: January 3rd, 2024

help-circle



  • As in if you live in a state with sales tax but down the road is a state without sales tax- why ever shop in your state?

    Mostly the states are quite big, so it’s not worth the trouble. But along various state borders, it distorts the shopping experience in odd ways.

    I’ve been to towns that are missing common retailers entirely, because everyone drives to the next town over (in another state), to avoid a tax.

    We also have a rich history of driving across state lines to purchase stuff that’s illegal in our own state. It’s also illegal to bring it back, but the borders aren’t patrolled, so the only way to get caught is to have a traffic violation while doing it.

    Or so I’ve heard. I never break any laws, myself.


  • Cool chart.

    It really makes the point to me that the PS1 and PS2, when adjusted for inflation, and for relative compute power, were just such a fantastic deal.

    I was recovering from some serious console-purchase fatigue, when I bought my PS1 to replace my garage sale purchased Super NES. It was a big deal to me.

    I’ve paid PS5 prices (inflation adjusted) for a game system a few times (my first Switch and SteamDeck), but they’ve been a lot more mind blowing than what appears to be on offer today.

    Disclaimer: My favorite game is 8-bit, anyway.











  • Well said.

    Here I am trying to wind people up and you’re responding with thoughtful nuanced consideration.

    You make some great points.

    I’ll add - for folks reading along - I do think a class is still almost always an anti-pattern, even with all the OOP class function and factory pattern stuff removed.

    I also feel (as you referenced):

    • Functions being forced to reside inside objects is just stupid.
    • Factory patterns are horrible, because they mix config into program code, maximizing uncertainty when debugging

    And also:

    • Inheritance is almost always a worse idea than an interface.
    • classes tend to have additional fancy tooling to make it easier to carry state data around - which is usually a bad idea

    State data is a necessary evil in most programs.

    I’ve found that most advanced class object implementations treat program state data more like a pet than a threat.

    Sorry for the long response - I know you don’t need it - you know what kind of tool you’re looking for.

    I figure they extra detail above might provide food for thought for folks reading along who are surprised there’s even contrasting opinions on classes.

    (And I feel a little bad for not really posting anything very useful earlier in the thread.)