klibertp

8 ms·

61.
by klibertp 3mo ago
The backend itself is fine, it's just trying to use JJ as a Git frontend for projects developed on Github (among 20 other devs using git, where each of them uses git through different interface and/or in different style) that&#x27
62.
by klibertp 3mo ago
IME, the only real pain point with JJ is Git integration. I love it, it's great in almost everything it does. Formalizing all the DSLs and using them consistently throughout the config and CLI is exactly how filesets, revsets, and temp
63.
by klibertp 3mo ago
Yeah. In my GToolkit setup, I started with giving it eval. At first, it tried to "rebuild the world" for each task, but we gradually settled on a set of images for specific tasks that can be rebuilt as a separate step and are othe
64.
by klibertp 3mo ago
> how relevant it was to share the same programming experience across environments. Right. If you view the language as just a part of a bigger "programming experience", you can do with a worse language with better tooling (path
65.
by klibertp 3mo ago
Depends very much on your harness and effective use of tools. For vibe-coding, stick to Python. It can get good with the right setup. I made Codex work with GToolkit (similarly underrepresented, but technically impressive and a seemingly
66.
by klibertp 3mo ago
> So why Lisp (or when) > [...] among its extensibility, its interactive environment, the REPL, and a lot of other features we haven’t touched yet. It is the combination of all of them that makes Lisp programming what it is. Agreed. H
67.
by klibertp 3mo ago
Yesterday, Codex helped me resurrect a project[1] from 2013, where the code was published, but trapped inside an exotic format that can only be read by a single application. That application had ~14 breaking releases (rewrite everything!) o
68.
by klibertp 3mo ago
I think the end goal the author describes: > I can imagine soon-to-arrive interfaces where you just drag and drop components while narrating your desires with your voice, the models able to perform the “brainstorming,” “planning,” and “w
69.
by klibertp 3mo ago
I don't think this is true. Computers are still computers, and code executes (mostly) deterministically. What computers struggle with is making sense of unclear inputs, precisely because of their determinism. OCR, speech-to-text, and c
70.
by klibertp 3mo ago
> you're going to get worse output from them Not completely true. Giving developers hardware that is too beefy is the main reason why so much software breaks down when run on users' machines, which are generally old, on spotty
71.
by klibertp 3mo ago
I came to appreciate typos, slightly ungrammatical sentences, and creative plays on common phrases. They are completely absent in LLM output without a specialized prompt (and they seem to struggle to make believable language mistakes even w
72.
by klibertp 3mo ago
There's a chance it's this: https://github.com/dhilst/algae
73.
by klibertp 3mo ago
As you note, being constrained in where you can go at level 1 is not a bad thing in itself, but it is a trade-off. Yes, as much as I personally don't mind it, I see how some players/designers might find such a limitation unfit for
74.
by klibertp 3mo ago
I hate level scaling in games with passion. An argument in favor I heard is that it's supposed to make it easier for the player to go anywhere from the start. Maybe, but coming from classic CRPGs and some TRPG background, I just can&#x
75.
by klibertp 3mo ago
> I'm not sure Gleam belongs on Wikipedia if Odin does not... They both don't belong there, TBH. I'm a PL nerd and have been one for nearly 20 years. Wikipedia is the last place I would search for information about even th
76.
by klibertp 3mo ago
> I've never heard of it before [...] but I've definitely heard plenty about Rust and c++ topics. Programming is a very broad and deep discipline. If you're a programmer for some time, chances are you know of very niche pr
77.
by klibertp 3mo ago
Steam with Proton made gaming on Linux viable. Just for that, they deserve my money. That some of it goes to game devs is a happy coincidence ;D
78.
by klibertp 3mo ago
Nice! Thank you, that explains it. FreeBSD was my first *BSD and the only one I had long-term contact with, so I unconsciously use it as my "BSD standard". My bad on that :)
79.
by klibertp 3mo ago
I'd like to know, too! DbC is an actual superpower. Coupled with a gradual type system, especially one that provides type refinements (not sure if that's a Racket-specific[1] or generic term), DbC covers a wide variety of problems
80.
by klibertp 3mo ago
I subscribe to Reuters. I've been using it as my primary source of non-tech news for the past 5 years. Compared to the Guardian or CNN, the reporting is much less subjective and less editorialized, and, outside of Breaking Views, I&#x2
81.
by klibertp 3mo ago
> wow, i guess you got hooked :-) Maybe a little :D REBOL line of languages has been on my radar for a long time - I've been a PL nerd for 20 years now - but I always found reasons not to engage with them. So it was a bit of a blind
82.
by klibertp 3mo ago
> I think GP is confused why the ftp command also handles http(s) :) Exactly - I even suspected for a second that `ftp` on NetBSD is something else entirely, not an actual FTP client with HTTP/HTTPS URLs bolted on. It's not - i
83.
by klibertp 3mo ago
Installation instructions: ftp https://raw.githubusercontent.com/segaboy/vulkan-netbsd/main/scripts/setup-env.sh !^^^^^! That's... a bit unorthodox. FreeBSD has a `fetch`[1] utility fo
84.
by klibertp 3mo ago
It looks like it works only on function bodies[1]. I'm not sure I understand why you would want to look at invoked callables code, though. Calling the same set of helper functions is already flagged; repeated code in helpers is flagged
85.
by klibertp 3mo ago
Correct me if I'm wrong, but looking at [1] it seems to be specifically using function definitions (I'm guessing this works with functions, methods, and lambdas (the "<unknown>" part)?) as units of repetition. If y
86.
by klibertp 3mo ago
I tend to follow the "rule of 3": a second similar implementation is OK, introducing the third triggers a refactor. As with everything, this isn't dogma, and sometimes the second implementation is already too much, while at o
87.
by klibertp 3mo ago
I had a bit of back-and-forth with ChatGPT about the possible implementations[1] - it shows how little I know about Red, unfortunately, but we came to this representation: shell [ var: [cmd1 arg --switch arg2] [cmd2 :v
88.
by klibertp 3mo ago
Ah, yeah, that makes sense, then. I tried writing a shell in GNU Smalltalk, but had to mess with the parser - otherwise, the need to parenthesize subexpressions makes it really tedious. I implemented |> as a pseudo-operator that implicit
89.
by klibertp 3mo ago
All that shell scripting needs is the ability to spawn processes and connect their stdin/out/err together. Or at least, that's what distinguishes "scripting" from "shell scripting". Obviously, you can writ
90.
by klibertp 3mo ago
Not sure why it wouldn't be usable for that: -▶ ./red-cli-066 --== Red 0.6.6 ==-- Type HELP for starting information. >> call/console "echo 123" 123 == 0 >> call/conso

More ›