• 0 Posts
  • 82 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle


  • Service charge I would presume is primarily paid out to the non-wait staff at the restaurant. The kitchen in particular.
    Tips go to the wait staff, and they will pay some of that out to other staff (e.g. front staff) depending on how the restaurant works.

    These are going to be separate. The service charge is there so they can increase prices by a tightly controlled amount without needing to fuck up the carefully targeted price points ($8 or $7.99 is a lot better than $9.44). Which is shitty, to be clear: it’s a hidden way to increase prices while still advertising the same price. But it’s not something that replaces or complements the tip, it’s just a shitty price-adjustment.

    A waiter or waitress is still going to be dependent on the actual tip.


  • The basic outline of where to split the company seems straightforward to me.

    AWS get split off first and foremost, that part is blatantly clear to me.
    From there, the retail webstore (what we generally think of as “Amazon”) gets split off from its broad category of services: music and movie streaming and everything in that category.
    After that, split anything that involves designing/repurposing other designs and selling a specific consumer product off. Kindle, Alexa, Roomba (if that purchase goes through), Amazon Basics, etc.

    I think there’s a decent amount of room to get more granular with the process, but I think that covers it as a basic outline.


  • BRICS isn’t an alliance or a cohesive entity. It’s the equivalent of the G7 for major non-western economies. India and China hate each other. China and Russia only really get along in being anti-US. Brazil and South Africa have no real intersection with the geopolitical goals of the other. BRICS isn’t a geopolitical anything of any meaning.

    I suspect India is doing this for the simple reason that they have zero control over Windows while they would have as much control as they want over internal-Linux use. They’re large enough that they can make it work, assuming they’re willing to dedicate the people and the money to it and put up with the non-insubstantial switching costs. Open question on what their follow through will look like, but it’s entirely within their capability.


  • Not a final decision. SCOTUS (via Kagan) refused to overturn a stay on a decision while legal proceedings continue. Basically just an order to keep things as-is until the case finishes working its way through the courts.

    Which as I understand it is generally how things work: if there’s no clear likely winner, go with the interim situation that most easily can be rectified if it is later ruled to have been wrong. In this case, if the ruling goes against Apple than they can be ordered to give money to Epic and other app-owners based on the revenue brought in from them to Apple during the appropriate period. The opposite case would require more complex estimates (how much revenue was shifted away from Apple incorrectly, in the case where Apple wins) and further it’d result in unnecessary consumer friction: users would go from A to B then back to A again.




  • This is speculation based on the combination of physical constraints and changing usage.

    Phone batteries today are in the 10-20 watt-hours range for capacity, or at least iphones are and that’s the data I found. Going from the typical ~20W fast charging rate to the full 240W capacity of USB-C EPR would allow a twelve times increase in battery capacity with no change to charge times. Are batteries going to increase in capacity by twelve times in the next 17 years? I’d be shocked if they did. The change from the iphone 1 to the iphone 14 pro max is 5.18Wh to 16.68Wh — a three times increase in 16 years.

    Likewise, with data transfer, it’s a matter of how human-device interaction has shifted with time. People increasingly prefer (a) automated, and (b) cloud based data storage, and (c) if they do have to move data from device 1 to device 2, they would rather do it wirelessly than with a physical connection. USB4 on USB-C is meant for 80 Gbit/s = 9.6 GB/s transfers. That’s already faster than high end SSD storage can sustain today, and USB4 is a four year old standard. People on phones are going to be far more likely to be worried about their wifi transfer speeds than their physical cable transfer speeds, especially in 2040.

    Then, on top of all of that… USB will continue to be updated. USB-C’s limitations in 2033 will not be USB-C’s limitations in 2023, just as USB-C’s limitations in 2023 are not the same as USB-C’s limitations at its inception in 2014. In 2014 USB’s best transfer rate was 10 Gbit/s, or 1/8 what it can do today.


  • I’d be surprised if USB-C was a limitation on phone technology even by 2040. The bandwidth and power delivery capacity are way beyond what are needed now. Data transfers from phones are going to increasingly move to wireless in that time frame too, I expect.

    The limitation on the viability of USB-C with phones won’t be the actual technological viability of the standard with respect to phones. Instead, the problem for USB-C for phones will be if another standard comes out and starts being used by other devices that do need higher bandwidth or power delivery capability. Monitors, storage devices, laptops (etc.) will eventually need more than USB-C can provide, even with future updates to its capacity. When those switch over to something new, that will be when phones (and other devices) will need to consider a new standard too.



  • You’re also making the implicit and incorrect assumption that this assumption of future income is not already the status quo. It is. The IRS already does this with your automatic withholding. It just does it at a higher level than necessary, due to what I mentioned above. Withholding basically assumes that a person will continue to earn whatever their paycheck was in every future payment period (weekly, semimonthly, whatever).

    Your assumptions on how this would be dealt with are not realistic. The outlines of how to implement this not only already exist, they are already used and have been used for decades. All the IRS needs to do is glue together its knowledge of your income sources and lower the withholding amount based on being able to predict an individual’s income far more accurately.

    Data on seasonal income is known too, for the record. Consistent trends in income changes with parts of the year are not a surprise to the government agencies that care about it.


  • For the majority of people out there, all their income is going to have digital records. A cash only store still deposits money in a bank, after all. For the people that don’t… chances are their income without a digital footprint isn’t being reported, and is small enough that no one is worried about that in the first place.

    If the IRS is being told by a person’s work how much they’re paid, by their bank how much interest they got, by any Etsy-esque services how much they were paid… then the IRS has every bit of information it needs to get automatic withholding correct.

    Right now withholding systems default to taking too much money out, because it’s easier for the government to send you money than it is for them to request money from you. It also avoids the headache of most people being hit with surprise IRS bills. The IRS could keep that default, and then as the year goes on it could shift that withholding down until it’s laser close. The negative there is that variability is bad for budgeting too, but with some work they could make it start close enough that it shouldn’t be all that variable.


  • The report gives a quick summary of what they include, but not any details or math.

    The cost of underlying energy (gas, diesel, electric)
    State excise taxes charged for road maintenance
    The cost to operate a pump or charger
    The cost to drive to a fueling station (deadhead miles)

    Elsewhere it says it assumes 12k miles in a year and is focused on the midwest and Michigan in particular. As it so happens, Michigan charges for registration based on the car value. EVs cost more than ICE vehicles in the same market segment most of the time. This would fall under excise taxes that they include.

    I wouldn’t be surprised if they also tacked on the cost to install a L2 charger once as “cost to operate a pump or charger” — intentionally ignoring that it’s a one-time fee to support EVs at a home. With those two data points they could easily add >$1000 to the cost to “charge” an EV for one year if that is what they wanted to do.

    The people making the report clearly picked criteria that sounds reasonable but also intentionally misleads people. Not a surprise.







  • After a certain point, scores are as much based on hype as quality.

    That’s not even a malicious choice, either. Hype influences our experiences and perceptions of whatever is being hyped. It’s intuitively obvious that people will enjoy a good thing that they are hyped about more than a good thing that they are not hyped about. Hype is strongest just before release… which is exactly when reviewers play and assign a score to a game.

    A sequel to a well received game is going to have more hype than the predecessor in most circumstances. Morrowind sold something like 5-10x the copies as Daggerfall and came about at a time when there was a lot of upheaval in the industry from a target-audience standpoint: a lot of potential Morrowind players (and reviewers) would have not played Daggerfall.

    In essence, Oblivion was reviewed more positively because of the positive reception of Morrowind. The positive reception of Oblivion in turn boosted Skyrim.

    This is not to say people would hate the games without the prior game before it or hype, just that there is a “hype boost” for games.