Comment Re: It's not the language it's the management (Score 1) 58
you can get this behavior in C if you tag your pointers with strict
I meant restrict, of course.
you can get this behavior in C if you tag your pointers with strict
I meant restrict, of course.
Some parts of C are easy to learn but pointers, particularly double and beyond , plus pointers vs arrays, tends to trip up the no hopers.
They'll have the same problem with Rust, which also uses pointers all over the place (though it calls them references). The difference is that the no hopers will be unable to get the Rust code to compile, while with C they can get it to build... and then hope that valgrind can find the ways it's broken -- because it is broken. They might be able to get the Rust to compile by eschewing pointers and cloning every damned thing so the borrow checker will shut up, making their code so inefficient that they might as well just write Javascript, or else by using raw pointers in unsafe blocks -- but unsafe Rust is actually more unsafe than C, with a lot more rules you have to follow and things you have to be careful about, so their code will be far less likely to work than it would in C, even.
(For those who haven't looked into it, the rules the borrow checker enforces don't go away just because you're using raw pointers in an unsafe block. The borrow checker stops enforcing the rules but the compiler absolutely continues assuming they're properly followed. In other words, in unsafe blocks you have to be the borrow checker. C intentionally gives up some performance to be more forgiving. Rust. Does. Not.
For one example: The C compiler assumes that any pointer may be aliased and so generates extra instructions to read and write through pointers when if it could know that the pointer was the only thing in the system referencing that memory it could optimize those away. The Rust compiler assumes that if you have a non-const pointer to some memory, that pointer is the only way in the program to modify that memory, so the compiler is free to optimize away any unnecessary reads or writes, and to reorder things as convenient (you can get this behavior in C if you tag your pointers with strict). If you stay in the safe Rust pool, using references, the bounds checker ensures that the compiler's assumptions are always true. If you write unsafe, though... it's on you. Screw it up and your code will be broken in crazy-subtle ways.)
More like heâ(TM)s lazy and his talent was being at the right place at the right time
I'm thinking "talent" may be a strong word here....
I mean, the words "rap" and "music" are mutually exclusive terms after all, eh?
SCO, the Santa Cruz Operation, was a pretty cool company that had nothing to do with any of this crap. They sold a pretty decent x86 Unix throughout the 80s and early 90s, but ultimately were forced out of business because they found it hard to compete with the Microsoft marketing machine pushing Windows NT on one side, and free, open source Linux on the other side.
Unable to continue, they sold their Unix rights to Caldera Systems, renamed themselves Tarantella and were ultimately bought out by Sun Microsystems. It was Caldera that ultimately morphed into The SCO Group, then became a copyright troll hoping to score a settlement with deep-pockets IBM when it realized that it couldn't make UnixWare competitive either.
As we did 20 years ago, we should call the original company SCO and label the copyright troll TSG to keep them straight. They were not in any way the same company; there were no leaders or employees or buildings or anything in common.
Walking on two legs is not a smart mode of locomotion for a machine.
I do not understand the point of colorful lights in keyboards and the like. But then, I am not mentally 5 years old.
Sorry your heart is dead, but a lot of us still understand fun.
If you do not find fun as an adult, you are doing it wrong. Here is a hint: Regressing yourself to a mental child is not the way to do it.
We should have the tools. I'm not arguing that we should go back to agrarian lifestyles. But somehow we as a society should find a way to not permit wanton waste of resources in the name of cheap, fleeting entertainment.
That's not the problem. The problem is we already are in a scenario where we have two good jobs for every five people. A good job here is something that lets you afford a one-bedroom apartment by yourself in a city that consistently has employment.
Apparently you and those like you, ONLY consider a city to be the equivalent of of NYC....which is quite the outlier.
Most other cities across the US, with plenty of good jobs, allow you to afford MUCH better than a 1 room apartment.
The issue is that those videos are being created en masse. People would simply not create them in the first place. Making resources so easily available that people waste them without thinking is the reason capitalism has turned our society into a planet destroying machine and called it "quality of life". Nobody's quality of life is improved by the existence of videos of fake cats doing improbable things, yet we've now invested a civilization worth of resources into creating them. It's the broken window fallacy, writ so large that it's unrecognizable.
Funny how they've got that blue barrier for them to crash into at the finish line, then they get carried away on stretchers. Should be an interesting story behind that.
Did they completely tap their battery for the final sprint and can't even stand anymore? Or were they never programmed on how to stop?
Problem is people aren't just querying. They're saying "generate a video of a cat riding a shark", which uses a LOT of inference and compute.
But then you would not have learned the value of a 10 second Google search before asking a question with an extremely easy to find answer.
Literally older than my account. Just.
If you don't have time to do it right, where are you going to find the time to do it over?