Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
arthursilva
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
31.
▲
by
arthursilva
11y ago
Probing is great but you have to be careful in a situation where deletes are common. Robin hood hashing is a great solution for those.
32.
▲
by
arthursilva
11y ago
Or even better line.split(' ').filter(|word| matches(word, search)).count()
33.
▲
by
arthursilva
11y ago
Impressive, specially considering the `lack` of allocations and that the compiler detects the bug on the parallel quick sort implementation.
34.
▲
by
arthursilva
11y ago
Pretty good for a first release, the docs look great already.
35.
▲
by
arthursilva
11y ago
I don't want to be that guy, but annotations at the end of the line, seriously? All the @public at the end of the function headers really hurt the eye. I think there's a reason 90%+ of the languages has either it above the declara
36.
▲
by
arthursilva
11y ago
I'm not 100% familiar with the internals, but I think it's safe to say that the persistence part is asynchronous in order to reach the low latency goals of the system.
37.
▲
by
arthursilva
11y ago
Secondary store is more like a backup, not for spilling.
38.
▲
by
arthursilva
11y ago
It's a very useful thing in Rust so it should be the same in C++, without the ownership constraints though it'll very unsafe.
39.
▲
by
arthursilva
11y ago
Impressive detailed writing.
40.
▲
by
arthursilva
11y ago
> Modern C++ ..., and would have been much more productive than go. This is definitely not correct. Any GC language with even the most basic packaging support (go get etc.) is miles ahead of C++ productivity wise.
41.
▲
by
arthursilva
11y ago
At the time it would suffer from the same problems as Golang (GC) and Rust (not stable, few libraries around).
42.
▲
by
arthursilva
11y ago
They started the project long before Rust was stable and even today the Rust ecosystem is still lacking some libraries (understandably). The performance potential is real but not free as the productivity isn't as good.
43.
▲
by
arthursilva
11y ago
It's competing with Golang, D and Crystal, also with C++ and Rust to some extent. Except Crystal every other language in this list have some kind of corporate backing and is experiencing orders of magnitude more growth.
44.
▲
by
arthursilva
11y ago
Is there a good GUI wrapper for gdb or lldb?
45.
▲
by
arthursilva
11y ago
What a great language, seriously. Unfortunately I have no hopes that I'll gain any significant traction.
46.
▲
by
arthursilva
11y ago
Great performance numbers, specially seeing that it only uses a single thread.
47.
▲
by
arthursilva
11y ago
Actually, yes.
48.
▲
by
arthursilva
11y ago
Very excited for BRIN indexes!
49.
▲
by
arthursilva
11y ago
This would be a great addition. After non lexical lifetimes this is probably the most awaited post-1.0 feature.
50.
▲
by
arthursilva
11y ago
Welcome improvements! I guess I'll be able to compile all my code on stable 1.4 judging by https://github.com/rust-lang/rust/pull/28339 .
51.
▲
by
arthursilva
11y ago
I'm fairly sure this is the same technique employed by pg_tgrm. There's a new version (1.2) floating around the mailing list that's BLAZZZING fast!
52.
▲
by
arthursilva
11y ago
Yep and it makes total sense, there's not a huge changelog since there's a release every 6 weeks. If there were ground breaking changes we'd see more discussion though.
53.
▲
by
arthursilva
11y ago
Can't we discuss the new/changed/deprecated items?
54.
▲
by
arthursilva
11y ago
That's a nice article(s). Gankro, the author, is very active in Rust, specially in data structures.
55.
▲
by
arthursilva
11y ago
Looks pretty good. The storage backend must have come a long way since the last time I checked it, at the time it crashed every time I accessed it from multiple threads.
56.
▲
by
arthursilva
11y ago
I wish they targeted py3 from the beginning, by the time they get it usable to the mainstream developer (if...) py2 will be lagging a lot of features. That kinda sucks :/
57.
▲
by
arthursilva
11y ago
I think it's a great usability improvement nonetheless. Sometimes you just need C* easy scalability (at least compared to the alternatives)
58.
▲
by
arthursilva
11y ago
Breaking backwards compatibility is dangerous in any major project. Hopefully the community will migrate reasonably fast and this don't turn up the same as Python 3.
59.
▲
by
arthursilva
11y ago
aiohttp is based on the stdlib event loop, it's likely to get much more support for async stuff. You can always plug gevent into Falcon, but you'll need a bit more luck finding compatible libraries though.
60.
▲
by
arthursilva
11y ago
Great product, besides the great overall offering it's a nice alternative to bitbucket when you need free private repos.
More ›