1,736 karma · joined December 14, 2012
What kind of monkey designs something like that. It's obsolescence by design.
I will never buy another Samsung product.
In the first dumpster, you should get a couple of backpacks, rucksacks, and a broom handle (to aid in digging). We'd find all kinds of things. Books we'd resell, lots of porn, lots of perfectly good clothing. It was great.
The best thing we ever found was a giant projection TV (it was the 90s) outside a frat. We took it home, and it turned out the TV had been rained on, and a few discrete components needed to be fixed in the low-voltage section. A couple trips to Radio Shack, and we had a massive frat TV (it was a pain to move it). We went back to the frat a couple of days after we had fixed it, and asked them for the remote. They chased us off.
Dumpster diving in college towns is definitely something the townies do.
I am not conspiratorially minded, but I bet this was because Waltz had Jeffrey Goldberg's number. I bet Waltz leaked things to Goldberg in the past, and this is the Trump administration cutting ties with him in the most "sleep with the fishes" way possible.
My friend passed away a couple of years ago, or I'd have him fill in the details.
I ask that in all earnestness. I am not a MAGA or a MAGA apologist.
Now, they're all fuckwits, but it's not outside the realm of thought.
(BRB, gonna go start a sci-fi story.)
Compilers take the code the programmer writes, and turns it into things called object files. Object files are close to executable by the target processor, but not completely. There are little places where the code needs to be rewritten to handle access to subroutines, access operating system functionality, and other things.
A linker combines all these object files, does the necessary rewriting, and generates something that the operating system can use.
It's the final step in building an executable.
--
More complicatedly: a linker is a little Turing machine that runs over the object files. Some can do complicated things like rewriting code, or optimizing across function calls. But, fundamentally, they plop all the object files together and follow little scripts (or rewrites) that clean up the places the compiler couldn't properly insert instructions because the compiler doesn't know the final layout of the program.
I had an Uber from the campus one day, and my driver, a twenty-something girl, was asking how to become a moderator. I told her, "no amount of money would be enough for me to do that job. Don't do it."
I don't know if she eventually got the job, but I hope she didn't.
* CapEx is up over 60% YoY – they're spending a lot of money on GPU/TPUs.
When I went to recreate it, I contacted QNX and asked if I could speak to the guy who did the work, and he had died the year before. So, I just took apart his floppy, and figured out how he did it.
The things you can do when you invest your time 100% in something.
CS majors (I was EE) aren't generally taught PID, and I have milked my arcane knowledge. It's very profitable to type in the control loop, do some Ziegler-Nichols, and go home early.
EDIT Oh, I forgot the most recent time I've used PID was with the high-school robotics team I coach. We used PID for part of our robot. I didn't go too deep with the students, it's really just a P controller, but it solved the problem, and dramatically simplified the code.
I've done the same thing with potato chips. Lay's are $5-6 a bag here, and the store brand are actually relabeled Herr's (and $2.50). The price increases on junk food have rendered it not-worth-it from a health perspective, and a wallet perspective.
All in all, I'm probably better for it. I say, keep raising prices.
In grad school, my advisor recommended this book, saying, "it will be right up your alley." I bought the second edition, and it was. It is truly a graduate level course in circuit design. I started reading this book (2nd edition) front-to-back, and when I finished it, I started again. It helped me innumerable times when I quit grad school and entered industry.
When the third edition came out, I was at Google in Cambridge, and Horowitz came to talk. I had bought a counterfeit copy from Amazon (by accident), and while he didn't sign it then, he did sign it later (when I got a real copy).
Personally, I think it's worth owning both the second and third editions of this book. It is truly one of the best books about electrical engineering out there.
But, really, don't build stairs like OP suggested.
First of all, I can't really parse your question, but I'll try to answer what I think you're asking.
Go isn't hated at Google – there's just a lot of other code in other languages. C++ and Java are the two most popular, with Python probably rounding out the top three. Go would probably be number 4 (discounting Javascript, because I'm really focused on backend or infra tech).
Go's performance is not as good as LLVM derivatives, but that's not what it tries to be. It's a simple language, that tries to be as helpful as possible to the programmer. I describe it as a big-boy python, but think of it as "the C I always wanted."
Generally, I don't need the performance of C++. I think lots of people that think they do are probably wrong, but I try to not argue on the internet. If I need to get something done, and get on to the next thing, I use Go. Do I leave cycles on the floor and have (very small) GC pauses – yes, but I get my stuff done, and IMO it's a small price to pay.
Use whatever language helps you get your stuff done. Stop arguing over languages.
--
Having said that, if the question is, "why aren't the WebAssembly people mentioning Go?" I don't know. Go's supported WASM for a long-time, and the people inside Google who care about WASM care about Go. There is new stuff in WASM not really taken advantage of in Go, but Go is also a strange animal with a strange stack model, and it takes time. I would think, as with all things Go, it'll be there, but it will take a little time, be thorough, complete, well thought out, and maintained roughly forever.