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

Points: 159

# Comments: 19

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

Points: 2

# Comments: 0

1. Implying that there are only "a few islands left" shoes a strong bias towards assuming that only thins humans do in the digital realm is relevant, when in fact, the vast majority of things humans do are not in the digital sphere at all.

2. It's pretty clear when most people say that machine intelligence is close, right now, they are alluding to LLM or Deep Learning based approaches. I don't think you should assume they mean machines will catch up in a 100 years. They seem to imply it will be by 2030 or sowmthing.

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

Points: 6

# Comments: 0

I think there is a programming language hole for a Rust-like language, but with GC and green threads. One that dispenses with single-ownership, and async/await footguns.

Something like F#/Kotlin is closest in terms of developer experience.

Unfortunately, we are really lacking a language that skews badly on some other axis

- F# - tainted by being Windows only for really long and being Microsoft. - Kotlin - tainted by the JVM - Java 24+ - has virtual threads, sum types, match expressions and other niceties, but tainted by the JVM again (Verbosity included, but this is not really a factor with IDEs and LLMs.)

Note that the opinions above are not mine, but "consensus". I'd say they are all unfair opinions.

I feel like people end up favoring new languages, simply because of novelty. Like, inevitably, somebody is gonna say Gleam. I'm all for having existing BEAM users getting access to new languages, but I'm not sure why one would pick a BEAM language for non-server applications when the developer tooling story for CLI apps, line-of-business apps and so on is so much stronger for the .NET and JVM ecosystems. No offense to the Gleam folks intended.

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

Points: 5

# Comments: 2

* CI (I understand pre-commit shifts errors left)

* in editor/IDE live error callouts for stuff like type checking, and auto-formatting for things like "linters".

Do you run tests? How do you know _which_ tests to run, and not just run every test CI would run, which could be slow?

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

Points: 2

# Comments: 0

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

Points: 145

# Comments: 124

Along with a guarantee that you get to keep access to older versions (Jetbrains and Sublime Text models)?

This is an accurate, but damning indictment of how some of the most highly paid workers on the planet won't pay for tools. Unlike nearly every other profession.

Folks, if you can afford it, please pay for quality software, instead of relying on FAANG and VC money to keep the tools going!

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

Points: 4

# Comments: 0

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

Points: 4

# Comments: 0

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

Points: 3

# Comments: 0