Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
biokoda
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
1.
▲
by
biokoda
8y ago
Schemas are per actor type and you can have many types. Actors are active or inactive. When you run a query against one, when it becomes active it will check if schema has changed and apply that before processing any query.
2.
▲
by
biokoda
8y ago
From that point of view yes you are right. There is a ton of nuance in CAP. Usually in these discussions the CAP question is if it is eventually consistent or not.
3.
▲
by
biokoda
8y ago
It's raft; thus firmly CP.
4.
▲
by
biokoda
9y ago
Yes a user space thread pool which is what node.js does on top of libuv.
5.
▲
by
biokoda
9y ago
> Waiting 200ms for the database + an additional 20ms for rendering Those are pretty awful numbers. https://blog.gigaspaces.com/amazon-found-every-100ms-of-late...
6.
▲
by
biokoda
9y ago
History has proven that anyone no matter their abilities is going to shoot themselves in the foot regularly while using C. Some just less frequently.
7.
▲
by
biokoda
9y ago
> Depending on how you define "big changes". The way every reasonable person would. This release being the obvious example.
8.
▲
by
biokoda
9y ago
That is entirely untrue. Releases are regular, big changes are anything but.
9.
▲
by
biokoda
9y ago
> Well, someone probably said the same about Go or React-Native when they first came out too RN came from a giant company that uses it in its core product. Big difference.
10.
▲
by
biokoda
9y ago
Yes SQLite with type check constraints.
11.
▲
by
biokoda
9y ago
io_ syscalls only really work on XFS and require O_DIRECT which means kernel is not caching anything. Unsuitable for web servers.
12.
▲
by
biokoda
9y ago
Changing the number of cores given to a VM is not so uncommon.
13.
▲
by
biokoda
9y ago
> There's no middle ground. Not at all. This is what the ? operator is for (was try! before). The idiomatic rust way is to have your own Error type that implements From for other Error types that you may encounter (io::Error, Utf8Er
14.
▲
by
biokoda
9y ago
Overly complicated
15.
▲
by
biokoda
9y ago
It's far from clear if tokio is not a dead end.
16.
▲
by
biokoda
9y ago
You can write low level code. Tier 1 platform list is very short however. https://forge.rust-lang.org/platform-support.html
17.
▲
by
biokoda
9y ago
A huge win compared to C is fearless refactoring. Making changes to an existing codebase in C is a minefield. Refactoring in Rust is a breeze.
18.
▲
by
biokoda
9y ago
The relatively low portability of rust programs is definitely one of its largest shortcomings.
19.
▲
by
biokoda
9y ago
The point of Erlang is that it makes writing robust distributed systems easy and fast. The language itself is tiny. Scala on the other hand is not remotely small and easy to understand.
20.
▲
by
biokoda
9y ago
Lots of companies (like us) use it as basically a replacement for C/C++. They just don't discuss it much.
21.
▲
by
biokoda
9y ago
Anyone needing that can also extract tikv's raft implementation. It's actually quite easy.
22.
▲
by
biokoda
9y ago
One plus is the best choice. Great hardware, reasonable price, up-to-date Android no horrible skins on top of stock.
23.
▲
by
biokoda
9y ago
C/C++ compiler will compile your code if it is correct. Rust will not compile code if it can detect that it will not work or it is not safe even though the syntax is correct. It can guarantee the program is memory safe (double free, u
24.
▲
by
biokoda
9y ago
A single repo can have lots of crates
25.
▲
by
biokoda
9y ago
> The only problem is that the compiler is very slow now, so it doesn't scale to large code bases The way of working with that is use cargo check command which is much faster and splitting your problem into multiple crates so you do
26.
▲
by
biokoda
9y ago
This is like reading criticism of Erlang which we use. A bunch of people (the vast majority of which never shipped anything in it) have plenty of arguments against it, those of us that actually use it love it to bits. Rust is productive, ef
27.
▲
by
biokoda
9y ago
Anycast is pretty standard.
28.
▲
by
biokoda
10y ago
> When you're doing voip you're doing so over UDP because TCP has far too much latency to be agreeable, Lots of wifis, corporate especially block all UDP traffic. Sometimes they even block all non http/https traffic. Apps
29.
▲
by
biokoda
10y ago
VOIP calls are very sensitive to intermittent connectivity. Sometimes wifi will work in batches. No packets will get through for a few hundreds of milliseconds (or seconds), then they will get sent all at once. Sometimes UDP traffic is bloc
30.
▲
by
biokoda
10y ago
Because a Rust library is safer, equally efficient, faster to develop, easier to build and can expose a C interface.
More ›