IRS’ 60-Year-Old IT System Failed on Tax Day Due to New Hardware

Re:IRS’ 60-Year-Old IT System Failed on Tax Day Due to New H... by _RPM on Monday April 30, 2018 @02:17PM (#16960908)

Should it be written in Go, or Rust?

[ Parent | on HN ]

Re:IRS’ 60-Year-Old IT System Failed on Tax Day Due to New H... by bsder on Monday April 30, 2018 @02:30PM (#16961012)

Because that always works so well ...

See the Chrysler Comprehensive Compensation fiasco: https://en.wikipedia.org/wiki/Chrysler_Comprehensive_Compens...

These kinds of systems are all about the exceptions and how you enable humans to deal with those, not the rules and how the computer deals with those.

The problem is that the system first needs a comprehensive test suite written. THEN you could actually think about rewriting pieces.

[ Parent | on HN ]

Re:IRS’ 60-Year-Old IT System Failed on Tax Day Due to New H... by dx034 on Tuesday May 01, 2018 @09:38AM (#16966927)

I have sympathy for Rust but will it be easier to find Rust developers in 2040 than COBOL developers?

[ Parent | on HN ]

Re:IRS’ 60-Year-Old IT System Failed on Tax Day Due to New H... by varjag on Monday April 30, 2018 @02:22PM (#16960953)

Depends on the decade you ask it.

[ Parent | on HN ]

Re:IRS’ 60-Year-Old IT System Failed on Tax Day Due to New H... by mythrwy on Monday April 30, 2018 @11:05PM (#16964319)

Haskell. Obviously.

[ Parent | on HN ]