71–80 of 136 posts
Earlier quoted context omitted.
Strange. What about GitLab and Gitea? And probably others.
In the case of Gitea, an argument could be made that it's actually `gi•tea`, not `git•ea` :)
Earlier quoted context omitted.
i was annoyed by the hyperbolic ambitious claims but if the guy and his friends pour out solid code then there's nothing else to say :) also they seem to aim at frugal fat free programming, i cannot not like that
Those that lie often either don't respect other people or they don't have the ability to know when they are lying. Which is scarier? Go, Nim, and Zig have similar focuses and their devs have put in years of public, good work. Some of the take downs at the time he was making his initial claims are absolutely brutal and make it clear that he not only couldn't back up his crazy claims, he wasn't getting the small stuff…
Also, allocating a fixed 1000 byte region at the start of a program is not a "memory leak". In fact even glibc has tons of such "initial fixed cost" allocations - IIRC valgrind has built-in "suppression file" to ignore these allocations. (It would be a memory leak if the compiler allocated new 1000 byte chunks every time println is called, but the article doesn't demonstrate it so I guess I'll never know.)
Earlier quoted context omitted.
Those that lie often either don't respect other people or they don't have the ability to know when they are lying. Which is scarier? Go, Nim, and Zig have similar focuses and their devs have put in years of public, good work. Some of the take downs at the time he was making his initial claims are absolutely brutal and make it clear that he not only couldn't back up his crazy claims, he wasn't getting the small stuff…
Some points in that page don't seem like valid criticism. Like, complaining that the compiler is not "zero dependency" on Linux, because it depends on glibc? Also, allocating a fixed 1000 byte region at the start of a program is not a "memory leak". In fact even glibc has tons of such "initial fixed cost" allocations - IIRC valgrind has built-in "suppression file" to ignore these allocations. (It would be a memory le…
Earlier quoted context omitted.
Here is a nice mini series of blog posts about V https://christine.website/blog/series/v
The best bit is this excerpt from the standard library (2019): fn download_file(url, out string) { // println('\nDOWNLOAD FILE $out url=$url') // -L follow redirects // println('curl -L -o "$out" "$url"') os.system2('curl -s -L -o "$out" "$url"') // res := os.system('curl -s -L -o "$out" "$url"') // println(res) } Here's what that file looks like today: https://github.com/vlang/v/blob/master/vlib/net/http/downloa...
Earlier quoted context omitted.
Those that lie often either don't respect other people or they don't have the ability to know when they are lying. Which is scarier? Go, Nim, and Zig have similar focuses and their devs have put in years of public, good work. Some of the take downs at the time he was making his initial claims are absolutely brutal and make it clear that he not only couldn't back up his crazy claims, he wasn't getting the small stuff…
Some points in that page don't seem like valid criticism. Like, complaining that the compiler is not "zero dependency" on Linux, because it depends on glibc? Also, allocating a fixed 1000 byte region at the start of a program is not a "memory leak". In fact even glibc has tons of such "initial fixed cost" allocations - IIRC valgrind has built-in "suppression file" to ignore these allocations. (It would be a memory le…
So listing it makes sense in that context.
Earlier quoted context omitted.
> V and it's creator get a lot of flack here on HN and the criticisms are probably warranted. Hi fellow Penguin :D! I'm impressed by the creator's dedication here too, but he's clearly biting off more then he can chew - he's been saying that he's making a * Web framework * GUI framework * SQL ORM * A language that has a lot of promises - seriously checkout their list. * Github alternative * VIM alternative This stuff…
I'm not working on these alone :)
It pretty much has the (for me, subjectively) ideal features of a small, fast, and static programming language. I've been following it for a while and I'm pretty sure I'll find a good use for it soon!
Unfortunately this will probably run afoul of Git's trademark: "In addition, you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service without Conservancy's written permission. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a…
It would be a stretch but git has another meaning, which some find consistent with their perception of SWEs ;) https://www.merriam-webster.com/dictionary/git
V and it's creator get a lot of flack here on HN and the criticisms are probably warranted. However, I personally enjoy seeing them out here hustling and really trying to make their language succeed despite all the shortcomings. As someone who skews more apathetic, I enjoy seeing people driven by so much passion. Now, it's time for me to be one of those critics! It's easy to promote the speed and size of your github…
i was annoyed by the hyperbolic ambitious claims but if the guy and his friends pour out solid code then there's nothing else to say :) also they seem to aim at frugal fat free programming, i cannot not like that
Unfortunately, they don't.