Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Orphis
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
by
Orphis
10d ago
There's also a chance the people claiming to do clean room are cheating and took some shortcuts. It's easy to make random claims that are impossible to prove or disprove.
2.
▲
by
Orphis
10d ago
They could claim that some employee one day used their model to ask a question about internal stuff and they trained on that. It doesn't have to necessarily have to make sense to make a claim, but it doesn't necessarily bear any w
3.
▲
by
Orphis
10d ago
If using the OpenAI models to develop this taints you with Apple insider knowledge, then so is developing any macOS, iOS, Android or Windows apps around that are using any LLM. You can't claim that some work is necessarily tainted by e
4.
▲
by
Orphis
10d ago
There's also been Wii games rereleased on PC with all debug symbols that cover the Wii parts that were still compiled in. You'd get mostly type names, enums, object layouts and function signatures that way.
5.
▲
by
Orphis
1mo ago
The Juniors are also very good with AI. Having them merge bad commits into logical ones is a fine operation for them too.
6.
▲
by
Orphis
1mo ago
People say they care about the "story" behind the PR. But no one cares about that story if it's about forgetting to fix a test and a typo in a comment. The extra commits are just noise that make you think the original commit
7.
▲
by
Orphis
1mo ago
Thinner modular systems also require some good tooling and a good platform that ensures many security properties. You will be trading a stable and vetted huge standard library for 200 small packages that may all be targets for supply-chain
8.
▲
by
Orphis
1mo ago
C++ ended up in that situation because they don't want to break backwards compatibility (ABI, API) or change contracts, except in some rare cases, even on major releases. Quite often, it is a vendor issue to break the ABI and fix issue
9.
▲
by
Orphis
1mo ago
You mostly hear about the bad ones. Mine has been doing great for almost 2 years now. I use it in a clean environment, I'm very careful and not clumsy, so that helps.
10.
▲
by
Orphis
1mo ago
It's not that noticeable when you use the device. It will depend on your ambient lights usually and how you hold it. It's a lot easier to see when someone else is holding the phone too, so if that was your reference, you may want
11.
▲
by
Orphis
1mo ago
I think the clumsiness can be improved. I always make a conscious effort when I grab my phone or put it away, so that is is always secure. No "I thought it slid into my pocket but apparently it was still outside it and then dropped&quo
12.
▲
by
Orphis
1mo ago
Turns into a small tablet which is great for reading, for impromptu client demos, and for playing some games like puzzles. It also enables multitasking by having applications side by side which can be very useful on a phone too. You don
13.
▲
by
Orphis
1mo ago
And mine is almost 2 years old and in great condition. It's hard to know what is responsible in those cases, a manufacturing defect or a rough user. And knowing what I've seen people do with their non-foldable phone, I'm not
14.
▲
by
Orphis
2mo ago
Practice helps! What also helped me is being so knowledgeable about the topic that I didn't need to prepare the presentation much (except for the slides and the general plan). When you know what you have to talk about, it becomes a lot
15.
▲
by
Orphis
2mo ago
Curious, Windows is not supported by this.
16.
▲
by
Orphis
2mo ago
Ultrawide curved are amazing. Put your main activity in the middle since there's no screen bezel and enjoy your neck-pain-free work hours. 2 monitors force you to usually have one on the left, one on the right and always face your head
17.
▲
by
Orphis
2mo ago
Why not just embrace Content Based Addressing and the Bazel action cache? Not necessarily adopt the RBE protos, but you could have on-disk cache that are similar or even identical. Nowadays, I think a build tool that doesn't natively s
18.
▲
by
Orphis
2mo ago
This is not purely a CMake problem, this is a maintainer problem. It's absolutely possible to not define the man page targets if the related tools are not found, or to add a variable to disable that. In practice, it does show the limit
19.
▲
by
Orphis
2mo ago
Xerces is an old library, probably ported from autotools and will do a lot of autotools like checks which for CMake means: creating a CMake project with the probe, generating the build files from it, building it, gathering results. Once for
20.
▲
by
Orphis
2mo ago
> I want the build stages to communicate in one direction for sanity That's easy to do if you control the whole pipeline and can integrate all the features together, not so much with the CMake model unfortunately. I think it would b
21.
▲
by
Orphis
2mo ago
Simple CMake projects using the Ninja generator are very efficient, unless you create generated files. And if they are in their own targets, they are not really an issue (they would serialize everything that depends on them as you'd ex
22.
▲
by
Orphis
2mo ago
Last time I checked (a while ago), it wasn't. You needed to compile musl and exclude a few files from the archive to then provide your own allocator. Depending on the toolchain, I'm assuming you could use some tricks or hacks to m
23.
▲
by
Orphis
2mo ago
That's to be properly measured. Assuming that the allocator will not cause issues there is to be proven. The application I recently improved by changing the allocator had a similar profile (a C++ include scanner) and thread parallel I&
24.
▲
by
Orphis
2mo ago
ripgrep is there to be FAST. Trading any speed to improve memory efficiency over a longer period of time for a process with a short life-time doesn't make sense in this case. It's also a development tool. If your development machi
25.
▲
by
Orphis
2mo ago
That's good! But I wonder why it wasn't then enabled for that configuration or why the override wasn't "global" enough and the default allocator was still partly used.
26.
▲
by
Orphis
2mo ago
Sure, but the problem isn't that the bug exists, is that it has surfaced in a performance application using musl and exerting code paths in a slow allocator. mallocng should not be used at all.
27.
▲
by
Orphis
2mo ago
I get why people don't bother replacing the default allocator from musl all the time (it's there, convenient). But in an application whose purpose is to be FAST, I find it weird they haven't bothered replacing it with another
28.
▲
by
Orphis
2mo ago
Chrome uses those already, and a few other pointer types that are fit for purpose. For example, lot of C++ objects are tied to a garbage collected object in JS, so you need something special to hold a reference in C++ code to those, and pre
29.
▲
by
Orphis
2mo ago
They did roll this policy for Chromium changes a few years ago too. And it wasn't just 2 humans but 2 Googlers. One Googler author and one Googler reviewer works. But an external author needed 2 Googlers to review changes, and all file
30.
▲
by
Orphis
2mo ago
Old bugs at the bottom of the prioritization list deserve to be fixed. Some were probably just theoretical "if we have over 2B of this item, it'll crash because X/Y/Z and that can be exploited", some are probably in
More ›