3 ms·

From: https://vlang.io/compare#go https://vlang.io/compare#go - No null - No err != nil checks (replaced by option types) - Immutability by default - Generi

by yawn 6y ago

From: https://vlang.io/compare#go https://vlang.io/compare#go - No null - No err != nil checks (replaced by option types) - Immutability by default - Generics - Sum types (type Expr = IfExpr | StringLiteral | IntLiteral ) - If and match expressions (including sum type matches) This might be my personal project goto language for 2021.

pwdisswordfish4 6y ago
> goto language As in ‘considered harmful’? I’m staying away from any language with vulnerabilities like these: https://christine.website/blog/OVE-20190623-0001 https://christine.website/blog/OVE-20190623-0001
- rsa25519 6y ago
  That looks like a vulnerability in a V playground, not a vulnerability in the V language itself.
  - pwdisswordfish4 6y ago
    It came from the same developer. The mere fact that he was that sloppy in securing a publicly-facing service to leave a vulnerability so severe and so easily discovered should have you asking: why should I believe that anything else in this project is any more robust and secure (and will be in the future)?
    - t0astbread 6y ago
      So what do you think about Linux after the kernel.org hack?
- coldtea 6y ago
  Not sure what the "considered harmful" implies here. It's clear what Djikstra meant, and it's not about removing goto altogether. Goto is still used as a best practice in many situations (e.g. error cleanup in the Linux kernel), and is very useful in other domains too (e.g. generated code for parsing, state machines, etc). As for the vulnerability, while it is real, it's not related to the language. And not even sure what "I’m staying away from any language with vulnerabilities like these" even means. As if other languages/compilers/etc, even established ones like C/Clang-GCC, Java, Javascript, etc don't have any?
  - simlevesque 6y ago
    https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...
    - coldtea 6y ago
      Yeah, I know of the paper, I even referenced it in my comment :-)
- yawn 6y ago
  The vulnerability was acknowledged and fixed in 1 day. If that's indicative of the type of response the project's authors have, color me impressed. Also, this post is for version 0.2. I ain't scurred for personal projects.
  - xena 6y ago
    Author of that secvuln report here. It was fixed by the playground server being decommissioned. I do not know the exact timeframe of any fix that was made to that playground service. Pedantically, I guess the server being permanently decommissioned could count as a fix. However it does not bode well.
    - bakul 6y ago
      The V playground seems to be up and running.
    - amedvednikov 6y ago
      Nope, all issues were fixed, and it ran without any hacks for 6 months, until it was replaced by a WASM playground.

by yawn 6y ago

pwdisswordfish4 6y ago

> goto language As in ‘considered harmful’? I’m staying away from any language with vulnerabilities like these: https://christine.website/blog/OVE-20190623-0001 https://christine.website/blog/OVE-20190623-0001

rsa25519 6y ago
That looks like a vulnerability in a V playground, not a vulnerability in the V language itself.
- pwdisswordfish4 6y ago
  It came from the same developer. The mere fact that he was that sloppy in securing a publicly-facing service to leave a vulnerability so severe and so easily discovered should have you asking: why should I believe that anything else in this project is any more robust and secure (and will be in the future)?
  - t0astbread 6y ago
    So what do you think about Linux after the kernel.org hack?
coldtea 6y ago
Not sure what the "considered harmful" implies here. It's clear what Djikstra meant, and it's not about removing goto altogether. Goto is still used as a best practice in many situations (e.g. error cleanup in the Linux kernel), and is very useful in other domains too (e.g. generated code for parsing, state machines, etc). As for the vulnerability, while it is real, it's not related to the language. And not even sure what "I’m staying away from any language with vulnerabilities like these" even means. As if other languages/compilers/etc, even established ones like C/Clang-GCC, Java, Javascript, etc don't have any?
- simlevesque 6y ago
  https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...
  - coldtea 6y ago
    Yeah, I know of the paper, I even referenced it in my comment :-)
yawn 6y ago
The vulnerability was acknowledged and fixed in 1 day. If that's indicative of the type of response the project's authors have, color me impressed. Also, this post is for version 0.2. I ain't scurred for personal projects.
- xena 6y ago
  Author of that secvuln report here. It was fixed by the playground server being decommissioned. I do not know the exact timeframe of any fix that was made to that playground service. Pedantically, I guess the server being permanently decommissioned could count as a fix. However it does not bode well.
  - bakul 6y ago
    The V playground seems to be up and running.
  - amedvednikov 6y ago
    Nope, all issues were fixed, and it ran without any hacks for 6 months, until it was replaced by a WASM playground.