spion · HackerTrans

в прошлом месяцеdiscuss

Use composer 2.5 fast in cursor (or cursor cli).

YMMW but I find it fast enough to maintain focus on one task (if that's what you're going for given a particular problem

spion

4 месяца назадdiscuss

A summary of the session should be part of the commit message.

spion

4 месяца назадdiscuss

Why aren't we using HATEOAS as a way to expose data and actions to agents?

spion

6 месяцев назадdiscuss

cold take speculation: the architecture astronautics of the Java era probably destroyed a lot of the desire for better abstractions and thinking over copy-pasting, minimalism and open standards

hot take speculation: we base a lot of our work on open source software and libraries, but a lot of that software is cheaply made, or made for the needs of a company that happens to open-source it. the pull of the low-quality "standardized" open source foundations is preventing further progress.

spion

6 месяцев назадdiscuss

Has anyone measured whether doing things with AI leads to any learning? One way to do this is to measure whether subsequent related tasks have improvements in time-to-functional-results with and without AI, as % improvement. Additionally two more datapoints can be taken: with-ai -> without-ai, and without-ai -> with-ai

spion

6 месяцев назадdiscuss

Great article. Really advances the thinking on error handling. Rust already has a head start compared to most other languages with Result, expect and anyhow (well, color_eyre and tracing), but there was indeed a missing piece tying together error handling "actionability" with "better than stack trace" context for the programmer.

With regards to context for the programmer, I still think ultimately tracing and color_eyre (see https://docs.rs/color-eyre/latest/color_eyre/) form a good-enough pair for service style applications, with tracing providing the missing additional context. But its nice to see a simpler approach to actionability.

spion

6 месяцев назадdiscuss

IMO you need both things: culture to make it happen, and technology to make it easy and reasonable looking. Rust lacks the former to some degree; Go lacks the later to some degree (see e.g. kustomize error formatting - everything ends up on a single line)

spion

6 месяцев назадdiscuss

I don't think there is anything in Go (the language) that helps achieve this - its mostly cultural. (Go creators and community being very outspoken about handling errors).

In fact, the easiest thing to do in Go is to ignore the error; the next easiest is to early-return the same error with no additional context.

Technically speaking, Rust has way better tools for adding context to errors. See for example https://docs.rs/color-eyre/latest/color_eyre/

It does expect you to use `wrap_err` to get the benefits, though. Which is easier to do than what Go requires you to do for good contextual errors, and even easier if you want reasonable-looking formatting from the Go version.

spion

9 месяцев назадdiscuss

I wonder if it would've felt more natural if the "part 2s" of the puzzles became separate days instead. (Still 12 days worth of puzzles, but spread out across 24 days, with maybe one extra, smaller, easier puzzle for the last day to relax)

spion

10 месяцев назадdiscuss

pnpm just added minimum age for dependencies https://pnpm.io/blog/releases/10.16#new-setting-for-delayed-...

spion

10 месяцев назадdiscuss

I don't think thats contrary to the article's claim: the current tools are so bad and tedious to use for repetitive work that AI is helpful with a huge amount of it.

spion

10 месяцев назадdiscuss

Its not settled whether AI training is fair use.

spion

3 года назадdiscuss

Its not an interface though:

  public abstract class Reader

Did Java add multiple inheritance or am I missing something?

spion

3 года назадdiscuss

Is that the modern Java equivalent of the single-method interface in Go? I can see its an abstract class - what do you do if you want to implement both Reader and Writer?

spion

3 года назадdiscuss

Kind of, but not quite. There is also:

- compiling to a single binary (I guess jpackage fixes this)

- saner / less elaborate / more ergonomic interfaces to implement and use e.g. compare `io.Reader` (https://go.dev/tour/methods/21) to the Java equivalent

spion

3 года назадdiscuss

I like the story, but I think people will notice pretty quickly as almost everyone reviews their photos right after taking them (so they can compare them with what they see in reality)

spion

4 года назадdiscuss

It was called MobX and it was getting more and more traction before the hooks hype.

spion

4 года назадdiscuss

This was not the only design possible. The main problem with lifecycle methods was that you couldn't have multiple of them. There is absolutely nothing about the design of React that necessitated hooks to fix that issue.

You could have this API

  this.addListener('mount', () => {
    // do things on mount
    // return cleanup to be called on unmount
    return () => cleanup()
  })

called from the constructur of a component. With this you could setup multiple listeners and make sure they're all cleaned up.

But no, the syntax wasn't "clean" (you'd pass `this` as an argument to the "custom hooks" equivalent"), so instead we got this error-prone order-dependent design that doesn't allow conditional execution and runs on every render.

spion

4 года назадdiscuss

> Which is a huge win IMO because the whole class/object paradigm in JavaScript is broken, and tracking what ‘this’ might be is literally impossible.

I chuckled. `this` is a piece of cake to understand compared to hooks.

`this` is a function argument that is typically passed to the function by placing it left of the dot at the time when you call the function. That's all you need to know - now you understand `this`.

Hooks are a whole nightmare in comparison - there is a stateful counter that assigns an index to every `useState` call just to determine which result you need to get back. This is a terribly error-prone design that passed review with lots of dubious justifications.

spion

4 года назадdiscuss

The original design was fine, the hooks redesign was a total miss

comments