tkzed49

how so?

Seldom is one of those words that's used occasionally in writing, but seldom in conversation.

Why would a left-leaning press engineer errors predicting the victory of the left? Wouldn't this lull supporters of the Democrats into a false sense of security and enable Republican wins?

why not?

They're offering to subsidize the cost that the individual would normally pay for COBRA coverage. They're only required to offer the coverage, but not to pay for it.

However, I don't think this is that unusual in SV layoff packages.

really feels like an article begging for photos

Pixel 10 absolutely ate shit when I opened the page!

You said it better than I could! As someone who does software for a living, do I want to come home and maintain a homelab that hosts photos, email, decentralized social, etc? Hell no!

Even if it's fun as a hobby, I don't want to be on call for my own basic online services.

Every time I hear about commit messages on HN, this is my first thought. I can't imagine not working in a squash workflow. No matter how good your commit messages are, I do not want to read all of them. The squashed commit will direct me to the original PR in case I need more detail.

It strikes me as odd that boxes are placed precisely using pixels, but the size of text is not specified, as far as I can tell. So you use real pixels to specify boxes, but still can't render a canvas exactly/consistently?

was this written using a LinkedIn skill

from my perspective--I have to use React, Lit, and all kinds of other creative solutions at my day job--I'm going to immediately devalue someone's argument if it starts with "I hate React".

React is not popular simply because engineers hate themselves or enjoy pain. There are problems it solves, and problems it creates. Explain what problems your solution solves, and feel free to dunk on React while you're at it, but write a tagline like this and I'm not gonna take you seriously.

"GitHub's own security guidance recommends pinning actions to full commit SHAs as the only truly immutable way to consume an action"

Why doesn't GitHub just enforce immutable versioning for actions? If you don't want immutable releases, you don't get to publish an Action. They could decide to enforce this and mitigate this class of issue.

you continue to contradict yourself by introducing concepts and saying they are not concepts.

I get what you're trying to say, that React hooks have special semantics, and that your abstraction feels more "native".

again, not sure how this is more "native" than Solid signals, just as an example.

> Solid has signals and createEffect... Gea takes a different path. It introduces no new concepts at all.

proceeds to introduce Stores and Components

what makes this magically easier than Solid, or any other Proxy-based reactive store frameworks?

out of curiosity, what makes Geekbench 6 better?

mid take ngl

Can I buy them for my underage friends at different stores? Is there revocation and hence a database that maps codes to identities?

How are the codes minted? Can I pretend to be a gas station and buy a big pack of ID cards, then just not check ID?

The average LLM writes cleaner, better-factored code than the average engineer at my company. However, I worry about the volume of code leading to system-scale issues. Prior to LLMs, the social contract was that a human needs to understand changes and the system as a whole.

With that contract being eroded, I think the sloppiness of testing, validation, and even architecture in many organizations is going to be exposed.

Can I get an AI that automatically nitpicks AI PRs with the goal of rejecting them?

Hey man, if you ever see this, not your fault it ended up on HN early! I'm sure this is solid for your usecase. That's just something that would dissuade me from choosing it!

I've gone back to using two dashes--LLMs typically don't write them that way.

I clicked on Dropdown, thinking it's one of the more complex things to implement. It doesn't even have a picture.

The fact that there's no tangible plan for any plugin support in Turbopack is actually what made me not choose Next.js.

The answer for people who need basically any build plugin is "use the webpack mode", and I have zero faith in Vercel maintaining that past the next major version.

I guess we'll see whether they figure out a story for plugins by then.

mirror https://bsky.app/profile/alexip718.com/post/3md6uyjftvc2f

why would you bid the highest price you can afford in an auction? the seller agreed to auction the thing; they could have just offered it for a set price.

let me clarify the intent of my comment then. Human rights is not a "two-sides" issue to be debated. If you attempt to reduce an affirmation of human rights for all people to a "political agenda", I will call out your conservative dogwhistle. I don't care how that's received.

human rights are not politics

Appreciate the perspective. I've worked on projects where hooks are auto-configured, and pre-commit is just never something that's going to agree with me.

I prefer to be able to push instantly and get feedback async, because by the time I've decided I'm done with a change, I've already run the tests for it. And like I said, my editor is applying formatting and lints, so those fail more rarely.

But, if your pre-push checks are fast (rather than ~minutes), I can see the utility! It sucks to get an async failure for feedback that can be delivered quickly.

Thank you. I don't need to "fix" a commit before it ends up on a remote branch. Sometimes I expect a commit to pass checks and sometimes I don't. Frankly, don't even run pre-push hooks. Just run the checks in CI when I push. You'd better be doing that anyway before I'm allowed to push to a production branch, so stop breaking my git workflows and save me the time of running duplicate checks locally.

Also, if most developers are using one editor, configure that editor to run format and auto-fix lint errors. That probably cleans up the majority of unexpected CI failures.