Quite a few list type views include logic to add a first class to the first item and a last class to the last item on the list. Do we really them?
IMO these complicate the views with little benefit. Especially considering we can now easily target these items with CSS pseudo classes like :first-of-type and :last-of-type.
Losing them is a potential b/c break with templates which happen to use them.
| Labels | Added: 
? | ||
 
                | Category | ⇒ | Layout | 
| Status | New | ⇒ | Discussion | 
 
                Before removing, double check the JS to ensure they're not being referenced there
| Labels | Added: 
J4 Issue | ||
| Status | Discussion | ⇒ | Closed | 
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-06-27 09:32:18 | 
| Closed_By | ⇒ | ciar4n | 
I'd say drop them. About the only reason I can see to keep them is if you're still supporting IE8 where the pseudo-classes aren't reliably available, and that's obviously not in J4's supported stack.