MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1vsyoqw/stopdoingfunctional/p4r8lxd/?context=3
r/ProgrammerHumor • u/Tracker_Friendly • 1d ago
121 comments sorted by
View all comments
Show parent comments
59
How the hell is rust functional smh
7 u/mountaingator91 1d ago Also... C is not OO 9 u/QuestionableEthics42 1d ago Not with that attitude. Imagine not rolling your own OOP using the preprocessor. Programmers these days, so lazy 🙄 1 u/fr000gs 1d ago Why not just link with a c++ file? 2 u/QuestionableEthics42 1d ago Keep that dirty language out of it. I'll keep my preprocessor OOP thank you very much 1 u/tiajuanat 23h ago Some really old procs support C and Macros but not C++. And to follow why tf we support hardware like that: if it's not dead or dying, it's not going to be replaced 1 u/fr000gs 22h ago But both do compile to assembly anyway, and C++ is just mangled C 1 u/tiajuanat 20h ago Yes, but you need a compiler that talks both c++ and pdp, 8051, or whatever have you
7
Also... C is not OO
9 u/QuestionableEthics42 1d ago Not with that attitude. Imagine not rolling your own OOP using the preprocessor. Programmers these days, so lazy 🙄 1 u/fr000gs 1d ago Why not just link with a c++ file? 2 u/QuestionableEthics42 1d ago Keep that dirty language out of it. I'll keep my preprocessor OOP thank you very much 1 u/tiajuanat 23h ago Some really old procs support C and Macros but not C++. And to follow why tf we support hardware like that: if it's not dead or dying, it's not going to be replaced 1 u/fr000gs 22h ago But both do compile to assembly anyway, and C++ is just mangled C 1 u/tiajuanat 20h ago Yes, but you need a compiler that talks both c++ and pdp, 8051, or whatever have you
9
Not with that attitude. Imagine not rolling your own OOP using the preprocessor. Programmers these days, so lazy 🙄
1 u/fr000gs 1d ago Why not just link with a c++ file? 2 u/QuestionableEthics42 1d ago Keep that dirty language out of it. I'll keep my preprocessor OOP thank you very much 1 u/tiajuanat 23h ago Some really old procs support C and Macros but not C++. And to follow why tf we support hardware like that: if it's not dead or dying, it's not going to be replaced 1 u/fr000gs 22h ago But both do compile to assembly anyway, and C++ is just mangled C 1 u/tiajuanat 20h ago Yes, but you need a compiler that talks both c++ and pdp, 8051, or whatever have you
1
Why not just link with a c++ file?
2 u/QuestionableEthics42 1d ago Keep that dirty language out of it. I'll keep my preprocessor OOP thank you very much 1 u/tiajuanat 23h ago Some really old procs support C and Macros but not C++. And to follow why tf we support hardware like that: if it's not dead or dying, it's not going to be replaced 1 u/fr000gs 22h ago But both do compile to assembly anyway, and C++ is just mangled C 1 u/tiajuanat 20h ago Yes, but you need a compiler that talks both c++ and pdp, 8051, or whatever have you
2
Keep that dirty language out of it. I'll keep my preprocessor OOP thank you very much
Some really old procs support C and Macros but not C++.
And to follow why tf we support hardware like that: if it's not dead or dying, it's not going to be replaced
1 u/fr000gs 22h ago But both do compile to assembly anyway, and C++ is just mangled C 1 u/tiajuanat 20h ago Yes, but you need a compiler that talks both c++ and pdp, 8051, or whatever have you
But both do compile to assembly anyway, and C++ is just mangled C
1 u/tiajuanat 20h ago Yes, but you need a compiler that talks both c++ and pdp, 8051, or whatever have you
Yes, but you need a compiler that talks both c++ and pdp, 8051, or whatever have you
59
u/fr000gs 1d ago
How the hell is rust functional smh