No Y2K? Try Y2K38 & Co.
We have witnessed the failure of Y2K but some of us wasn't quite sure about it's reason. Now we know that C Programming Language stores time variable in 32 bit signed integer and so it delays Y2K bug but takes rebirth as Y2K38. There are some other bugs hanging around too namely Y2184 and Y29990. But these aren't for worry today. Yet these bugs need attention and be rectified as quickly as it can. Whatever be the solution for it e.g increase variable capability by increasing it's bit size or storing it in unsigned format, our computer hardware needs to get improved first and then some mind can be put into creating some other programming language for coding Operating Systems.
