jmb99

21 ms·

271.
by jmb99 2y ago
That is correct. I treat my 15 Pro like having a set of prime lenses at varying lengths, and so only use 0.5x (13mm), 1x (24mm), 2x (48mm, which is 12MP out of the main camera’s 48MP), or 3x (77mm). In theory, anything between 1x and 2x sho
272.
by jmb99 2y ago
Obviously anecdotal but yeah, this is by far the most durable phone I’ve owned. My 11 was the first I went caseless with, and it got pretty beat up in the first year. My 13 Pro was better, but still worse for wear after a year. The 15 Pro i
273.
by jmb99 2y ago
My phone has a couple (literal 2) scratches slightly under the notch bubble, that I am fairly certain were caused by laying the phone face-first on a desk that had some kind of dirt on it, and removing the phone by sliding it off the desk (
274.
by jmb99 2y ago
Not even just iPhones - I ran Siri on a 3rd gen iPod Touch. Anything that could run iOS 5 could use Siri with a jailbreak.
275.
by jmb99 2y ago
I’ve had the 15 Pro since launch day, and it is incredibly durable. No case, no screen protector. The screen is slightly scratched around the edges, there are a couple ~1mm^2 dings in the titanium, but aside from that, no problems. I’ve dro
276.
by jmb99 2y ago
There’s a massive difference between trusting banks (insured, backed by the state, etc) and trusting some random SaaS/web app you saw 10 minutes ago with access to said banks.
277.
by jmb99 2y ago
I don’t think “performance reviews” in the traditional sense are a silver bullet for finding the sorts of employees to invite to such a retreat. They’re good for finding “top performers” (by definition - you define what performance looks li
278.
by jmb99 2y ago
My company of ~1600 currently does annual retreats with 90-110ish people. All of the C suite and their direct reports, but also a good number of engineers and other ICs, as well as some “line-level” managers, and 10 people who have been ide
279.
by jmb99 2y ago
Parsing command line arguments, reading/manipulating binary data, memset_s are of course all available in the C standard library. I’m not familiar with rust, but if it’s true that dependencies are required for those types of basic oper
280.
by jmb99 2y ago
Both of those features have been built in to macOS for 2 decades, so in comparison, it’s quite slow.
281.
by jmb99 2y ago
Yeah, having run some state of the art obfuscated code through ChatGPT, it still fails miserably. Even what was state of the art 20 years ago it can't make heads or tails of.
282.
by jmb99 2y ago
Shares of a company are tradeable assets, no? Maybe not before the company is public depending on wording, but definitely after.
283.
by jmb99 2y ago
Ignoring the many other reasons why that would be problematic, what happens when the US government suddenly owns notable (or even controlling) stakes in companies?
284.
by jmb99 2y ago
It’s not that simple. If hundreds of billions of dollars need to be liquidated across every asset class in every industry, the entire economy is going to tank. Not just “oh no the stock market’s down.” Asset prices would drop severely (hous
285.
by jmb99 2y ago
> Idea: tax loans taken out using assets as collateral at regular income tax rates. I don’t think it’s as simple as this. This will end up catching normal people (any mortgage, automotive loan, etc) but may result in tricky accounting&#x
286.
by jmb99 2y ago
That’s a different statement. HN is awesome because of the rules and moderation =/= HN has awesome rules and moderation.
287.
by jmb99 2y ago
45 minute build for 32 million lines of code seems pretty reasonable, to me. What are some projects of equal complexity with lower build time in other languages?
288.
by jmb99 2y ago
Does iMessage not count and E2EE (with the caveat of disabling iCloud) to you? It’s available on desktop.
289.
by jmb99 2y ago
From experience, a lot of talent security people really just don’t want to be developers, even if they’re good at it. It’s not always as simple as shuffling people around between teams.
290.
by jmb99 2y ago
> There is no way to add a safety margin to code. This is, in my opinion, an incredibly naive take. There are currently decades of safety margin in basically all running code on every major OS and device, at every level of execution and
291.
by jmb99 2y ago
> so it is not just cache misses. Agreed 100%. SMT is waaaay more complex than just cache. I was just trying to illustrate in simple scenarios where increasing cache would and would not be beneficial to SMT.
292.
by jmb99 2y ago
Yeah, I don’t see how one can blame Microsoft in this scenario. If you choose to run buggy kernel-level code, that’s on you, not the publisher of the kernel/OS. Especially when the code you’re running is a replacement for functionality
293.
by jmb99 2y ago
My understanding is that a larger cache can make SMT more effective, but like usual, only in certain cases. Let’s imagine we have 8 cores with SMT, and we’re running a task that (in theory) scales roughly linearly up to 16 threads. If each
294.
by jmb99 2y ago
It’s kind of hard to pitch “zero-day prevention” if you suggest people roll out definitions slowly, over the course of days/weeks. Thus making it a lot harder to charge to the moon for your service. Now, if these sorts of things were b
295.
by jmb99 2y ago
Oh absolutely. There’s many levels of failure here. A few that I see as being likely: - Lack of testing of a deployment - Lack of required procedures to validate a deployment - Engineering management prioritizing release pace over stability
296.
by jmb99 2y ago
As always, a relevant xkcd[1]. I would not be surprised if the answer to “how many machines can be compromised in 24 hours by threatening one person” was less than 8 figures. If you can find the right person, probably 9+. [1] https:/&
297.
by jmb99 2y ago
Kind of a side talent, but I’m currently (begrudgingly) working on a project with a Fortune 20 company that involves a complicated mess of PKI management, custom (read: non-standard) certificates, a variety of management/logging/d
298.
by jmb99 2y ago
> I find it hard to believe that they didn't test it before deployment. I’m not sure why you find that hard to believe - based on the (admittedly fairly limited) evidence we have right now, it’s highly unlikely that this deployment
299.
by jmb99 2y ago
As an example to illustrate the sibling comments’ explanations: int *array = NULL int position = 0x9C int a = *(array[pos]) //equivalent to *(array + 0x9C) - dereferencing NULL+0x9C, which is just 0x9C This will segfault (or equiv
300.
by jmb99 2y ago
The failure mode here was a page fault due to an invalid definition file. That (likely) means the definition file was being used as-is without any validation, and pointers were being dereferenced based on that non-validated definition file.

More ›