5 ms·

The public contract previously discussed in RFCs and conference talks hasn't changed. Coding language is just an implementation detail.

dwb 3mo ago
Implementation details matter! Especially when reviewing the implementation.
arcadialeak 3mo ago
Nevertheless, it's also React team that came up with prefixes like __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED in their codebase because people couldn't stop messing with the internals. So any documentation about the new compiler would be anything but rejected by the community.
xedrac 3mo ago
While this is true, the fact that it is Rust provides a much greater level of confidence than if it was Python or something.
- absintini 3mo ago
  Confidence about what? That it works properly? Hopefully? Why don’t you read the 120k lines of code and tell us all how it works.
  - phillmv 3mo ago
    i feel like ppl have magical beliefs about type systems. just because it's _probably_ (did it use unsafe?) memory-safe doesn't mean it does what you want it to do
    - rowanG077 3mo ago
      That's obviously true. On the other hand its also true this is more likely to work because it is rust compared to python or js for example. And that's not only because of memory safety. It's because static typing gives an automatic proof of a certain level of correctness of the code. That correctness is correlated with correct business logic bugs. So it is valid argument to make. Of course that doesn't mean that there are no businesses logic bugs.
- xdavidliu 3mo ago
  only if it is not littered with unsafe blocks
bwfan123 3mo ago
> Coding language is just an implementation detail Sure, but what machine model do the public contract docs and RFCs target ? While the specific coding language is a detail, programming languages target a precise machine model. There is no machine model for english prompts and spec docs. So expect fuzziness - he-said-she-said bugs in your code - things that the LLM made up because the RFCs were not precise. And by the time you add precision to the specs, it has morphed into a new programming language with a machine model. In this usecase, since it is a port, the impact is mitigated because it is a clone of some existing functionality.

dwb 3mo ago

Implementation details matter! Especially when reviewing the implementation.

arcadialeak 3mo ago

Nevertheless, it's also React team that came up with prefixes like __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED in their codebase because people couldn't stop messing with the internals. So any documentation about the new compiler would be anything but rejected by the community.

xedrac 3mo ago

While this is true, the fact that it is Rust provides a much greater level of confidence than if it was Python or something.

absintini 3mo ago
Confidence about what? That it works properly? Hopefully? Why don’t you read the 120k lines of code and tell us all how it works.
- phillmv 3mo ago
  i feel like ppl have magical beliefs about type systems. just because it's _probably_ (did it use unsafe?) memory-safe doesn't mean it does what you want it to do
  - rowanG077 3mo ago
    That's obviously true. On the other hand its also true this is more likely to work because it is rust compared to python or js for example. And that's not only because of memory safety. It's because static typing gives an automatic proof of a certain level of correctness of the code. That correctness is correlated with correct business logic bugs. So it is valid argument to make. Of course that doesn't mean that there are no businesses logic bugs.
xdavidliu 3mo ago
only if it is not littered with unsafe blocks

bwfan123 3mo ago

> Coding language is just an implementation detail Sure, but what machine model do the public contract docs and RFCs target ? While the specific coding language is a detail, programming languages target a precise machine model. There is no machine model for english prompts and spec docs. So expect fuzziness - he-said-she-said bugs in your code - things that the LLM made up because the RFCs were not precise. And by the time you add precision to the specs, it has morphed into a new programming language with a machine model. In this usecase, since it is a port, the impact is mitigated because it is a clone of some existing functionality.