Kevcmk

Just a reminder that iTerm is FOSS: https://github.com/gnachman/iTerm2

I agree with most of this article but the "don't use poetry" comment is ridiculous. Pdm could be great with time but suggesting it is premature.

Pro tip, sites don't have the means/motivation to challenge a user's assertion that they're in France (GDPR) or California (CCPA). Just pick a Paris address and demand a GDPR Data Subject Request (DSR) to delete your data.

With css this bad, I don’t think I’m capable

Nvidia is powering a mega Tesla supercomputer powered by 10,000 H100 GPUs

You'd be a bad parent

Bad take

I believe that what is being missed in this thread is that, as it stands, user consent can be forged by prompt injection.

The chat muxing issue wasn't great, but it was an understandable software error that any professional software engineer could have made. The AI alignment challenge is much more pertinent and under-attended.

It's 2023 what kind of plebeian is using raw image tags? NextJS's OSS design is exactly what it should be, I want the image tag. I don't want Vercel boxing me into a choice:

  1. Serving images over Node.
  2. Using Vercel.

I also don't want to eject code that is sitting right there in the repo. And I don't want to maintain a fork of a homebrew reimplementation of it.

Which one, the go ahead and "define your own custom loader"? You mean re-implement the image export that is sitting right there in their express server... from scratch? Hah.

NextJS won't let you export their optimized images in a static site export because they want _everything_ running through their Express server.

Why's that great for them? Because they get to charge you for image bandwidth and image optimization. This is called vendor lock in.

Sources:

In vivo (v13.3.0):

  > npx next export
  <...>
  error - Image Optimization using the default loader is not compatible with export.
    Possible solutions:
      - Use `next start` to run a server, which includes the Image Optimization API.
      - Configure `images.unoptimized = true` in `next.config.js` to disable the Image Optimization API.
    Read more: https://nextjs.org/docs/messages/export-image-api

and https://vercel.com/changelog/changes-to-vercel-image-optimiz...

Vercel is deceitful.

The Image/img fiasco really pulled the covers off for vercel for me. I have migrated all my work off of the platform.

NextJS’ lint strategically dissuades you from using the img tag in favor of the NextJS Image component. If you make the mistake of heeding this advice and migrating to it, you can’t use static site generation—which means you are stuck using their hosting.

Here’s one of the most PR-shameful threads I’ve ever read in OSS:

https://github.com/vercel/next.js/discussions/19065

I shoot exclusively film and am thrilled to see attempts at this. The medium is far too expensive and need not die in the name of exclusivity

Agree. This is misdirection.

Cynicism is both cheap and lazy. You two sound miserable

Agree. But experts/intermediates often gloss over language semantics in pursuit if getting something done. For me, floating point by-default is more often a nuisance

Can you imagine how miserable you'd have to be to overreact this hard to an eighteen-year-old sending you a PR