1989 Detroit Drive season

The 1989 Detroit Drive season was the second season for the Drive. They finished 3–1 and won ArenaBowl III.

1989 Detroit Drive season
Head coachTim Marcum
Home fieldJoe Louis Arena
Results
Record3–1
Division place1st
Playoff finishWon Semi-Finals (Bruisers) 43-10
Won ArenaBowl III (Gladiators) 39–26
Team MVPGeorge LaFrance

Regular season

Schedule

WeekDateOpponentResultsGame site
Final scoreTeam record
1 July 7 at Chicago Bruisers W 40–28 1–0 Rosemont Horizon
2 July 15 Maryland Commandos W 39–7 2–0 Neutral Site
3 July 21 Denver Dynamite L 14–15 2–1 Joe Louis Arena
4 July 28 Pittsburgh Gladiators W 61–34 3–1 Neutral Site
5 Bye

Standings

1989 Arena Football League standings
Team W L T PCT PF PA PF (Avg.) PA (Avg.) STK
xy-Detroit Drive310.7501548438.521W 1
x-Pittsburgh Gladiators310.75015914739.7536.75W 1
x-Denver Dynamite310.750949723.524.25W 2
x-Chicago Bruisers130.25016715541.7538.75L 1
Maryland Commandos040.0007917019.7542.5L 4

Playoffs

RoundDateOpponentResultsGame site
Final scoreTeam record
Semi-finals August 11 Chicago Bruisers W 43–10 1–0 Joe Louis Arena
ArenaBowl II August 18 Pittsburgh Gladiators W 39–26 2–0 Joe Louis Arena

Roster

1989 Detroit Drive roster
Quarterbacks
  • -- Tony Burris
  • 17 Mike Trigg

Wide Receivers/Defensive Backs

Running Backs/Linebackers

Offensive Linemen/Defensive Linemen

Wide Receivers/Linebackers

Kickers

Rookies in italics
Roster updated March 11, 2013
20 Active, 0 Inactive, 0 PS

→ More rosters

Awards

Position Player Award All-Arena team
Wide Receiver/Defensive BackGeorge LaFranceMost Valuable Player1st
Fullback/LinebackerLynn Bradfordnone1st
Offensive Line/Defensive LineReggie Mathisnone1st
gollark: Well, yes, but they're byte sequences.
gollark: I mean, it's better than C and stuff, and I wouldn't mind writing simple apps in it.
gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.