In the spirit of redefining the kilobyte, we should define byte as having a nice, metric 10 bits. An 8 bit thing is obviously a bibyte. Then power of 2 multiples of them can include kibibibytes, mebibibytes, gibibibytes, and so on for clarity.
On RISC machines, it can be very useful to have the concept of "words," because that indicates things about how the computer loads and stores data, as well as the native instruction size. In DSPs and custom hardware, it can indicate the only available datatype.
The land of x86 goes to great pains to eliminate the concept of a word at a silicon cost.
ARM64 has a 32-bit word, even though the native pointer size and general register size is 64 bits. To access just the lower 32 bits of a register Xn you refer to it as Wn.
Appeasing that attitude is what prevented Microsoft from migrating to LP64. Would have been an easier task if their 32-bit LONG type never existed, they stuck with DWORD, and told the RISC platforms to live with it.
I'm saying the term "Word" abstracting the number of bytes a CPU can process in a single operation is an outdated concept. We don't really talk about word-sized values anymore. Instead we mostly explicit on the size of value in bits. Even the idea of a CPU having just one relevant word size is a bit outdated.
I got an amazon gift card because there was a promotion for $12.50 credit, and then with the prime card that's an extra $3 credit. So basically a free $15 for spending money on money I'll eventually spend anyways.
That's when you give em the name "a" and a temporary email address. Gives them one more chance to prove themselves, and if not, they get left with garbage in their database.
Maintenance is always done on site. Do you think the workers on oil rigs take a commute to land every night? No, so people are going to need to live in space to solve problems in space.
Until a general purpose robot that can do all the things a human can do is developed and can be more cheaply deployed than a human, a human's gonna do it instead.
That is true. But keep in mind two things: first, the robot does not have to be fully autonomous, and second, maintaining a human in space is so expensive that we already have such robots. Just look at Curiosity and its cousins.
I don't think Curiosity and its cousins can tighten down leaky bolts on pipe connections, which is what I think of when the term "maintenance" comes up. The closest we have right now in that vicinity is Spot from Boston Dynamics, and it basically only acts as a universal monitoring tool to go yell at a human to fix things.
I guess what I'm saying is that robots can identify problem points, but at the current time can't actually troubleshoot or resolve those problems. Those are really difficult problems to solve.
Get a job at a government contractor; I haven't done shit in several months. I hate it though because of the constant politics and my lead being generally incompetent.
Yeah, I'm trying to avoid places with politics. If my current job didn't involve so much office politics then I would probably say I could coast here. But working on the politics is one of the more annoying parts and definitely takes up some time.
Makes sense to me (but I'm of course biased) due to selection bias. My impression is that those for whom APL clicks, find the day-to-day APL experience very enjoyable, while those that just don't get it will tend to leave APL behind. Probably not so for more widely-used languages, where people will stay with them, even if it means daily frustration.
