YorickPeterse

7 ms·

61.
by YorickPeterse 2y ago
Not quite. A borrow doesn't do cleanup because it's, well, a borrow, i.e. a temporary reference to some owned value. It's the owned value that's tasked with disposing of any resources/memory when it goes out of scop
62.
by YorickPeterse 2y ago
In Inko a borrow is sort of a hybrid in that it does increment a counter, but there's no shared ownership like there is in traditional reference counting (e.g. a borrow is never tasked with cleaning up data). Terminology is a bit annoy
63.
by YorickPeterse 2y ago
On the diagnostics side of things, the compiler produces these in two places: 1. If you try to define a `mut` field (= one you can normally assign a new value), it will produce an error at the definition site 2. If you try to do something l
64.
by YorickPeterse 2y ago
Although linear typing is certainly interesting, I think linear typing on its own is not enough. That is, you basically end up with something like Austral where you use linear types _plus_ some form of compile-time borrow checking, at which
65.
The Inevitability of the Borrow Checker(yorickpeterse.com)
3 points by YorickPeterse 2y ago|0 comments
66.
by YorickPeterse 2y ago
This sounds like an issue with your environment. For example, on my Fedora 41 setup Ghostty starts up pretty much instantly regardless of the value of this option.
67.
by YorickPeterse 2y ago
My `~/.var/app` directory is 14 GiB in size, 12 GiB of which is used by Signal (which is mostly photos and videos) and 1.8 GiB by Firefox. All other programs only take up a few MiB of space. In terms of installation size it's
68.
by YorickPeterse 2y ago
Both you and sgarland are missing the point here: the example I gave is literally just that: an example. There could be many more complex cases, some relying on other business logic provided by your application, some more isolated. Some of
69.
by YorickPeterse 2y ago
> Disagree. SQL is a declarative language that is both clear and universal. Feel free to generate the migrations however you’d like, but I want to see the SQL. This works until you need something beyond the trivial "UPDATE table SET
70.
by YorickPeterse 2y ago
If you enjoy maintaining 5 different formats of the same data, then by all means use a document storage DB. But at some point you'll have to migrate the data, at which point you'll face the same issues (or possibly worse due to th
71.
by YorickPeterse 2y ago
Good point, I forgot about tunability. At GitLab we did have a mechanism for this for background migrations, IIRC it looked at the vacuuming statistics of PostgreSQL and would back off if it deemed there was too much load.
72.
by YorickPeterse 2y ago
I hadn't heard of Liquibase until now. Taking a brief look, it doesn't seem like it would be suitable though. For large scale migrations you really need to be able to express arbitrary logic ("migrate A to B but only if file
73.
Building a better and scalable system for data migrations(yorickpeterse.com)
68 points by YorickPeterse 2y ago|36 comments
74.
by YorickPeterse 2y ago
You can call Israel out on its bullshit while also doing the same with Hezbollah and Hamas, it's not mutually exclusive.
75.
by YorickPeterse 2y ago
Is this actually proven though? I've seen other people argue that threads are already as fast as they can be, yet nobody is able to actually substantiate that claim.
76.
by YorickPeterse 2y ago
That particular paragraph can be phrased better so I'll adjust that. What I meant to say is that you can't handle it asynchronously like you can with sockets, i.e. polling it for readiness. This is because for file IO, reads and w
77.
by YorickPeterse 2y ago
I'm not sure how any of this is relevant to what you're quoting? I'm specifically arguing that if creating and switching between threads was as efficient as say Goroutines, you wouldn't need epoll/kqueue/async
78.
Asynchronous IO: the next billion-dollar mistake?(yorickpeterse.com)
7 points by YorickPeterse 2y ago|5 comments
79.
by YorickPeterse 2y ago
For parsing this might be the case, but writing tests becomes a lot more tricky the further down the compilation pipeline you go, as the amount of boilerplate code needed to set things up increases.
80.
by YorickPeterse 2y ago
It's more the latter: Ghostty doesn't introduce any groundbreaking features, instead it's a bunch of incremental improvements/nice-to-have's.
81.
by YorickPeterse 2y ago
There are DAP extensions for both Vim (e.g. https://github.com/puremourning/vimspector ) and NeoVim ( https://github.com/mfussenegger/nvim-dap ). I can't speak as to the experience in detail (I
82.
How to write a code formatter(yorickpeterse.com)
4 points by YorickPeterse 3y ago|0 comments
83.
by YorickPeterse 3y ago
How suitable would this be for a text editor of sorts, and what latency would one expect? Using the demo it's difficult to gauge the latency by just eyeballing it.
84.
by YorickPeterse 3y ago
This seems like a very one-sided opinion/experience. While I've certainly had my own share of odd experiences and heard similarly odd stories, this doesn't really strike me as specific to The Netherlands as a whole.
85.
by YorickPeterse 3y ago
Respectfully, I didn't. I specifically wrote the following: > I didn't get along well with this manager, The resulting conflict lead to a "performance enablement plan", a procedure meant to get things back on track be
86.
by YorickPeterse 3y ago
> how can you assure that? it seems like a classic self-fulfilling prophecy of arrogance. Because colleagues have told me so, and the annual employee reviews were positive as well. In fact, outside the PEP the only actionable/to-imp
87.
by YorickPeterse 3y ago
In Rails, you can write something like this: Project.limit(10).each do |project| project.members.count end Here `project.members` returns some sort of query object that produces a query along the lines of this: [...
88.
by YorickPeterse 3y ago
Every time we'd look into this, we'd look into the challenges we'd have to face and see if they changed since last time. One of the problems GitLab faces is that it JOINs all over the place. In addition, while most data can b
89.
by YorickPeterse 3y ago
I can assure you that me being a pain to manage wasn't the problem, nor was it ever brought up. In fact, the only negative/improve-upon-this-thing kind of feedback I got once or twice was to adjust my communication style to be les
90.
by YorickPeterse 3y ago
I think the live stream was both a great and terrible idea. It was great because it showed the world we weren't just sitting on our hands. It was terrible because trying to do your work while 5000-something people are watching (we were

More ›