There's a lot of push back against AI-generated graphics and music. For code, it's more difficult to know. AI is used by some people to automate the boring tasks, so that they can focus more on the artistic side.

Comments URL: https://news.ycombinator.com/item?id=47391834

Points: 26

# Comments: 3

Comments URL: https://news.ycombinator.com/item?id=46937806

Points: 1

# Comments: 0

Multiple of my blog posts have been shared here before

The source code is here: https://github.com/laurentlb/shmup8/blob/main/src/shaders/sc...

Blending is on lines 241, 242.

I didn't try to get a specific 80s look, I just played with formulas.

Comments URL: https://news.ycombinator.com/item?id=46325337

Points: 108

# Comments: 18

But I find this kind of presentation much harder to read than a classic blog post. It's difficult to skim through the text to see how far it goes (and the article structure is not apparent); instead, I was kind of forced to read the text sentence by sentence (since I was familiar with the topic, I wanted to skip over the basics).

I'm starting a new project, I may have to use this tool in the next few months.

Comments URL: https://news.ycombinator.com/item?id=45631123

Points: 2

# Comments: 0

- Content may be provided by contributors (like Duolingo did for many years)

- It could be supported by donations (I believe the costs can be kept low)

My feeling is that lots of problems with Duolingo are caused by monetization (and many things were better in Duolingo a few years ago).

I'm still not sure of how it should be designed and what we need exactly. One of the problems is also to get enough contributors. I'd be interested in hearing more thoughts on this.

As a hobby, I started building an alternative to the Duolingo Stories feature (https://lingostories.org), but it's still fairly limited.

Nice game otherwise.

Comments URL: https://news.ycombinator.com/item?id=45203707

Points: 4

# Comments: 0

Potential issues:

- If you have content in a database, can you able to restore the database at any point in time?

- If you code has dependencies, were all the dependencies checked in the repository? If not, can you still find the same version you were using.

- What about your tools, compilers, etc.? Sure some of them like Go are pretty good with backward compatibility, but not all of them. Maybe you used a beta version of a tool? You might need to find the same version of the tools you were using. By the way, did you keep track of the versions of your tools, or do you need to guess?

Even with static websites, you can get into trouble if you referenced e.g. a JS file stored somewhere else. But the point is: going back in time is often much easier with static websites.

(Related topic: reproducible builds.)

It's usually called operator because it uses an infix notation.

When I looked into CYOA, I opted for Ink. It's using a nice text-based language, a bit like markdown. It worked well for me, and I think it's a good option if you want to use a text editor.

I wrote about my experiments here: https://laurent.le-brun.eu/blog/my-adventures-with-narrative...

As it was not clear from the description, there's a one-time payment (4.29€) to get more than 7 puzzles in a day.

Lichess also offers a good alternative to this, although their offline support is limited.

Comments URL: https://news.ycombinator.com/item?id=44446917

Points: 249

# Comments: 126

I also enjoy alternating work between multiple of my hobby projects, and I find it refreshing to come back to this F# codebase once in a while. :)

  const float x = sin(2);
  const float y = 2;

Renaming uniforms is optional (there's a flag). If you use C++, you can generate a .h header file that contains both the minified shader and macros that tell you how they've been renamed.

So Shader Minifier will generate macros like:

  # define VAR_time "f"