hctaw

20 ms·

151.
by hctaw 6y ago
"Makee" and "makees" aren't in the dictionary but native speakers would probably understand what you mean
152.
by hctaw 6y ago
On some low power architectures without FPUs it is significantly more power/compute efficient to use fixed point arithmetic. But that's really it.
153.
by hctaw 6y ago
Fixed point is obsolete on the vast majority of compute devices today. It is only a reasonable alternative in ultra low power scenarios or on tech stacks that haven't migrated to modern architectures, like some DSPs (which are also rea
154.
by hctaw 6y ago
The program doesn't "know" anything. The executable has a header used by the loader that tells it to use libc. If the libc version does not contain the symbols that the program expects or the symbols do not have compatible de
155.
by hctaw 6y ago
That assumes you have a header, which only exists at compile time for the developer. The running program knows nothing about it.
156.
by hctaw 6y ago
Custom allocators are quite common, it's not an arcane convention. I think the rule of thumb is preallocate until it gets questionable in complexity, then write your custom allocator - and really it's only applicable to code with
157.
by hctaw 6y ago
Because not everything is recompiled from source. That's why stable ABIs need to exist.
158.
by hctaw 6y ago
Most of these things can't be fixed at the language level without seriously breakages or preventing users from doing necessarily dangerous things.
159.
by hctaw 6y ago
The solution to these problems is spinning off business units. That's why people say "break up big tech" and not "fine big tech."
160.
by hctaw 6y ago
I wouldn't have expected an Apple device of the last generation to fit your needs, let alone the new ones. Why did you buy the computer?
161.
by hctaw 6y ago
I'll use what I can read. I can't parse that at a glance, and won't use it. The real pro tip is: don't use bash if it's not trivial to read
162.
by hctaw 6y ago
The original poster was paying for iCloud storage with their apple card, which is an Apple service.
163.
by hctaw 6y ago
The problem of a heterogeneity in GPGPUs is that AMD and Intel can't make products that are competitive with NVidia. The "programming model" for "cross industries" (whatever those mean, the whole naming of this proj
164.
by hctaw 6y ago
My uneducated guess is that they don't have a good way to keep the app signatures intact when patching binaries.
165.
by hctaw 6y ago
Disclaimer: I've only worked on lower parts of the stack so my experience is biased. It's mostly the concept of "garbage in, garbage out." There's a simple fix for most audio problems: - use wired headphones - use a
166.
by hctaw 6y ago
Many of my documents are accessed electronically through various web services. Many of them function poorly or not at all with Firefox. I'm sure I could make a phone call and get them mailed to me, but "don't use the internet
167.
by hctaw 6y ago
A $10 billion investment in anti aircraft missiles that forces a $100 billion investment in aircraft instead of schools and semiconductor fabs is great ROI for an adversarial nation state that knows their government would be wiped off the f
168.
by hctaw 6y ago
Cool story, I still have to use Chrome to talk to my doctor, view my healthcare documents, and get my W2. While Firefox is "doing the right thing," me, the Firefox user, has to use a different browser that doesn't respect my
169.
by hctaw 6y ago
The risk of downing a manned aircraft for a nation state is much higher than a drone.
170.
by hctaw 6y ago
we dump money into both
171.
by hctaw 6y ago
You still have to shoot down a fighter jet to disable it. An enemy can't hack the pilot remotely and safely land it on their own air strips, which has happened with drones.
172.
by hctaw 6y ago
The race car/pickup truck analogy is useful here. The F35 failed because they tried to make a vehicle that could be both a race car and a pickup truck, and wound up making one that is more expensive and worse at both jobs than building
173.
by hctaw 6y ago
> Regardless of Firefox abiding by the standards (or doing what Chrome does) or not, this was always going to be the case, and so it isn't that big a deal. It's a huge deal to me as a Firefox user. This is a total anecdote, but
174.
by hctaw 6y ago
call the warehouse or walk into it
175.
by hctaw 6y ago
For the last three years I've had to use my phone's flashlight to peruse the shelves in the Burbank store because they couldn't be bothered (or afford) to turn the lights on. Fry's saved my ass a couple times. Once it wa
176.
by hctaw 6y ago
Probably checking that SignIn.app's signature is valid
177.
by hctaw 6y ago
well anything that takes untrusted input that might need to be validated with parsing is a massive security hole. Parsing generators don't fix this class of bug, they just change how it manifests.
178.
by hctaw 6y ago
> We never need to see each other live code. That would be annoying/intruding on the other engineer's privacy. I do need to pair program remotely, and collaborate on design docs. Collaborative editing isn't like a 24/
179.
by hctaw 6y ago
This has been my experience as well, but I'd extend it to parsing in production. There are a million reasons why you need to write custom parsing code and 99% of them are faster and better implemented by hand than using a generator.
180.
by hctaw 6y ago
I think if your syntax and semantics imply the stack-ness of your coroutine implementation then you you have a language design problem. Coroutines are subroutines with two additional primitives (resume after call, and yield before return).

More ›