Similar thought… If it was so revolutionary and innovative, I wouldn’t have access to it. The AI companies would be keeping it to themselves. From a software perspective, they would be releasing their own operating systems and browsers and whatnot.
gcc main.c
- unity build gang
Also depends how hard the AI runs them. A good chunk of the graphics cards that were used as miners came out on life support if not completely toasted. Games generally don’t run the piss out of them like that 24/7, and many games are still CPU bound.
I took his comment to mean recession from bubble popping.
I don’t think you would get much traction on C developers’ existing projects. C gives you the option to do everything your way. If the developer’s paradigm doesn’t agree with the borrow checker, it could become a rewrite anyway.
Most projects don’t use the newer c standards. The language just doesn’t change much, and C devs like that. This might get a better response from the modern C++ crowd, but then you are missing a large chunk of the world.
They are also dev friendly too,
Not saying you’re wrong because I don’t use it, but from the outside, they appear actively hostile toward developers.
100%. In my opinion, the whole “build your program around your model of the world” mantra has caused more harm than good. Lots of “best practices” seem to be accepted without any qualitative measurement to prove it’s actually better. I want to think it’s just the growing pains of a young field.
You shouldn’t have any warnings. They can be totally benign, but when you get used to seeing warnings, you will not see the one that does matter.
And, you can have pointers to bits!
60k rows of anything will be pulled into the file cache and do very little work on the drive. Possibly none after the first read.
Meh. I had a bash job for 6 years. I couldn’t forget it if I wanted to. I imagine most people don’t use it enough for it to stick. You get good enough at it, and there’s no need to reach for python.
Heh, the red alert readme says it currently requires borland for the asm and watcom compiler for the c/c++.
I’m on your side dude. Comments rot. Some are useless. Don’t even get me started on doxygen comments.
She already exists! I swear!
Yeah, I had a silly hack for that. I don’t remember what it was. It’s been 3-4 years since I wrote bash for a living. While not perfect, I still need to know if a pipeline command failed. Continuing a script after an invisible error, in many cases, could have been catastrophic.
Woah, that ((i++)) triggered a memory I forgot about. I spent hours trying to figure out what fucked up my $? one day.
When I finally figured it out: “You’ve got to be kidding me.”
When i fixed with ((++i)): “SERIOUSLY! WTAF Bash!”
I was never a fan of set -e. I prefer to do my own error handling. But, I never understood why pipefail wasn’t the default. A failure is a failure. I would like to know about it!
I’ll give you my vim when you pry it from my cold, dead hands.
Hey! I know the guy working on this. Super cool, detail oriented guy.
AI hype in a nutshell