nixpulvis

7 ms·

91.
by nixpulvis 7mo ago
I don't think explicit naming of impls is wise. They will regularly be TraitImpl or similar and add no real value. If you want to distinguish traits, perhaps force them to be within separate modules and use mod_a::mod_b::<Trait for
92.
by nixpulvis 7mo ago
I mean, macOS supports tabs now. I wouldn't call it "good" though.
93.
by nixpulvis 7mo ago
It's comical how much time I've spent convincing people that tabs are a window manager feature not an application feature. People in the Alacritty issue on the subject were pissed!
94.
by nixpulvis 7mo ago
Not technically under the umbrella of Apple Intelligence, but you might be surprised to find out what photoanalysisd is doing.
95.
by nixpulvis 7mo ago
Yes, that's my point though. It's not about being built into the OS, it's about being controllable.
96.
by nixpulvis 7mo ago
Yea I respect that. I too would not want any unprompted access to my files. At the end of the day this issue is that we don't trust the OS and we cannot easily validate how it is designed to behave.
97.
by nixpulvis 7mo ago
So the issue isn't actually that it's baked into the OS, it's that you should have control over when it's used.
98.
by nixpulvis 7mo ago
So Apple Intelligence doesn't bother you?
99.
by nixpulvis 7mo ago
I never want to read another Bean or log4j config ever again.
100.
by nixpulvis 7mo ago
Agreed. It's clear to me as a more seasoned engineer that I can prompt the LLM to do what I want (more or less) and it will catch generally small errors in my approach before I spend time trying them. I don't often feel like I end
101.
by nixpulvis 7mo ago
A junior engineer who might spend a few hours trying to understand why you added a mutex, reading blogs on common patterns, might come back with a question about why you locked it twice in one thread in some case you didn't consider. J
102.
by nixpulvis 7mo ago
That's actually one of the best parts. You can trust some of the context you have loaded is side loaded in the LLM, making task switching feel less risky and often improving your ability to work on needed and/or related changes el
103.
by nixpulvis 7mo ago
Is the non-local reasoning here a limitation of Rust, async Rust, or the libraries built around async Rust?
104.
by nixpulvis 7mo ago
I don't even think there is a sound notion of "sanitization" when it comes to LLM input from malicious actors.
105.
by nixpulvis 8mo ago
Isn't it nice to have a USB-C port and then use the back panel inductive charging for this? I don't see why I would want magsafe on my phone at this point.
106.
by nixpulvis 8mo ago
To be clear. Proper 2FA, via something like a smartcard or any truly external device is still much more secure. You could have one of those factors be a passkey, that's fine, and may be a good idea. But there are UX issues with passkey
107.
by nixpulvis 8mo ago
Those deep pockets are funded by the same pot we all feed from.
108.
by nixpulvis 8mo ago
This works if there's no cost of failure in the meantime. If we're putting humans into rockets into space, I'd like to think we adopt a balanced approach.
109.
by nixpulvis 8mo ago
IIUC the issue is, you could have a "secure" network and a guest network sharing an AP, and that guest network can access clients on the secure network. Someone did mention the xfinity automatic guest network, which might be a pai
110.
by nixpulvis 8mo ago
An external firewall with strict no WAN access would be smart regardless.
111.
by nixpulvis 8mo ago
I still haven't used a system as nice as Ruby on Rails and Heroku circa 2014.
112.
by nixpulvis 8mo ago
You sly dog.
113.
by nixpulvis 8mo ago
Incorrect.
114.
by nixpulvis 8mo ago
I didn't say all language is planned and agreed on. But we absolutely do plan and agree on things.
115.
by nixpulvis 8mo ago
That's a terribly nihilistic outlook on language. We agree to meaning to communicate and progress without endless debate and confusion. SI is pretty clear for a reason.
116.
by nixpulvis 8mo ago
Exactly. If you're talking loosely, then you can get away with it.
117.
by nixpulvis 8mo ago
They should be more precise if they are talking about KiB in a context where the difference matters... luckily those contexts are usually written down.
118.
by nixpulvis 8mo ago
Yea I don't understand the issue here. SI is pretty clear, and this post explains the other standard a little bit. It's really not all that crazy of a situation. What bothers me is when some applications call KiB KB, because they
119.
by nixpulvis 9mo ago
> Swift takes Rust’s ideas and hides them in C-like syntax. This example doesn't show me any meaningful difference, and Rust also let's you attach functionality to enums.
120.
by nixpulvis 9mo ago
Knowledge that the ACA is Obamacare is my litmus test for basic healthy civic engagement.

More ›