epage

31 ms·

331.
by epage 4y ago
I've been evaluating different languages for writing plugins and TCL really seems tempting. Unfortunately, I've been leaning towards Lua just due to its pervasiveness (today). I also vaguely remember one of the top contenders ha
332.
by epage 4y ago
While tools like Github check for patch conflicts, they don't check for semantic conflicts (e.g. one PR adds a new use of a function another PR removes). This is where merge queues come into play which have a variety of names (merge qu
333.
by epage 4y ago
I found this part odd > . If YJIT is built in dev mode, then cargo is used to fetch development dependencies, but when building in release, cargo is not required, only rustc I'm not finding any information on why they bypass cargo a
334.
by epage 5y ago
It means they haven't (yet?) transitioned to open-first and it'll require proving themselves that they'll do open-first development before trusting them. Not willing to bet my work on a product where the governance isn'
335.
by epage 5y ago
A bit skeptical when there are relatively recent commits like > Re-sync with internal repository
336.
by epage 5y ago
I miss its version of blame (time-lapse view) and wish there was a git gui that matched it.
337.
by epage 5y ago
Tried Bluey? I describe it as a positive family sitcom. There are lessons to the episodes but they do a great job integrating them into the stories. I enjoy watching it on my own. Unfortunately, only Season 1 is on DVD in the US. If you
338.
by epage 5y ago
I have a bad taste in my mouth or the phrase because I saw someone wielding it as a weapon at others. Its been a few years, so I don't quite remember the details unfortunately. The funny part is the person wielding it was playing pol
339.
by epage 5y ago
> Dev/CI drift: instead of writing the same automation twice - once in a CI-specific configuration, and again in a Docker compose file, shell script or Makefile - simply write a Dagger plan once, then run it in all environments. Wor
340.
by epage 5y ago
Before CI became prevalent, I was against checked-in code generation and it took me a while to unprogram that bias and re-evaluate. Its been a big help in keeping runtimes fast with a python program at a previous job and at keeping build-t
341.
by epage 5y ago
> Not speaking ill of the dead is morally wrong. Maybe just me but I feel like this misses what Speaker For the Dead does. It isn't about speaking ill or not ill of people but understanding their life experience, to give context to
342.
by epage 5y ago
As another former p4 user, know of any git tool that provides anything like p4's blame viewer (was it called "time-lapse view"?)?
343.
by epage 5y ago
Really glad to see this! Really want an easy way to render graphs in Rust without resorting to the graphiz binary. What is the current status? Not seeing it listed anywhere, like if there are features that are not supported or if it uses c
344.
by epage 5y ago
I'd recommend checking out the API Guidelines for some thoughts on this. The default recommendation if you don't have another preference is MIT + Apache 2.0 https://rust-lang.github.io/api-guidelines/necessit
345.
by epage 5y ago
Something Nix seriously needs is a searchable index of people's nix configs. When I attempted to use it, I had tabs open for around 10 configs that I was cross referencing but I can't find that list of configs anymore and I have m
346.
by epage 5y ago
There is a tension between digestable changes and context to understand why a change exists. I wish review tools handled multi-commit and stacked PRs better (Phab has its share of problems).
347.
by epage 5y ago
Checkout https://github.com/gitext-rs/git-stack/blob/main/docs/compar... (note, the tool hosting this page is not included but as the author). As the author of git stack, with all relevant biases, I
348.
by epage 5y ago
> The number one problem Rust has now is that it’s overall not significantly better than C++ and sometimes the reverse is true. Maybe we are coming at this from different angles but I disagree. I remember seeing some discussions in the C
349.
by epage 5y ago
For me, the reason I like an explicit `.iter()` is because its more refactor-friendly. If I have an existing loop over `&collection` but want to call an iterator method, I have to switch to `collection.iter().enumerate()`.
350.
by epage 5y ago
> Every file in the tests directory is a separate crate, compiled to its own executable. This is a reasonable decision, with undesirable consequences: Other problems with this: - You have to link each test file which can be slow - You ge
351.
by epage 5y ago
For me, Serious Sam captured some of what I enjoyed about Doom 2.
352.
by epage 5y ago
> If he has free time, why doesnt he finish those instead of writing new books?? Something he has spoken of in the past is he if dropped his side projects, like people sometimes ask, his output is likely to go down because these project
353.
by epage 5y ago
> Another nail in the coffin of the traditional "publishing industry" too. Expecting to see "edited and produced by" credits in books soon, and to pay attention to the names of those as much as the authors. I think Sc
354.
by epage 5y ago
Rust uses it and so has become a default license for Rust crates. See https://rust-lang.github.io/api-guidelines/necessities.html#...
355.
by epage 5y ago
I've not been able to get my credit report because of something incorrect in my credit report that they were asking me to verify...
356.
by epage 5y ago
Generally, they haven't. The most I've seen is using pre-release to communicate between teams when a shared dependency is ready to ship. In the Rust community, there is tooling and culture around Major that we pay attention to th
357.
by epage 5y ago
I feel minor vs patch is useful for communicating and for the psychological effect. Most people won't care about adding a stray function for one person. Major new functionality is different. Yes, this mixes "sentimental versioning
358.
by epage 5y ago
For me, semver isn't perfect but its good enough. At least for my experience in the Rust community: - You can trust people to not break things. For the unsusual cases, people are quick to respond by yanking. - Once people hit 1.0, they
359.
by epage 5y ago
I wanted to keep the focus on the idea and not have this be viewed as an attack on the person. However, the person has gone on to more publicly talk about their views (the linked users post) so its more clear who I was responding to so I&#x
360.
by epage 5y ago
I've traditionally done the same out of laziness. `cargo add` being merged into cargo (soon) will remove some of that laziness. This does make me interested in adjusting `-Z minimal-versions` to get it useful. The biggest problem is de

More ›