joshka

30 ms·

391.
by joshka 2y ago
My point was not about "x.y.0" (I mispoke), but "x.y" (or "0.x") that causes this problem. Take a look at any random crates's cargo config, and you'll regularly see dependencies specified as "1&q
392.
by joshka 2y ago
I, a Datapoint of 1, find the functional style to generally express the ideas of what's happening to be significantly easier to grok. Particularly if intermediate variables and conversion constructors are introduced rather than relying
393.
by joshka 2y ago
There's a subtle point there though. When you rely on something that was introduced in x.y.z, stating that your version requirement is x.y.0 is an error that can easily cause downstream breakage.
394.
by joshka 2y ago
That's exactly what I was hoping would exist (thanks for posting this). I was aware of crater, but not aware of these tools.
395.
by joshka 2y ago
When thinking about building something like this sort of device (but on a lesser scale), I've often considered how it stacks up to something like just grabbing an old second-hand iPad. For about the same price you can grab a 2017-19 or
396.
by joshka 2y ago
To clarify this a bit: 1. The widely used Time crate had some code which converted to an unspecified type. The code then converted this again in a following line. Because there was only a single possible (identity) conversion, this code was
397.
by joshka 2y ago
> This PR seems relevant... It's not. The change doesn't have anything to do with the prelude. It was a new conversion was added, where existing code made an assumption that there was only one possible conversion that satisfied
398.
by joshka 2y ago
Meta rules that are often ignored: 1. Establish what is good enough 2. Measure, don't guess 3. Fix the biggest bottleneck first 4. Measure after fixing And some general things: 5. Avoid micro-benchmarks (i.e. things not at the entire s
399.
by joshka 2y ago
I'd like to suggest adding an example of the output before the install instructions. Show don't tell...
400.
by joshka 2y ago
If you have write access a path like C:\Windows\System32\drivers\CrowdStrike\ (and I'd assume the parent directory), then you pretty much can crash the kernel many ways. If you have the means to insert an AV config file update in betwe
401.
by joshka 2y ago
> I actually don't think it's outrageous that these files are rolled out globally, simultaneously. Anyone competent that manages software at scale should generally hold the opposite opinion to this.
402.
by joshka 2y ago
Then ask for an email address for that purpose... in your app... for your app...
403.
by joshka 2y ago
Please don't request email address when authorizing using github auth. This invariably leads to spam, either intentionally, or accidentally when services don't guard their database / email sending. Instead make this optional
404.
by joshka 2y ago
The way I look at async in this case is that it kind of does the opposite of the inversion of control (in the original sense[1], not the Java/C# IoC container sense) that you're doing here. Your approach replaces a linear method w
405.
by joshka 2y ago
Got it - thanks for the update. I'll take a run at it sometime - if only to understand where the pain points in doing this are more thoroughly.
406.
by joshka 2y ago
+1 to everything here. TL;DR: predictable > most things The development container idea however is useful when you're dealing with any type of distributed system as it allows you to develop against a known setup of those things (e.g.
407.
by joshka 2y ago
Agreed with this pretty much 100%. I'd add to the list: - oh my zsh git shortcuts are great - git-extras (especially git-brv for when you're an open source library maintainer) - pushing to PR submitter's branches to clean up
408.
by joshka 2y ago
I'd replace that with giving someone a link to Git Fix Um[1] [1]: https://sukima.github.io/GitFixUm/
409.
by joshka 2y ago
> This isn't an adequat comparison in my eyes. Your example moves a very critical component out if the "protocol logic": message parsing. (for context in case you didn't see the link in the other comments - https:&#x
410.
by joshka 2y ago
yep - color_eyre is a better anyhow (and there's plans afoot to merge them into just one at some point[1]). Miette occupies a space that I generally don't need (except when processing data), while color-eyre is in the goldilocks z
411.
by joshka 2y ago
https://news.ycombinator.com/item?id=40879547 async fn stun( server: SocketAddr, mut socket: impl Sink<(BindingRequest, SocketAddr), Error = color_eyre::Report> + Stream<Item = Res
412.
by joshka 2y ago
The Stun protocol is surprisingly easy to implement, but see my comment at https://news.ycombinator.com/item?id=40879547 about why I'd just use async instead of making my own event loop system. https://gist.
413.
by joshka 2y ago
This article / idea really refactors two things out of some IO code - the event loop - the state machine of data states that occur But async rust is already a state machine, so the stun binding could be expressed as a 3 line async func
414.
by joshka 2y ago
If you want a web protocol, try oauth2. There's complexity in the number of things you can support, but in essence there's a state machine that can be modeled.
415.
by joshka 2y ago
I see what you mean about the squashed commits now. I've updated the template we're using to make this a little nicer now - https://github.com/ratatui-org/ratatui/blob/5e7fbe8c328050a2... (from an i
416.
by joshka 2y ago
> It looks like the commits are lightly processed (scanning “type”, removing it, moving it to the correct section/heading), put in bullet points, adding a hyperlink to the commit hash, using section breaks for something (maybe per P
417.
by joshka 2y ago
Yes. See https://github.com/ratatui-org/ratatui/blob/main/cliff.toml#...
418.
by joshka 2y ago
yes and yes
419.
by joshka 2y ago
If I was getting spam from devs to fix a thing in a library like this, my response would be "sure, here's my rate $/h". This seems like a pretty fair put up or shut up response. The underlying issue here is that there ar
420.
by joshka 2y ago
Here's an example of a changelog that is generated using git-cliff: https://github.com/ratatui-org/ratatui/blob/main/CHANGELOG.m... The things that make this work well for us are - We make sure we d

More ›