K0nserv

12 ms·

181.
by K0nserv 2y ago
Only if you remember, which you, or someone else, is bound to not eventually
182.
by K0nserv 2y ago
The overarching lesson of my career has been that people are fallible and processes that rely on humans to not make mistakes are bound to fail. Recently I've also been thinking about the importance of being able to reason "locally
183.
by K0nserv 2y ago
Or just don't use a photo at all if it doesn't add something substantial. A nice photo from Unsplashed is much better than AI slop, but it's often largely superfluous.
184.
by K0nserv 2y ago
This is focused on people whose job it is to write documentation, but I think it applies generally. A previous company I worked at moved away from Read The Docs to Confluence and it was terrible. This decision was resisted by much of engine
185.
by K0nserv 2y ago
The thing about state is a good point. With the sans-IO pattern we have inversion of IO and Time, but adding memory to that would be a nice improvement too.
186.
by K0nserv 2y ago
Yes true, the one difference might be that you don't expect other consumers with a different approach to IO to use your internal libraries, although it does help you if you want to change that in the future and the testability is still
187.
by K0nserv 2y ago
The big thing, in the context of Rust, I think is how this solves function colouring, but it also makes testing really simple as outlined in the post. The current situation in Rust is that if you implement a library, say one that does WebRT
188.
by K0nserv 2y ago
For 4 you can implement that with a channel passed along with the message to send a result back. You can then block the sending side all the way to the callsite if you wish. My feeling is that sans-IO is particularly useful for libraries, a
189.
by K0nserv 2y ago
I do this too, barcelonaairportwifi@<domain> is a prime offender and gets a lot of spam. I've also taken to using Fastmail's masked email support along the 1Password integration for the same.
190.
by K0nserv 2y ago
Maybe this tax is not good, it feels a bit too specific to me. However, if every country and leader took your position, actually tackling climate change would be hopeless, maybe it is.
191.
by K0nserv 2y ago
I'm not a climate scientist, presumably the Danish government has consulted some of those though. My understanding is that livestock farming, in particularly beef and dairy cows, contribute significantly to the Co2e(carbon dioxide equi
192.
by K0nserv 2y ago
Yes of course, it's pricing in a negative externality that was previously not accounted for.
193.
by K0nserv 2y ago
This looks really cool. I wanted to try it, but it seems that version 0.53.0, which adds --tail, is not yet available via Homebrew.
194.
by K0nserv 2y ago
I analysed[0] many apps on the App Store when Apple started forcing app authors to disclose their use of data, at the time nine apps collected audio in a context that could be construed to mean use for ad targeting. It’s been four years so
195.
by K0nserv 2y ago
> Seems like the wrong problem to solve. "Systems programming" is hard, and should be hard, for reasons unrelated to the programming language used. Something like Rust which forces you to constantly reevaluate your design befor
196.
by K0nserv 2y ago
I definitely went on this journey with my running. At first I would run very short distances at very high pace(zone 4/5), but I fell out of it. I picked up running again last year and ended up more in zone 3/4, but for the last si
197.
by K0nserv 2y ago
Right you are! I guess I'm one of today's 10000
198.
by K0nserv 2y ago
Thanks! I totally missed that
199.
by K0nserv 2y ago
This site should really include Mozilla's position on the spec too. Google shipping some, potentially harebrained, idea in Chromium doesn't mean that Safari and Firefox MUST also ship it. There should be links to relevant entries
200.
by K0nserv 3y ago
That would be true if you used `Vec::clear` too, it doesn't allocate a new vector. My point was that you still end up running Drop implementations with RepeatedField<T>, just not all at once. See https://play.rust-lang
201.
by K0nserv 3y ago
About step 2: You still need to drop items, that's required for Vec<T> to be sound. By not calling `Vec::clear` and instead using pub struct RepeatedField<T> { vec: Vec<T>, len: usize, } w
202.
by K0nserv 3y ago
Risky Business is a fantastic podcast in general, well worth listening to weekly if you are interested in infosec.
203.
by K0nserv 3y ago
It's been a while since my Haskell days, but I think the key difference is whether you are abstracting over the IO or if the IO sits outside the pure code entirely When you abstract over IO you have blue(pure code) that contains generi
204.
by K0nserv 3y ago
No problem, here are some examples of it: * Quinn(A QUIC implementation, in particular `quinn-proto` is sans-IO, whereas the outer crate, `quinn`, is Tokio-based)[0) * str0m(A WebRTC implementation that I work on, it's an alternative t
205.
by K0nserv 3y ago
I agree with your diagnosis. It's what I concluded in my own Rust async blog post[0](which surely are mandatory now). It's even worse than bifurcating the ecosystem because even within async code it's almost always closely ti
206.
by K0nserv 3y ago
I'd think so too, but the number of implementations that use dark patterns that make it more difficult to reject consent than accept it seems to indicate they aren't erring on the side of caution. I'm not talking just de-emph
207.
by K0nserv 3y ago
> Even worse, this thread is full of armchair lawyers that will confidently tell you there's no need for cookie banners in particular cases. Nevermind that there's hardly any case law about this and each country seems to interp
208.
by K0nserv 3y ago
I wrote something elsewhere in the thread about this[0]. I don't think laws mandating specifics of implementations at the level of browser settings is a good idea. To your point about government employees not being competent I don&#x27
209.
by K0nserv 3y ago
This doesn't require a specific implementation just that informed consent is given. This could be implemented as a web standard alá Apple's ATT(App Tracking Transparency). There's nothing preventing the industry from creating
210.
On Async Rust(hugotunius.se)
1 points by K0nserv 3y ago|0 comments

More ›