HNHacker News
TopNewBestAskShowJobs

amedvednikov

1,578 karma · joined November 15, 2016

submissionscomments
amedvednikov··on Mojo is a much better “Objective-C without the C” than Swift ever was
Yeah, this docs section was not synchronized with the landing page, and had bad wording. It says "work in progress", meaning that's something that's planned/being investigated.

This was later worded better. But I agree, the docs should have never had such wording.

amedvednikov··on Mojo is a much better “Objective-C without the C” than Swift ever was
Can you please list outrageous claims by V?
amedvednikov··on Mojo is a much better “Objective-C without the C” than Swift ever was
Here's the version of the website 3 years ago:

https://web.archive.org/web/20200629153446/https://vlang.io/

Can you point to that claim?

Here's 4 years ago:

https://web.archive.org/web/20190828170427/https://vlang.io/

> V manages memory at compilation time (like Rust). Right now only basic cases are handled. For others, manual memory management is required for now.

amedvednikov··on Mojo is a much better “Objective-C without the C” than Swift ever was
V claims to take care of most objects (~90-100%) and uses GC for the stuff it can't figure out during compilation.

This is very clearly explained on the website:

https://vlang.io/#memory

amedvednikov··on Mojo is a much better “Objective-C without the C” than Swift ever was
V is close to C since it literally compiles to C, and it is a simple/readable language like Python and Go, so what's to call out?
amedvednikov··on DeviceScript – TypeScript for Tiny IoT Devices
It delivers on everything listed on the website/docs. You can check for yourself.
amedvednikov··on V0.3.4 is out. A big release with cool features like live web app reloading
A pure V native WASM backend, vweb worker pool, middleware/controllers in vweb, lots of ORM fixes, a new online playground and so on.
amedvednikov··on Ask HN: Faster than C, simpler than Python, safer than Rust. Possible?
If there's an error at reading app.log, the error is printed, and the function is returned.

Code after that won't run at all.

amedvednikov··on Simulating Softbody Dynamics in Vlang
The source code release wasn't actually delayed. It was promised by June 2019, and it was released by June.

I did an early release of the Patreon-only compiler without sources, and that was a mistake.

amedvednikov··on Simulating Softbody Dynamics in Vlang
> the scientific lib vsl is quite different from the tensor lib

Check out vtl:

https://github.com/vlang/vtl

amedvednikov··on Twitterrific has been discontinued
Discord doesn't ban third party clients, only illegal stuff like spamming.

From the people at Discord:

> I run the infrastructure department at Discord which includes our anti-spam engineering team -- Just want to +1 what you're saying and confirm that we are never trying to ban third party clients (that aren't self-bots). Honestly, it would be a waste of our time and basically do nothing good for Discord.

https://news.ycombinator.com/item?id=28438440

amedvednikov··on Go runtime: 4 years later
V fixes most of these, but it doesn't use Go's runtime:

https://vlang.io/compare#go

amedvednikov··on V 0.3
It literally says V 0.3 in the very center of the website. First thing.
amedvednikov··on V 0.3
Macros are unwrapped by Clang when generating C AST.

No plans to support C compilation for now, translation works well enough.

amedvednikov··on V 0.3
They are both true, and it clearly says it's not production ready yet, so there are bugs.
amedvednikov··on V 0.3
Sure.

https://www.youtube.com/watch?v=pvP6wmcl_Sc

> they expect V to compile itself in less than a second for the general case (not just one very specific case).

What on earth are you talking about? There's no specific case. Check the video. Try it yourself. Have you actually tried it?

Can you list the inaccurate claims here please and in progress features that are not clear to the user?

amedvednikov··on V 0.3
The first public release of a C2V alpha is not going to handle all C programs right away. This is planned for a 1.0 release later this year.
amedvednikov··on V 0.3
All popular languages have more open bugs on github.
amedvednikov··on V 0.3
No, it describes it absolutely accurately:

> until V's autofree engine is production ready.

amedvednikov··on V 0.3
Who's Cadey? Do you have a link?
amedvednikov··on V 0.3
It takes a lot more than one troll to mass flag a post 3 times within a day.
amedvednikov··on V 0.3
strconv.v_sprintf is an internal function only used by the compiler in string interpolation. It should simply be made private.
amedvednikov··on V 0.3
You said there are false claims about language capabilities, I asked you to list them. It's a reasonable request. I don't want to have false claims on the website.
amedvednikov··on V 0.3
> You claim V is as fast as C but there are many many many cases where V is slower than C. On average, V seems to be much slower than any compiled language.

This is false.

> Everyone wants you and V to succeed

The same people who write articles about V and say V should die?

amedvednikov··on V 0.3
Lol, no issues/comments are removed.

One and only time a github comment was removed was before the open source release and I just started this new job of an open source maintainer.

Actually, sorry, I did remove one issue recently. It said "Delete this project, it's a joke".

amedvednikov··on V 0.3
That's a bug, the compiler should require `unsafe { n := Node { 123,nil,nil } }`.
amedvednikov··on V 0.3
Because it's null (unsafe{0} will be replaced with unsafe {nil})

It needs to be inited recursively with

app := App { gg: &gg.Context { ... app } }

And that doesn't work yet. It used to work in the initial V, but not right now.

It'll be fixed in 0.4.

amedvednikov··on V 0.3
But it is true. V doesn't add any overhead. You can verify with `v -o file.c file.v`.

As long as you use the same data structures and algos, you'll get the same perf.

There's stuff like bounds checking, but it can be disabled, and it adds like 5%.

amedvednikov··on V 0.3
It's funny because in the previous discussion I got lots of "what's the problem? fix the bugs and publish your own post going through the points in this one".
amedvednikov··on V 0.3
"As fast as C" is not a lie. It literally translates to C.

The 200x compile speed up referred to C++ compilers, this was vague and hard to measure, since the languages are so different, and was removed.

The code may not have been perfect at the time of the 0.0.1 release, but it worked. V could compile itself.

Now it's much better and more organized.

← PreviousPage 5 of 26Next →