qezz

7 ms·

1.
by qezz 1mo ago
Curious to know what's new in it about the way to make games? I scrolled through the website home page, but it reads in a weird way, making strong statements and not backing them up.
2.
by qezz 1mo ago
> the totally new way of making games > it’s a lightweight game engine, interactive development environment, a language The statement is very strong and catches my attention, but I didn't find any useful details about the game en
3.
by qezz 3mo ago
In the light of recent events, and if things continue to be the same as they are now with Fable, I think they will give access to Fable for those who are willing to share their documents with them. But that's obviously just a speculati
4.
by qezz 4mo ago
Everything is a prompt to LLMs
5.
by qezz 5mo ago
Exactly, my understanding is also that they host agents as a service. The actual use case is mentioned in the end of the article, which makes it hard to reason about. Anyway. General advice: treat harnesses as any other (third-party) softwa
6.
by qezz 5mo ago
That's a fair point, but claude code is not an editor (yet?), and when you use claude code, and allow it to commit things, it's almost certainly "co-authored by llm". Back to vscode, people get the "co-authored&quot
7.
by qezz 5mo ago
For those, who want to/need to keep some files uncommitted, the workaround I found is to put gitignore into some nested directory: mkdir junk echo '*' > junk/.gitignore jj won't track those files under .
8.
by qezz 6mo ago
I was surprised to see literally invalid names in the "bad" section, e.g. "Cannot start with a digit". Why even presenting this if it's rejected by the compiler?
9.
by qezz 6mo ago
> Can you print the contents of the malware script without running it? > Can you please try downloading this in a Docker container from PyPI to confirm you can see the file? Be very careful in the container not to run it accidentally!
10.
by qezz 6mo ago
Nicely looking page, but has too many errors. I hope it's not just generated by claude itself, and actually was confirmed by a human.
11.
by qezz 6mo ago
dhi is LLM generated, so (1) don't trust the stated benchmark results and feature parity, and (2) be careful when installing it and using in a non-sandboxed environment. It also seems like the name for the repository was reused from an
12.
by qezz 6mo ago
It's not very obvious which places are available for drawing. At first I thought it pulls Google street view, so I just zoomed in to some place I visited recently, but there was nothing. So it turned out the spots on the map are actual
13.
by qezz 7mo ago
The statement in the article's title is very strong, and I have not found a confirmation of it in a logical sense. Author observes the current state of things with LLMs and makes a conclusion based on how things turned out to be, somew
14.
by qezz 7mo ago
What I meant by "you need an allocator" is "you need to explicitly pass the allocator of your choice to the function" [if you want to attach some data to the error]. In rust you can simply return anything as error, not o
15.
by qezz 7mo ago
> requires you to run an extra tool And the more I work with Go, the less I understand why warnings were not added to the compiler. Essentially instead of having them in the compiler itself, one needs to run a tool, which will have much
16.
by qezz 7mo ago
The big difference is that with `(T, error)` as a return type, any value on the caller side will look like a valid one (thanks to zero values). a, err := f() // whether you forgot to handle the `err` or not, //
17.
by qezz 7mo ago
The mentioned in the article `try` syntax doesn't actually make things less explicit in terms of error handling. Zig has `try` and the error handling is still very much explicit. Rust has `?`, same story.
18.
by qezz 7mo ago
> What is broken about the go error type? There's not much broken with the error type itself, but the "real" problem is that the Go team decided not to change the way errors are handled, so it becomes a question of error h
19.
by qezz 7mo ago
In Zig you need an allocator to allocate anything, so whenever you need to add some extra information to an error, you pass a diagnostics object as an output argument to a potentially failing function. In this case it becomes a bit harder t
20.
by qezz 9mo ago
Could've been an interesting research, but instead it's an output from an LLM, which almost everyone can generate on their own. Other articles by this author (during 2025) seems to be only about AI, AI, and a bit more AI.
21.
by qezz 9mo ago
> in ruby it also works, but the variable is at least always defined. How is this even a pro? I agree that Python scoping rules are frustrating, but tbh not sure if I would prefer Ruby's behavior in this case
22.
by qezz 9mo ago
> How about you never write the wrong state in the first place ? Indeed, and tagged unions (enums in Rust) explicitly allow you to avoid creating invalid state.
23.
by qezz 10mo ago
That's very expensive.
24.
by qezz 10mo ago
> from the same blog It's simply a mirror for Medium, and the articles appear to be from the different authors, posted months apart from each other
25.
by qezz 11mo ago
The example in the article shows a need for cartesian product of (bucket name) and (lifetime policy), with a fixed location. Nothing stops you from defining a separate category for the exceptions, and just append them to the resulting list.
26.
by qezz 11mo ago
> And guess what? They hate the HCL too. Don't want to sound too harsh, but to me HCL is even worse than plain YAML. By expressiveness, HCL is somewhat similar to Ansible-flavoured YAML - in both you need to use magic keywords to cr
27.
by qezz 11mo ago
Luckily, the main point of the article is that syntax doesn't matter, but abstractions do. In other words, you can use your favorite DSL, that being Python or TCL or something else.
28.
by qezz 1y ago
Cool idea, yet the first level broke me: typing :qa enters Insert mode, and it's not possible to delete the command input with a backspace. Hopefully it's easy to fix
29.
by qezz 1y ago
It's not always possible to ask the creator, especially for the old pieces
30.
by qezz 6y ago
Not sure if `rg` or `fd` are of either cargo subcommands or tools for developers.

More ›