Laravel Blade Components... Best practice for props?

There's a great Livewire tutorial on Laracasts by Kevin McKee where he gives an example of using Laravel components for form elements. His example looks like this:

<x-text-input
    wire:model="name"
    type="text"
    label="name"
    :required="true"
    placeholder=""
    class="" />

And the actual component file:

@props([
    'text' => "text"
    'label' => ""
    'required' => false
    'placeholder' => ""
])

<div class="{!! $attributes !!}">
  <label for="email">{{ $label }}</label>
  <input id="email"
    type="{{ $type }}"
    required="{{ $type }}"
    placeholder="{{ $placeholder }}">

etc.

Whereas Laravel Breeze follows the same pattern, but implements it far more simply:

<x-input 
    id="email" 
    class="block mt-1 w-full" 
    type="email" 
    name="email" 
    :value="old('email')" 
    required 
    autofocus />

And the actual component file:

@props(['disabled' => false])

<input {{ $disabled ? 'disabled' : '' }} {!! $attributes->merge(['class' => 'rounded-md shadow-sm border-gray-300']) !!}>

What's the reason for Kevin McKee's approach, when you could simply ignore @props and they would pass through to the rendered HTML anyway (as with Laravel Breeze's approach)?

Edit: Ignore the above question. It totally makes sense now. Still don't understand the following, though:

And why does Laravel Breeze use disabled as a @prop when it could easily be passed through in the same way required and autofocus are?