catiopatio

13 ms·

91.
by catiopatio 3y ago
On my system, where clang is statically linked, the binary is 48mb. As in megabytes. Nearly all of clang and LLVM are linked as libraries.
92.
by catiopatio 3y ago
This is a very serious accusation you’re leveling, and it does not appear to be supported by the facts. Conflating that anodyne image with “disturbing imagery with young girls or hypersexualized, extremely young women” is wildly irresponsib
93.
by catiopatio 3y ago
How about: After a landmark constitutional amendment guaranteeing absolute equity under the law, the government mandates the implantation of “equalizers” in all citizens at birth. These brain implants suppress intelligence to a standardized
94.
by catiopatio 3y ago
Thanks. I’ll be honest, I’m avoiding giving 404media any clicks and was responding solely to the commentary here. The last thing I want to do is contribute traffic to vapid outrage-bait Vice/Motherboard-style journalism, and HN has bee
95.
by catiopatio 3y ago
The general public knows what a “magazine” is. Even if we didn’t, it’s a journalist’s job to inform. Using “clip” isn’t just a colloquialism — it refers to a different thing entirely, and is incorrect. If they genuinely believe the public i
96.
by catiopatio 3y ago
Surprised you didn’t use the perennial “boomer” to describe anyone over 40. The statistics don’t lie. Drivers under 25 are much higher risk than drivers over 40.
97.
by catiopatio 3y ago
This makes perfect sense to me, as someone who lives in a college town and witnesses the uptick in terrible driving when the students return. Fortunately, my anecdotal experience isn’t necessary to make this call. Insurance companies are we
98.
by catiopatio 3y ago
“railway oriented programming” (aka nomadic effects) don’t require that. As a bonus, you can’t accidentally fail to catch an exception, and you can model much more complex error handling than just ”catch and raise.” For example, it’s trivia
99.
by catiopatio 3y ago
That sounds incredibly ugly and painful.
100.
by catiopatio 3y ago
Do you write a try block around every call you make? How do you know what calls will throw exceptions and unwind the stack?
101.
by catiopatio 3y ago
How do you know what to cleanup when you have no idea which APIs might throw, what stack frames might have been skipped when they do throw, and what state was left broken by yeeting a stack-unwinding exception up your call stack?
102.
by catiopatio 3y ago
External services having gone offline, timeouts, and invalid user input are expected conditions you should handle locally. Almost everything else you listed represents a bug in your software that should terminate execution. I’m more than a
103.
by catiopatio 3y ago
> That's all very well as long as people actually do that. It doesn't always happen in practice. And even when they do, the abstractions are likely to be leaky ones. They don’t have a choice under “railway oriented” API in a ty
104.
by catiopatio 3y ago
No; you simply abstract the underlying subsystem’s exceptions in your own types, the same way you do with any other type. And yes, “railway oriented approaches” can absolutely do this.
105.
by catiopatio 3y ago
You could have learned enough vim to be usable in the time it took to write that comment.
106.
by catiopatio 3y ago
I’m not sure that’s a great interview question; the right answer to google the appropriate algorithm (e.g. Fisher–Yates), make sure you understand implementation errors that will lead to bias, and implement it over any arbitrary sequence.
107.
by catiopatio 3y ago
> "make a linked list" no, just use a library like everyone else. If you cannot sketch out a simple linked list on a whiteboard, you’re not an engineer and have no business being hired as one at a place like Apple, full stop. I
108.
by catiopatio 3y ago
In addition to the cost advantage, HDD firmware is simpler and more reliable.
109.
by catiopatio 3y ago
What file systems support transparent tape loading? That’s a neat feature, but I’d expect a lot of software to behave badly if local file system operations suddenly started exhibiting tape-level latency.
110.
by catiopatio 3y ago
SGI also made an LCD display with a detachable backlight panel for this purpose — the Indy Presenter: http://archive.irixnet.org/siliconsurf/products/Indy/present... “When combined with an Indy workstation--
111.
by catiopatio 3y ago
I hope you won’t mind me saying so, but I’m most reminded of NeXT’s reverse-acquisition of Apple. It’s not quite as stark, but the same pattern is emerging — folks that couldn’t or wouldn’t adapt found themselves working on ever-shrinking i
112.
by catiopatio 3y ago
I live in the mountains and certainly enjoy a hot tub on a crisp, cloudless, snow-covered night. However, they’re a pain in the ass to own and maintain. Our previous rental home had one — I spent more time maintaining it than using it. When
113.
by catiopatio 3y ago
Dynamic dispatch with heavy reliance on runtime metadata is a huge attack surface in terms of being able to leverage a data bug into full control of execution. Additionally, the language provides very few runtime or static compile-time guar
114.
by catiopatio 3y ago
I cannot provide a citation for my evidence. Your citation shows the clear trend, however. Swift usage is only increasing, and Objective-C is discouraged (not deprecated, discouraged) for new projects.
115.
by catiopatio 3y ago
I said almost no new projects. It is highly discouraged.
116.
by catiopatio 3y ago
I’ve been writing software for 30 years, and have often worked on OS code bases with revision history that extends back to the 1970s. Your style of commit message is a crime against the future. It makes it impossible for a future developer
117.
by catiopatio 3y ago
Almost no new projects within Apple are written using Objective-C, and old code is actively rewritten for many reasons, with security being a large one.
118.
by catiopatio 3y ago
Commit comments are how you find code diffs. Focus on what/why in your commit messages. If you can’t articulate that in your commit messages, I can almost guarantee you’re thinking deeply enough about your code changes.
119.
by catiopatio 3y ago
I don’t recall that being the case, but my memory could be faulty. As I recall, the High Sierra Format - which served as the basis for ISO 9660 — was widely used prior to ISO 9660’s standardization and adoption.
120.
by catiopatio 3y ago
No, this is what the word has always meant. An embedded device with a failed bootloader update is considered “bricked”, even if you can open it up and reflash it with a valid bootloader. I don’t know why folks are so insistent on gatekeepi

More ›