Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
victorNicollet
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
victorNicollet
5mo ago
Isn't the ¨ (U+00A8) character equivalent to an umlaut on a space? I suppose you used ◌̈ (U+0308).
2.
▲
by
victorNicollet
1y ago
The atmosphere is estimated to have ~830PgC worth of CO₂, and plants are estimated to photosynthesize ~120PgC worth of CO₂ every year, so a given molecule would have 14% chance to be broken down in a year. The probability to survive for 200
3.
▲
by
victorNicollet
1y ago
I have seen the similar assertion "some of the water molecules you drank today were once part of a dinosaur", which is false because water molecules do not last very long when in liquid phase (they continuously swap protons, turni
4.
▲
by
victorNicollet
1y ago
We are using binary formats in production, also for data visualization and analysis. We went for a simple custom format: in addition to the usual JSON types (string, number, array, boolean, object), the serialized value can contain the stan
5.
▲
by
victorNicollet
1y ago
I would say 4. grab individual code files (as opposed to entire libraries) and manually edit them, removing unnecessary features and adding new ones where needed.
6.
▲
by
victorNicollet
1y ago
Tree-shaking is able to remove code that will never be called. And it's not necessarily good at it: we can detect some situations where a function is never called, and remove that function, but it's mostly the obvious situations s
7.
▲
by
victorNicollet
1y ago
The snippet you shared is consistent with the kind of output I have also been seeing out of LLMs: it looks correct overall, but contains mistakes and code quality problems, both of which would need human intervention to fix. For example, wh
8.
▲
by
victorNicollet
2y ago
We use the following steps: - Each service listens on a different, fixed port (as others have recommended). - Have a single command (incrementally) build and then run each service, completely equivalent to running it from your IDE. In our c
9.
▲
by
victorNicollet
2y ago
Indeed. Worst week of 2023 ! But I consider myself lucky that the issue could be reproduced on a local machine (arguably, one with 8 cores and 64GiB RAM) and not only on the 32 core, 256GiB RAM server. Having to work remotely on a server wo
10.
▲
by
victorNicollet
2y ago
One of the hardest bugs I've investigated required the extreme version of debugging with printf: sprinkling the code with dump statements to produce about 500GiB of compressed binary trace, and writing a dedicated program to sift throu
11.
▲
by
victorNicollet
2y ago
The trouble is, darklaga.bin will not work locally because it must be fetched over an HTTP(S) connection. So, there's a darklaga.local.html provided when running locally. The build sequence is "npm run pack" then "npm ru
12.
▲
by
victorNicollet
2y ago
Yes, ship offset from touch point was an intentional 2024 change. In the 2004 version, touch screens used a stylus, which were thin enough that you could see whatever you were touching, so the player's ship was centered on the stylus p
13.
▲
by
victorNicollet
2y ago
The square pattern enemies are a bug (well, level design mistake) back from 2004, where they would move outside the range of the laser but would still be within reach of other weapons. I must admit, since I no longer have access to the leve
14.
▲
by
victorNicollet
2y ago
On other browser/platform combinations I use fullscreen mode, which gets rid of the issue entirely. But it isn't supported on iOS Safari as far as I can tell.
15.
▲
by
victorNicollet
2y ago
Sadly I could no longer build the C++ version of the game because of some missing proprietary dependencies, but I don't expect there would have been noticeable improvements: it was already running at 60FPS on computers from the time, e
16.
▲
Show HN: A remake of my 2004 PDA video game
(nicollet.net)
106 points
by
victorNicollet
2y ago
|
23 comments
17.
▲
by
victorNicollet
2y ago
I agree ! We use the commit status instead of the PR status. A non-FF merge commit, being a commit, would have its own status separate from the status of its parents.
18.
▲
by
victorNicollet
2y ago
I suppose our development process is a bit unusual. The meaning we give to "the commit is green" is not "this PR can be merged" but "this can be deployed to production", and it is used for the purpose of select
19.
▲
by
victorNicollet
2y ago
Wouldn't CI be easier with a monorepo ? Testing integration across multiple repositories (triggered by changes in any of them) seems more complex than just adding another test suite to a single repo.
20.
▲
by
victorNicollet
2y ago
I'm not familiar with GitHub Actions, but we reverted our migration to Bitbucket Pipelines because of a nasty side-effect of conditional execution: if a commit triggers test suite T1 but not T2, and T1 is successful, Bitbucket displays
21.
▲
by
victorNicollet
2y ago
Avoiding SQL migrations was my #1 reason for moving to event sourcing. This approach cuts the "database server" into an event stream (an append-only sequence of events), and a cached view (a read-only database that is kept up-to-d
22.
▲
by
victorNicollet
2y ago
> Onion architecture etc. is a long-term strategy that mainly benefits the company/project owner, but not the individual contributor. So it basically has to be forced upon programmers, who will resist it in every way possible, becau
23.
▲
by
victorNicollet
2y ago
I have created a DSL for supply chain optimization over the last 10 years[1], and gave a talk about it back in 2017[2] that summarizes the main reasons why we did this over the alternatives (such as using Python). We measure success along a
24.
▲
by
victorNicollet
3y ago
I'm a maintainer for an open source .NET library that, ironically, only exists because it provides a feature that Microsoft removed from .NET during the migration to .NET Core. Very rarely have I needed a library to solve a problem, an
25.
▲
by
victorNicollet
3y ago
In a situation where I'm adding a new feature to the language, with a new syntax that causes me to add a new rule to the grammar, I'm concerned that the new rule will accidentally "capture" some code that already exists
26.
▲
by
victorNicollet
3y ago
The host language is the language that you are using to write the compiler/interpreter. I suppose the grandparent is asking the question in order to recommend a parser generator for your use case. From your GitHub profile, I assume it&
27.
▲
by
victorNicollet
3y ago
I am a bit biased (in the sense that I wrote my own SLR parser generator twice, in C# and F#!), but the benefit of LR is that you can know whether your CFG contains conflicts, which is a game changer for preserving backwards compatibility w
28.
▲
by
victorNicollet
3y ago
Not having ambiguities is actually the main selling point of PEGs. If you have two rules A and B that can both match the input, then a CFG A|B has an ambiguity (two possible derivations), but a PEG A/B explicitly says that the A deriva
29.
▲
by
victorNicollet
3y ago
Yes, something like ANTLR for Java, or the entire list here: https://en.wikipedia.org/wiki/Comparison_of_parser_generator... I've had good experiences with Menhir (for OCaml) and Tree-sitter, and implemented my ow
30.
▲
by
victorNicollet
3y ago
I would say JSON + schema, rather than just JSON. Like S-expressions, JSON saves you from having to implement a tokenizer, and a tokenizer is one of the easier parts of a DSL. You still need to implement something like a syntax, because thi
More ›