carlosneves
Joined 6 years ago
Karma
21
Submissions
26
Member since
Apr 24
Recent submissions
Comment · 2 months ago
Comment · 2 months ago
That's exactly the situation I'm in... :crying-laughing:
The fix is merged, but won't deploy... it's been hours
Thankfully it's a batch job, and isn't interrupting production ATM
Comment · 3 months ago
Thanks for linking to Fexpr's. I've thinking about "functions with lazily evaluated arguments" recently, and trying to understand how they are different from macros. So I was basically thinking about fexprs.
I have some reading to do, but overall it seems like macros are favored instead of fexprs. Macros completely avoid some environment handling issues.
Comment · 7 months ago
An `--ignore-file=` flag would be nice I guess:
--ignore-file=.ignore
--ignore-file=.gitignore
--ignore-file=.dockerignore
--ignore-file=.npmignore
etc
but then, assuming all those share the same "ignore file syntax/grammar"...
Comment · 7 months ago
This concept of "machine worship" reminds me of E. M. Forster's The Machine Stops.
Is it possible for a tech-oriented ideal to escape "machine worship"?
As we strive to refine our "machines" ever further, and our "machines" become ever more capable, where does that lead us?
Comment · 9 months ago
Comment · 10 months ago
You can always ask it to nudge you in the right direction instead of giving the solution right away. I suspect this way of using it is not very popular though.
This is not a new problem I think. How do you use Google, translator, (even dictionaries!), etc without "degenerating" your own abilities?
If you're not careful and always rely on them as a crutch, they'll remain just that; without actually "incrementing" you.
I think this is a very good question. How should we actually be using our tools such that we're not degenerating, but growing instead?
Comment · 11 months ago
And oftentimes some endpoints simply hit the max URL length limit and need a proper body.
I thought we ought to already be using this method. Seems quite fitting for fulfilling GETs with bodies.
Comment · 1 year ago
I was going to say that. Gratitude to the creators of fish shell. The history-based rank is immediate as you type. Lately I've simply done:
abbr --add c cd
And then the "most used paths" are just present in the history filtered by the prefix I already typed.
Comment · 1 year ago
For awareness, if you want to build a SSG/SSR frontend, there's also [Astro](https://astro.build/)
It lets you ship client islands to the client, which AFAIK is essentially partial hydration.
Comment · 1 year ago
> When using npm, all dependencies for a project are installed in a single node_modules directory. This means that if two packages depend on different versions of the same package, the one that is installed last will be used, which can lead to compatibility issues. This is known as "dependency hell" and can make it difficult to manage the dependencies of a project.
> pnpm's symlink feature addresses this problem by allowing different versions of the same package to be installed side-by-side, and linking them to their dependents through symlinks. This helps to ensure that the correct version of a package is used for each dependent, reducing the chances of compatibility issues and making it easier to manage dependencies.
From the last issue linked in the PR (https://github.com/oven-sh/bun/issues/1760)
Comment · 1 year ago
Empty is not the same as succinct & straight to the points. I'd say strong title, succint content. Each of the points invites as much thought as you can give it.
Comment · 1 year ago
I think he's proposing a fix for the regex in the title.
/(ab?)using/ matches:
- ausing
- abusing
while /(ab)?using/ matches:
- using
- abusing
The downside compared to macros I think is that, as argument expressions become lambdas, it becomes harder to manipulate them. Check the cond example which needs two fexprs, whereas one macro could do it.
Not sure about D, but if it were lisp, even lambdas could be manipulated as lists. Macro args not having the lambda wrapping just seems simpler.
[1] https://en.wikipedia.org/wiki/Fexpr