gorthol

4 ms·

1.
by gorthol 9y ago
For example you could implement a credit system where anyone could be a creditor and vote (with their digital signature) what requests get approved. Then, once the money changes hands, the smart contract would automatically deduce que perio
2.
by gorthol 9y ago
I think it was "safe and performant without a GC" because both Nim and D have C++ level performance while being memory safe as any GCd language is.
3.
by gorthol 9y ago
D uses C calling conventions and struct layout so it's pretty trivial to call D code from D or vicecersa and link together, the only step added over C++ is writing an include file with the declarations of the stuff you want to call.
4.
by gorthol 9y ago
There is Vibe.d but I don't know if is as good as Go stdlib.
5.
by gorthol 9y ago
It depends. If you don't care about the specific error and just want to notify the failure up the stack or recovering is perfectly fine. A lot of Go code with the same intent just do a lot of "if err!=nil return err" which is
6.
by gorthol 9y ago
Actually, D suports "fibers" where you have a "Task". Then you can switch the task handler to another implementation and have Go-like M:N coroutines. The default handlers in the stdlib are only thread based or single-thr
7.
by gorthol 9y ago
Salaries in Madrid or Barcelona are more or less the same. Typical ranges are 18-28K for a junior, 36-52 for a senior and 42-70 for a lead. A CTO on a startup will depend a lot on the startup but 80-150k would not be uncommon for small ones
8.
by gorthol 9y ago
I still like D the most because of stability and how many features at your disposal, but Nim is a close second and is looking really good to.
9.
by gorthol 9y ago
Tried it recently. It still very far away from what I would call a decent Vim emulation.
10.
by gorthol 9y ago
I work on several languages professionally being the only one without exceptions Go and I don't see how its idiotic pattern of checking the value returned after every single call is a massive improvement on anything except masochism.
11.
by gorthol 9y ago
I've bursts. Sometimes I can work three days non stop and sometimes I strugle to write any good code. Luckily I've some margin to decide on what to work every day so I do documentation or unit/integration testing the days my
12.
by gorthol 9y ago
That how I would maximize developer productivity (but NOT working hours) if I owned a company: - Let them work at home, at any time they want. Just reserve some hours for meetings or stand-ups if you want. Don't control the hours, co
13.
by gorthol 10y ago
Upload your vimrc file and .vim directory to github and just do a clone on every new server.
14.
by gorthol 10y ago
I've been doing Python professionally for 13 years (among other languages, but Python is in the one I've used more). I like the language but I also hate some things (mainly, the GIL, the lack of static typing now lessened thanks t