zaphodias

Joined 8 years ago

Karma

165

Submissions

Member since

Aug 14

https://anto.pt <- personal blog :)

View on Hacker News

Recent submissions

Comment · 8 months ago

A lot of companies use tailwind. Here's an extract from https://claude.ai (the chat interface after logging in):

    <main class="mx-auto mt-4 w-full flex-1 px-4 md:px-8 lg:mt-6 max-w-7xl h-full !mt-0 flex flex-col items-center gap-8 md:px-14 3xl:px-20 pt-[10vh] md:pt-[20vh] max-sm:!px-1 relative">
    <div class="mx-auto flex w-full flex-col items-center gap-7 max-md:pt-4 max-w-2xl">
    <div class="ml-0.5 inline-flex items-center gap-1.5 rounded-lg h-8 px-2.5 text-center font-small sm:font-base bg-bg-300 text-text-500 select-none">

Comment · 8 months ago

they have individual IPFS links but they don't work 100% of the times

Comment · 10 months ago

Did you mean gRPC maybe?

In any case, my experience so far has been great. The connect-es generator takes your protobuf and generates a TypeScript library which looks pretty good. You can use ConnectRPC both from the browser and from Node.js (the latter can leverage HTTP/2, while the former uses the native fetch() or a function you provide).

Comment · 10 months ago

This is great - thanks for sharing. I am actually building something very similar myself as I started building a couple SaaS and though it would be nice to extract the common pieces in a template.

My stack is similar, with a few differences:

- Go backend with sqlc, but using ConnectRPC[1]. I chose this as it allows me to define a proper API scheme and generate a decent-quality Typescript client.

- Nuxt (Vue) instead of Next.js (React). I chose this even though I'm new to vue cause I saw the open source components and templates here [2] (especially the dashboard template: [3]) and was convinced.

I'll definitely check out your repo as inspiration.

[1]: https://connectrpc.com/

[2]: https://ui.nuxt.com/

[3]: https://dashboard-template.nuxt.dev/

Comment · 1 year ago

I don't think there are humans involved. I've now seen countless PRs to some repos I maintain that claim to be fixing non-existent bugs, or just fixing typos. One that I got recently didn't even correctly balanced the parenthesis in the code, ugh.

I call this technique: "sprAI and prAI".

Comment · 1 year ago

I remember seeing the concept of "torrents with dynamic content" a few years ago, but apparently never became a thing[1]. I kind of wish it did, but I don't know if there are critical problems (i.e. security?).

[1]: https://www.bittorrent.org/beps/bep_0046.html

Comment · 1 year ago

Me too, reinforced by author's name :)

Comment · 1 year ago

Did you read the article's section "Why I Built My Own Audio Player"?

Comment · 1 year ago

Just to be clear, I am authenticated. Maybe they are struggling with the AI scrapers though, you're right.

Ask HN: Did GitHub UI become unbearably slow?

14 zaphodias 1 year ago 10 comments

Comment · 1 year ago

isn't the whole point avoiding FOUC, while also avoiding to block the rendering for CSS network requests?

Comment · 1 year ago

I'm doing the same, I have family plans with my friends for pretty much anything so I don't think I ever reached such high monthly costs though.

I started my home server for self hosting Immich, not only for the cost but because I like to have my images close to me.

I also recently replaced Lightroom with ON1, it's definitely not the same quality but, as hobbyist, it didn't make much sense to pay that much for me anymore. It was by far the most expensive subscription I had.

Comment · 1 year ago

Maintenance overhead, plus:

- convenience (everyone already has a GitHub account and is familiar with the platform) - discussions platform (issues, prs, discussions) - CI (GitHub Actions)

It's already there, and it's free for the most part. Why would I bother hosting my own?

Comment · 1 year ago

Don't get me wrong, I agree! Especially performance-wise, I'd love to have the best primitives that let me build whatever I want and not some very generic primitives that perform a bit worse and I have to tune myself so I don't shoot myself in the foot.

Comment · 1 year ago

While I think you're right (generics might be useful there), it's fairly easy to wrap the `sync` primitives such as `sync.Pool` and `sync.Map` into your specific use case.

Go is pretty strict about breaking changes, so they probably won't change the current implementations; maybe we'll see a v2 version, or maybe not. The more code you have, the more code you have to maintain, and given Go's backward-compatibility promises, that's a lot of work.