A DVD/Blu-ray/CD player and a digital TV tuner.

I think it costs less too, whereas a new or used PS5 costs more but doesn't add a lot of value -- there are roughly 15 exclusive games for the PS5 so it's not compelling if you have a gaming PC, but it is a nice package to sit next to your TV that does a lot and can stream games from the gaming PC. Personally I like a PS4 controller better than the Apple TV thing.

The launch edition doesn’t? I’m surprised vendors even sell a bluray drive that doesn’t have that capability. I guess sony wanted to cut every cent off they could…

That's cool! We'll still need to change all of the references to `resource[0]`, right? Or does tofu obviate that need as well?

I’m not sure I understand. You refer to the conditional resource fields normally - without list indices. You just have to make sure the object isn’t null.

There’s some samples in the docs[0] on safe access patterns!

[0]: https://opentofu.org/docs/language/meta-arguments/enabled/

You were seeing the base64 image tag output at the bottom. The SVG input is at the top.

My first concern is that this looks very difficult to remove if the battery begins to swell, as silver-oxide batteries are wont to do. Perhaps that's less likely with single use batteries.

This is one of the reasons why we decided not to have rechargeable batteries! We saw what happened to the Samsung ring.

There is no risk of swelling with Index 01

I thought you might find it interesting to know that it’s “wont” instead of “want”, when saying “wont to do”

https://www.merriam-webster.com/dictionary/wont

Also: I agree with your concern

I'm embarrassed. Thanks for the correction!

Don’t be :) learning is lifelong

Should be relatively straightforward to remove with a small wire cutter.

just like with the samsung rings, oh wait...

No, not if you rewind them. At least mine doesn't. But I can't trust the tension on a new tape.

It's not obvious to me that we should avoid padding, or why it's seen as undesirable.

Padding ties up capital, it reduces credibility, it delays deployment, it adds costs through delay. It is bad for organizations. However, it is a great solution if you're a worker in a bureaucratic environment that can tolerate large costs, but is intolerant of 1-day of schedule slips. It's a great solution for complacent management, who are confused about the game they're playing and wants to report that they're "on track", which means "not late".

The agile solution of incremental value delivery is a compromise, and can produce good outcomes for functional changes. But agile has unacceptable failure modes when working on infrastructure and satisfying system constraints. Agile can work okay for programmers, but it's not a solution for engineers. Acknowledging, owning, and managing risk is more scalable, but you have to have leaders who acknowledge that they exist and have the maturity to take on that responsibility.

> Padding ties up capital, it reduces credibility, it delays deployment, it adds costs through delay.

Well done timelines are a negotiation between the stakeholders and engineers. The stakeholders need something done for the business, the engineers give a timeline. If that timeline works for everyone, great. If it doesn't, then the stakeholders will ask if it can be done in a faster time.

A timeline that lands on time, or early, is good. The point of timelines is that teams outside of engineering are resourcing their projects based on your timelines. They may have made outside commitments to customers, they may be lining up marketing, they may have embargoed PR, it may be delivered by someone at a conference, etc.

A project running late can be catastrophic. Bad customer relations, wasted marketing spend, pulling back stories from PR, delays for dependent teams, etc.

You pad to make sure your timelines aren't overly optimistic, because we're all bad at estimating, and it's possible our dependencies are too. By padding, when it comes time to negotiate for shorter timelines, you also have some wiggle room.

Bureaucratic environments tend to be larger companies and they care about schedule slips, because they have more teams being impacted, and those teams are handling larger numbers of overall projects. Schedule slips can lead to cascading failures.

Agreed. I don't find the 38 percent figure to be surprising. I have no basis on which to find it surprising so the author's incredulity is baffling.

> Same goes for clothes, toilet sounds, etc.

What do you mean "same goes"? Are you saying there are cultures in which being loud on the toilet is considered proper?

No it isn't. You can slurp noodles without being rude but they do not consider 'loud mouth noises' respectful.

First link: That is a Swedish robotics blog and the sources linked are just landing pages for Chinese tours or language lessons.

Second link: Where do they say that 'making loud mouth noises is a sign of respect'? They say 'people slurp noodles' which is exactly what I said.

> It's so common that the only logical explanation is that it is encouraged. It appears to be the norm and the non-slurper is the exception. I'm glad that your parents taught you to not slurp. You are an exceptional individual.

Anyway I’ve asked enough Chinese people about it to get the same answer. Not all do it, but some do it for these reasons.

I doubt you ever asked any Chinese.

They are saying it is normal to slurp noodles, which is what I said in my first reply to you. They did not say that they make 'loud mouth noises' as a sign of respect.

Ask this specific question: "Do you make loud mouth noises while you eat as a sign of respect, or is it just normal to slurp noodles?" and see what answer you get.

That's a pretty common config pattern. SublimeText does that, and when you edit the settings it opens a 2 paned editor with the default config on the left and user config on the right.