LetMeEatCake

joined 1 year ago
[–] LetMeEatCake@lemmy.world 3 points 1 year ago

... I didn't say they can't do so. I said they're allowed not to. Since it's allowed, that's what they do.

[–] LetMeEatCake@lemmy.world 7 points 1 year ago (4 children)

Because they're allowed not to do so. The answer is shitty yet simple.

Someone not tipping won't change that either; all that will do is stiff a worker. This needs to be fixed by changing labor laws.

[–] LetMeEatCake@lemmy.world 15 points 1 year ago* (last edited 1 year ago) (33 children)

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.

[–] LetMeEatCake@lemmy.world 12 points 1 year ago

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.

[–] LetMeEatCake@lemmy.world 5 points 1 year ago (1 children)

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.

[–] LetMeEatCake@lemmy.world 20 points 1 year ago (25 children)

This is a result of a SCOTUS decision. SCOTUS membership is determined by the president and control of the senate at the time of vacancies. Neither of those are influenced by gerrymandering.

At the core of it this comes down to 2016 when a larger than typical number of people on the left lied to themselves and said "eh, they're all teh same" and tossed their vote at a third party or just didn't vote at all. Following that, SCOTUS went from a 4-4 tie (with 1 vacancy) to 6-3 conservative advantange.

I wouldn't blame laziness, but instead a combination of apathy and people who are more interested in ideological purity than in accepting the available-better such that they would rather complain about the unavailable-best.

RBG refusing to retire in 2012-2014 also shares blame. She could have retired then and the court would be 5-4 instead.

[–] LetMeEatCake@lemmy.world 6 points 1 year ago

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.

[–] LetMeEatCake@lemmy.world 31 points 1 year ago (15 children)

It's smart, I don't know how people will feel about it but it's smart.

The US and China are in an escalating economic cold war. It's goes completely against US interests to invest finite resources into growing the economy of an economic rival — and ditto for the converse of China investing into growing the US economy. Especially in an aggressively competitive economic sector where relative technological advancement is king for competitive purposes.

[–] LetMeEatCake@lemmy.world 4 points 1 year ago (2 children)

It's convenience and efficiency. At the end of the day a single cable can provide that functionality needed for 99.9% of such devices. Getting everything on a single cable format reduces waste, simplifies people's lives, and even opens up competitive spaces. There's no need for it to be two cables.

[–] LetMeEatCake@lemmy.world 6 points 1 year ago* (last edited 1 year ago)

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.

[–] LetMeEatCake@lemmy.world 19 points 1 year ago (8 children)

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.

[–] LetMeEatCake@lemmy.world 53 points 1 year ago* (last edited 1 year ago)

In theory it's exceptionally illegal to curtail unionization efforts.

In practice, the law has been whittled away by decades of conservative judiciary decisions and weak department of labor enforcement. This isn't helped at all by the balance of power.

Companies can afford to scare off some degree of workers, especially at the lower end of the salary range. Big businesses can survive shutting down a store or losing business at locations indefinitely. Big businesses can afford expensive lawyers and to indefinitely stay in litigation over union busting efforts.

For workers, it's a completely different proposition. Is Walmart or Home Depot or Starbucks going to want to hire someone that is actively suing another major corporation for anything at all? It's even worse if it's labor rights related, but just suing them in the first place is going to make it a struggle to find employment at a lot of places. That's even pretending they can find & afford lawyers. Or that they can handle the transition period from job A to job B even if it isn't difficult to find job B.

These businesses hold all the cards and they know it. You see similar thinking, though different details, behind Hollywood's decision to just try and wait out the striking writers and actors. They can survive losing billions of dollars in income a year from now with unmade projects; striking workers will struggle to get by with no salary.

 

I've been doing occasional weekend day trip to Boston and have been parking at Alewife without any issues. From what I've read on weekdays the parking garages fill up very early in the morning.

What time of day do the garages start to have free spaces again? If it matters I'm open to parking at any of the outer terminus stations: Oak Grove, Alewife, Riverside, Braintree, whatever. It doesn't need to be Alewife.

There's a weekday concert in mid September I want to see. If I knew I could reliably park sometime in the afternoon (or late morning), that'd give me the push to go ahead with getting a ticket.

view more: next ›