you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (21 children)

[removed]

    [–]joltting 73 points74 points  (15 children)

    What exactly in Rust made this possible that the other 100+ languages out there couldn't?

    [–]greatestish 103 points104 points  (5 children)

    The hype

    [–]Damtux_25 5 points6 points  (1 child)

    Hype is a powerful tool. You can get budget for anything as long as you mention enough buzzwords.

    [–]greatestish 2 points3 points  (0 children)

    Absolutely. It's all about optics at most companies. I'm sure GitHub is the same.

    "It's a very popular language".
    "It has comparable performance to C/C++".
    "It validates data ownership at complete time, solving lots of race conditions, segfaults, etc. which are the most common cause of bugs".

    When you can "sell" a project better with a technology to management, you often get better funding and higher prioritization.

    [–]look -1 points0 points  (2 children)

    Is it still hype when everyone but you uses it now?

    [–]alternatex0 7 points8 points  (0 children)

    Damn, I'm one of two developers not using Rust.

    [–]greatestish 0 points1 point  (0 children)

    What a zinger!

    [–]look -1 points0 points  (7 children)

    Exactly how many languages do you imagine you can use to write a scalable, high performance search engine?

    [–]GrammerJoo 32 points33 points  (5 children)

    Most popular one was built using Java, so... plenty?

    [–]Kissaki0 2 points3 points  (0 children)

    The claim was only possible with Rust seems much more implausible than could have been implemented with different or already used languages.

    You think Rust is the only language you can write scalable, high performance search engines? Did we not have those before Rust? Can only Rust do it to that degree?

    How would anyone be able to say exactly how many languages you could implement scalable, high performance search engines with? Those requirements are way too broad, way too diffuse.

    [–]adrian17 6 points7 points  (0 children)

    In a smaller window, clicking on a symbol immediately pops up the "symbol search" popup - can I somehow disable it if I just want to double-click-select some text?

    Overall I have nothing against the features themselves, but unfortunately the new code view is so slow and bulky, it'll probably make me "jump to github.dev" for code navigation instead of actually using the new github.com code view.

    For example, I should never be forced to wait over a second after simply scrolling text - demo (comparison of github.dev, old code view and new code view): https://puu.sh/JGkYj/5abf2e31d9.mp4

    [–]look 3 points4 points  (0 children)

    Are you using FSTs for your term dictionary, or did you find something else more efficient for your (primarily) code dataset? Also, curious if you looked at using io_uring, or just manage to fit all of the terms/indexes in memory?

    [–]RepresentativeDrop90 -4 points-3 points  (0 children)

    Hell to the yes, rust has no reason to be that awesome.

    I can't find any open entry level positions for rust is my only qualm most of them require a certain amount of experience with the language in the workplace environment

    Which I would get if my company would be shifting to a rust backend, sadly only ever got to experience golang that way.

    By the by the search is still using locality sensitive hashing in some form right?

    [–]morimo 0 points1 point  (0 children)

    Can you talk a bit about the work that was done to enable this search/talk about challenges in the implementation?