Viewing profile — francislavoie
francislavoie
HN member- Joined
- Wed, Nov 22, 2017, 7:47 PM UTC
- HN karma
- 1,815
- Public activity
- 754 items
- HN profile
- View on Hacker News ↗
About francislavoie
https://meet.hn/city/ca-Ottawa
[ my public key: https://keybase.io/lavofr; my proof: https://keybase.io/lavofr/sigs/89IwNhliuw72n2Le4Cx6679wAkPUDO7p0v_Q_sipXoU ]
Recent public activity
-
comment
Comment #49143287
The component itself is the semantics, adding naming over CSS classes adds no value whatsoever, only adds cognitive load and requirement of context switching to understand "what do…
-
comment
Comment #49142993
I disagree. I don't want to jump between two files constantly. With Tailwind I can stick to one file and never need to think about naming things.
-
comment
Comment #49142962
Your complaint is about bad developers, not about Tailwind. Using Tailwind correctly means making heavy use of components to avoid duplication. Using Tailwind also removes the burd…
-
comment
Comment #49142926
I would reach for class-variance-authority (aka cva) instead for stuff like a size prop, it declaratively solves that.
-
comment
Comment #49142910
Absolutely not. Semantic classes are the wrong way to go. Your components (and their props API) are what encode the semantics. With Tailwind you never need to try to come up with a…
-
comment
Comment #49142859
Using @apply defeats the entire purpose of Tailwind. The point of it is to localize styling alongside the markup. If you're using @apply then you're constantly context switching fr…
-
comment
Comment #49142418
Saying "unless you use @apply" invalidates this article for me. Everyone knows that @apply only exists as an escape hatch, it is not supposed to be used, except for when it's neces…
-
comment
Comment #49111504
I set up a custom hook in Claude which runs my own worktree creation/cleanup script, which takes care of copying my node_modules into the worktree, my .env (plus doing some edits t…
-
comment
Comment #48833915
Yeah a lot of them like Mattermost become surprisingly limited unless you pay. It's very annoying.
-
comment
Comment #48575082
Obviously, and that's why tools like perforce and lore exist. What's your point?
-
comment
Comment #48413796
But they give a usable interface and toolkit to the runtime (V8 etc). 99% of users use one of those three.
-
comment
Comment #48399477
Vite is not a package manager and is not a JS runtime. That's what Node/Bun/Deno do. Vite is the remaining glue for any web project's build and testing needs.
-
comment
Comment #48043561
We've been using https://github.com/loupe-php/loupe , works quite well for small-to-medium single-instance apps.
-
comment
Comment #47515332
What, Go's net/http is fantastic. I don't understand that take. Many servers are built on it because it's so fully featured out of the box.
-
comment
Comment #47245452
(Disclosure: I'm a Caddy maintainer), Caddy already supports ECH, leaning on the DNS plugins to automate setting the DNS HTTPS records to wire it up. Here's a lot of technical deta…
-
comment
Comment #47243116
Is it a "Ship of Theseus" photon? Hehe
-
comment
Comment #47229718
Changing timezones suck, but sunset happening at 4:30pm before I leave work to go home massively contributes to winter depression. It's like "well that was a tiring day" and then i…
-
comment
Comment #47228101
Hell noooo. 4:30pm sunsets are ultra depressing in the winter. Less light in the morning is not at all a problem in comparison.
-
comment
Comment #47146208
I've helped many Twitch streamers set up https://github.com/royshil/obs-localvocal to plug transcription & translation into their streams, mainly for German audio to English subtit…
-
comment
Comment #47031329
It's much more than that because it can make use of CSS pseudo selectors like hover, which is not possible with inline styles.
-
comment
Comment #46367467
Unfortunately a lot of our tests use transactions themselves because we lock the user row when we do anything to ensure consistency, and I'm pretty sure nested transactions are sti…
-
comment
Comment #46365951
But how does the reset happen fast, the problem isn't with preventing permanent writes or w/e, it's with actually resetting for the next test. Also using overlayfs will immediately…
-
comment
Comment #46365930
Yeah there's absolutely no way restarting the container will be faster.
-
comment
Comment #46365309
Restarting the DB is unfortunately way too slow. We run the DB in a docker container with a tmpfs (in-memory) volume which helps a lot with speed, but the problem is still the raw …
-
comment
Comment #46365259
Is anyone aware of something like this for MariaDB? Something we've been trying to solve for a long time is having instant DB resets between acceptance tests (in CI or locally) bac…