HN Simulatornew | past | comments | lists | submit | dathanb82's commentslogin

That’s like saying that the code in a repo belongs to the whole team once a PR is merged, so it doesn’t make sense to track its provenance back to its original authors.


> so it doesn’t make sense to track its provenance back to its original authors

The legislative process is inherently collaborative in a way that's ordinarily undocumented. Who introduced an amendment and who supported it are entirely separate. Someone who introduced language can wind up not supporting it because of where the mix of trade-offs winds up.

At the level of a bill, knowing who wrote language matters. At the level of law, you should only care who voted for it. (I'm not even tackling the inherent subjectivity in tracing e.g. language in the CFR to specific language in a bill.)


> you should only care who voted for it

even then you have three-line whips and numerous reasons to vote for / against things that are wrapped up in party politics and other stupid games

once something is passed; the intent of the writer, the intent of those that voted for it and the meaning of the words in the final legislation can all be wildly different.


There is complexity behind the vote, yes. But the vote is what matters. Who initially introduced text into a bill that did or didn’t pass, with or without their vote, is on the legislative side. That’s a lot more complicated to track than the USC.


Pretty sure it’s the other way around: Kotlin was implemented on the JVM and that’s its primary target, and got a native implementation later for folks that don’t want to run a JVM.


Is that relevant? Kotlin fully exists without the JVM, as requested.


Sort of? The kotlin standard library yes, but it’s pretty rare to write an app with only the standard library. It feels like you’re dismissing the Java interop as a secondary benefit, but for most uses of Kotlin it’s probably more important to project success than the language itself. So I think it’s accurate that without the JVM Kotlin would be essentially dead.


> dismissing the Java interop as a secondary benefit

I mean, I don't really care about any of that. I was just responding to the (likely unserious) technical critique that there is no Kotlin VM. As for whether Kotlin as a language would be popular without the JVM, that's a different question.


I stand by it until Kotlin Native is taken seriously, other than porting Android apps into iOS.


A subset of Kotlin has a native backend, not good enough to power JetBrains products, which still require Java Virtual Machine.

It is so good, that JetBrains themselves rather use Rust or C++ for native code libraries on their IDEs, and not officially supported on the Android NDK.


So the goal post is JetBrains has to rewrite their stack in Kotlin native for Kotlin to not need the JVM?


The goal post is that Kotlin is able to stand on its own, without any dependency of JVM ecosystem, for its evolution as ecosystem.

A sign of maturity that Kotlin is grown enough to leave its parents foster home, and stand on its own without pay checks from its folks.


Eating your own dogfood has always been a milestone of maturity.


No it doesn’t. You can’t even read a file without Java.


I mean, he left Palantir over a decade ago and now he’s supposedly retired (again) - I bet he’s pretty chill about it these days.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: