> TypeScript just gets in the way of that for me. Not just because it requires an explicit compile step, but because it pollutes the code with type gymnastics that add ever so little joy to my development experience, and quite frequently considerable grief. Things that should be easy become hard, and things that are hard become `any`. No thanks!

That comment is expected by a Ruby enthusiast, which is arguably one of the most dynamic languages in existence.

▲

hvb2 3 hours ago | parent | next [-]

Types are a safeguard, they rule out certain errors. So using them is mostly for maintainability, and especially in large codebases and teams that becomes a thing.

I think that comment is clear in that he likes to work alone which for problems of a certain size just isn't feasible

▲

egorfine 2 hours ago | parent [-]

> Types are a safeguard, they rule out certain errors

I have migrated to TypeScript just about a year ago and it's my third try to migrate to TS from JS during the last decade and finally a successful one. While TS went a long road since the first versions which were incredibly hostile, my rewrite of a large codebase from js to ts revealed exactly zero type-related bugs.

	▲	overfeed 2 hours ago \| parent [-]
		eons ago, I migrated a frontend to Typescript and caught a lot of type-related bugs[1]. It was a 5kLoC, fast-moving productized prototype written by a team of 5. I won't ever do dynamic-typed plain Javascript in a team ever again, type-checker is superior to human code-reviews when it comes to catching potential bugs. Then again I prefer codebase stability of clever code or "expressiveness" 1. 20% were type-coercion bugs, 30% were non-boolean values being passed to boolean-named fields (with some overlap with the former). Linters have come a long way, but compile-time type-checking is better in almost every way.

▲

dymk 2 hours ago | parent | prev | next [-]

I'm a Ruby enthusiast - Sorbet is one of the best things since sliced bread to happen to the ecosystem. matz is pushing hard on static typing as part of the standard Ruby ecosystem as well.

	▲	matltc 30 minutes ago \| parent [-]
		Really? Matt is pushing for it now? Dang. Might try Sorbet out. What IDE/LSP do you use? I was on VSCode/ruby-lsp and disabled sorbet, but after working with Zod, I became quite intrigued with the value of letting the schema do a lot of the guarding. I was under the impression that things like Crystal (statically typed Ruby) were not in vogue, and that the reason no one was moving toward static typing was because Matz did not give his blessing. (Just checked sorbet landing page, looks like it's mainly/only for fn signatures?)

▲

aaronvg 2 hours ago | parent | prev | next [-]

these painpoints seem moot in a world where AI agents are writing all the code.

	▲	recursive an hour ago \| parent \| next [-]
		Type declarations can help an LLM in the same way they help people.
	▲	overfeed 2 hours ago \| parent \| prev [-]
		That world will never be. Humans will always be writing some code, at least for as long as I live and breathe.

▲

3 hours ago | parent | prev [-]

[deleted]