Why use map() when you could just use forEach()?

For anyone else here, I believe .forEach() to be a better implementation than .map() (with respect to Guil), since he is appending the values to the DOM within the callback.

• .forEach() is best to perform a task with each item of the array in turn (as per this exercise)
• .map() is best to return a new array where each index contains a value which is some modification of the value at the same index of the original array.

Quick example:

const array = [1, 2, 3, 4, 5];
const doubledArray = array.map(num => num * 2); // [2, 4, 6, 8, 10];
let total = 0;
doubledArray.forEach(num => total += num);
console.log(total); // 30;
// Note: this would be better achieved with '.reduce()', but that's for another time ;)

In my opinion, a more appropriate use of .map() for this lesson would be something like:

function generateHTML(data) {
  const sectionsHTML = data.map(person => `
    <div class="section">
      <img src=${person.thumbnail.source}/>
      <h2>${person.title}</h2>
      <p>${person.description}</p>
      <p>${person.extract}</p>
    </div>`) // Now each person object has been 'mapped' over with a HTML block distributing its data
      .join(''); // Remove commas between each 
  peopleList.innerHTML = sectionsHTML; // Only one write to the DOM :)
};

I'm not saying this is the best way of doing it, but I understand this to be a better usage of .map().

My thoughts were the same. The purpose was to iterate over each array and 'do something... period', instead of iterate over each array to return a new modified array.