Frame Relay in the real world

Hey, guys. I've heard a few local people mention that Frame Relay isn't used at all in the real world, at least not commonly, and laugh when it's brought up. Now, I'm not sure if the people who said this are credible and I don't personally know them, but it was just kind of hard to believe that it's as faded out as they say from how prominent it is in Cisco material.
I'm not in the job market yet, so I really don't have an opinion/knowledge of it one way or another and I know that it's a rather old protocol so it's understood if it is true. I really just want to know exactly why and what replaced it(VPNs, I'd imagine) if so. Thanks for your help.
I'm not in the job market yet, so I really don't have an opinion/knowledge of it one way or another and I know that it's a rather old protocol so it's understood if it is true. I really just want to know exactly why and what replaced it(VPNs, I'd imagine) if so. Thanks for your help.

Comments
There are some CCIEs in Twitterverse that said Cisco should take out Frame Relay out of the content since fewer companies are running FR.
MPLS is covered in the CCIP.
You beat me to it, Mrock4.
TE Threads: How to study for the CCENT/CCNA, Introduction to Cisco Exams
Finally, usually I am late to the party!
I've worked for a few places that had frame relay networks, depends a lot on if the company had an existing infrastructure. You'll never need to really configure any of the 'core' items if you're doing LAN work. MPLS is also a provider thing.. the most you may have to do is configure vrf's in your CPE to interface with the provider.. that's also a BIG MAYBE... well shizzle let me give an example
Place I worked for (CLEC) would sell customer T1 right?? well... we also had MPLS ... so the topology was as so... This is a perfect example of configuring frame-relay types and interop with MPLS
{7600}--->DCX--->MUX--->{provider uplink}--->{LEC CO}-->{MUX}---->{Customer CPE}
ip vrf internet
rd 1:1
controller T1 0/3/0
framing esf
linecode b8zs
channel-group 0 timeslots 1-24
!
controller T1 0/3/1
framing esf
linecode b8zs
channel-group 0 timeslots 1-24
interface MFR1
no ip address
frame-relay lmi-type ansi
!
interface MFR1.1 point-to-point
description => Internet
ip vrf forwarding internet
ip address 63.138.x.x 255.255.255.252
ip access-group 101 in
ip inspect DEFAULT100 out
ip nat outside
ip virtual-reassembly
no cdp enable
frame-relay interface-dlci 501 IETF
!
interface MFR1.2 point-to-point
description =>MPLS
ip address 63.139.x.x 255.255.255.252
ip virtual-reassembly
no cdp enable
frame-relay interface-dlci 502 IETF
interface FastEthernet0/0
description LAN
ip vrf forwarding internet
ip address 74.11.x.x 255.255.255.240
ip nat inside
duplex auto
speed auto
!
interface FastEthernet0/1
description $ES_LAN$
ip address 192.168.1.254 255.255.255.0
ip access-group 100 in
ip virtual-reassembly
duplex auto
speed auto
!
interface Serial0/3/0:0
no ip address
encapsulation frame-relay
no arp frame-relay
!
interface Serial0/3/1:0
no ip address
encapsulation frame-relay
no arp frame-relay
ip classless
ip route vrf internet 0.0.0.0 0.0.0.0 MFR1.1 63.138.x.x
ip route 192.168.2.0 255.255.255.0 MFR1.2 63.139.x.x
What this does is allow us to carry internet and mpls by just using the dlci's I guess a poor-man's QinQ for T1
NOTE: When I say internet/mpls traffic I'm really referring to vrf-lite... thought I might add this in
Frame-relay has more or less been taken over by MPLS as mentioned above.
Latest blog post: Let's review EIGRP Named Mode
Currently Studying: CCNP: Wireless - IUWMS