Recent searches
Search options
@brianb@fosstodon.orgGonna do a poll because why not.
If you're a #webdev or webdev #teacher, I need input on what to do next with a first year web development class.
We're working on JS. Just finishing up a simple rock/paper/scissors game to learn about conditionals and flow control & more DOM practice, etc. I need a next project that will push them a little and add some new concepts.
Thanks in advance, boosts appreciated.
@brianb IMO: Map, Filter, LocalStorage are all useful but *somewhat* niche. You won't always need them, and they can be worked around. They're sugar of sorts.
API's and Fetch though - There aren't really alternatives, they are broadly useful, and they allow for making use of things *someone else made*, which is in itself interesting.
I'd go with API's and Fetch next; map and filter (and local storage) can come as part of parsing that returned data after.
@mattwilcox My only hesitation with fetch is the complexity of async work. Async/await makes it easy, but I need to do some mental prep before starting them on that route :-)
I agree with your assessment, though. Fetch is pretty fundamental.
@brianb Yup, that’s fair too. I don’t think you can go wrong really in either order, but I aren’t sure if localStorage/filter/map etc are a step to Fetch or just a different thing to learn.
@brianb Granted a dad joke generator will cover more real world development stuff, a todo list would help you avoid issues with an api being down