Re:Xapiand: A fast, simple, modern search and storage engine
by ddorian43 on Tuesday January 15, 2019 @05:01AM
(#18910024)
Yeah but it's golang, so it's kinda like java, so I see no pros in it TBH.
[ Parent
| on HN ]
Re:Xapiand: A fast, simple, modern search and storage engine
by hardwaresofton on Tuesday January 15, 2019 @05:50AM
(#18910226)
There are a lot of differences between Golang and Java. As much as I dislike writing Java when I have a choice, the JVM (with Java or whatever else on top) is a very capble tool... Could you explain what you mean by there being "no pros"?
Are you maybe trying to get at the difficulty of tuning the JVM?
Re:Xapiand: A fast, simple, modern search and storage engine
by ddorian43 on Tuesday January 15, 2019 @05:59AM
(#18910264)
rust/c++/c has no gc and better performance/efficiency compared to java/golang. so you get excited for a library/db in those languages
golang is kinda a java alternative. a db/search-engine in java/golang kinda sucks (it will under pressure)
Re:Xapiand: A fast, simple, modern search and storage engine
by hardwaresofton on Tuesday January 15, 2019 @10:03AM
(#18911548)
While I definitely agree with you on the broad strokes of the differences between rust/c++/c and java/golang (representing languages without runtimes and those with them respectively), I'd say that golang is a bit more than a java alternative if we consider more than whether a runtime is included or not.
Of course, if the only consideration is whether a runtime is there or not, golang is identical to java but also identical to common lisp or maybe even interpreted languages like python.
I do want to point out that it's possible to write horribly buggy code in c++/c (less so in rust :), which can tank performance/efficiency when compared to a java/golang program. All things considered though, the ceiling on performance and efficiency is of course higher in manual memory management land.
Thanks for clarifying what you meant!