3 ms·
It's 2020. We have planetary scale computers that do exaflop computations and AIs that can slaughter humans at almost any strategy game. The entire stock market
by titzer 7y ago
It's 2020. We have planetary scale computers that do exaflop computations and AIs that can slaughter humans at almost any strategy game. The entire stock market is essentially driven by AI. Drugs are being developed by AI. Bitcoin is consuming more electricity than Ireland.
And yet programmers are still fucking around with move constructors, copy semantics, and host of other horseshit foisted upon us by people who think that saving a copy of a couple words of memory here and there should be absolutely foremost in programming. And then one of those designers has the gall to tell us we are all stupid for not understanding this and blowing our legs off every day.
C++ is such a waste of everyone's time. Don't even get me started on how much computational power its build system wastes.
sigh
- jcelerier 7y ago> exaflop computations Most certainly written in c++ > and AIs that can slaughter humans at almost any strategy game. Guess in what language is trnsorflow written > Bitcoin Ditto
- titzer 7y ago> Most certainly written in c++ Totally beside the point! Actually, FORTRAN mops the floor with C++ when it comes to bigtime numerical computations on supercomputers. And they're all running kernels written in good ole C. Most of the FAANGs are running absolute shittons of Java, Javascript, PHP, and Python. Also running kernels written in C. > Guess in what language is trnsorflow written Derp, tensorflow has to interact with GPU drivers which are all C++ interfaces. Btw it generates shader code which is definitely not C++, but some weird vendor languages, which don't have any of this move constructor related garbage. > Bitcoin Ditto Actually the vast majority of bitcoin's computational load is done by ASICs. Congratulations, you missed the whole point. My point wasn't what languages those things are written in (your Red Herring, not mine), but the fact that we spend an absolute metric shitton of computation on other things, but still expect slow, dumb programmers to fret over niggling details, usually screwing it up in the process, when this task would be far better served by throwing some god damn computational resources at it--you know the ones we waste on O(N^2) compilation tasks and parsing header files over and over and over again.... sigH