Been a minute since I've looked for a job, and been even longer since I have been paid to write code in Java, but you might want to plug Spring in your search terms too. If memory serves, that was their big framework. From what I've seen Golang is almost exclusively used by devops and SRE types. I know the pay ceiling for SRE can be ludicrous, but the on call/fixing other people's broken shit nature of it made me shy away from that path.
Spring, Android, and Quarkus are the big 3 'frameworks' for Java. I fully expect Quarkus to start dominating over the next decade because it's absolutely insane.
There's a ton of companies looking for Java programmers. Mostly because you have a ton of shit that was written in the 2010s in Python/Ruby/Javascript that now is starting to show its age and becoming difficult to scale-up. IIRC Netflix recently decided to rewrite a ton of their backend web services in Java because of this and I expect there's more than just them in the 'big tech' sphere doing that (or opting for C#). If you only know basic Java from studying it in a CS program, I'd recommend learning Spring and building a few projects because it's a little bit different than just writing a Swing app for your CS3 final.
Scala also opens up some data science or machine learning opportunities, if you do that or have any interest in that. Haven't touched it myself but I've met people who use Scala for DS and ML.
My go-to for this kind of stuff is Datasette & the related SQLite-utils. It will have you up and running with full-text search and a nice web interface fairly quickly, though honestly I don’t know what the performance will be like with that amount of data (find out and let me know!).
Seems I use "lunr" for my text search. Which is an offshoot of "Solr" ( https://solr.apache.org ) which is probably closer to your needs.
Thanks! I'll check these out.
Probably a drop in solution would be best, but if you want to take a stab at a novel homemade solution you could try a matrix profile. I only suggest it because it's been on my to-do to fool around with one for too long.
Nawh Go isn't just devops or SRE, it's also used for heavy use API frameworks. Half my job right now is converting our PHP code into Go to leverage Go's concurrency and stop us exceeding the time limit on certain cloud jobs. It's a decent language for such web applications and should be something one is at least aware of if looking for a job in that field.
Java was popular in orange county when I worked there. You might also look to branch off into .net
That's interesting. I haven't heard of Go replacing PHP until you brought it up. I've played around with Golang for toy projects but mostly when I've seen it brought up its in comparison to languages like Rust and C++ as well as Python. I don't think Go is necessarily a good comparison to the first two languages but you can draw some reasonable comparisons to Python. I've had the displeasure of writing some PHP in the past and it was God-awful. Now that you've pointed out the connection between the two I think Go could replace a lot of the crappy backend code on the internet.
How’s your experience with Golang so far? I’ve tried a few things in it but the error handling kind of skeeves me out.
I'm not the person you are asking, but I spent this past December writing a tiny project (~1000 deployed loc), and my unwarranted opinion is that Go is a decent language to teach people the basics of software engineering: writing software, using source control, versioning, testing, coding conventions, simple debugging, deployments, and so forth. It has a rudimentary syntax and a basic type system, and with this it tries to be uniform with its interfaces (e.g.
len() for the length of containers, for being the only looping syntax, etc.) There's not much you need to learn about any aspect of it deeply in order to get okay working code, and that is by design. That being said, there were issues I had with the language that I don't see mentioned often elsewhere: forking existing projects and the community.go mod edit -replace This ended up with an error about module declares path as "x" but was required as "y" (stack overflow thread: https://archive.is/jgaE6), and after trying everything in that thread, I still couldn't resolve the issue. (I of course looked elsewhere, but pretty much every answer I found was the same as that thread). In the end I got it to work by doing a find and replace of the old URL over the entire project. I ended up trying to fork a different project at a later point and that had no issue when using the replace directive, so it might have been an issue with the first project or me, but the experience left a bad taste in my mouth.
Ocaml is great stuff. Yeah, I think language-wide lazy evaluation is overkill and fucks with your mental model of what's happening behinds the scenes.
Sexprs and lisps are good because you can rewrite the language at really low levels to implement new ideas.
Oh yeah the error handling is tedious as hell at times (the lack of try catch threw me when first learning it), but once you get your head around it being glorified variable checks it can yield some nicely streamlined code. I'm an OOP fanboy, but there's a lot of nice things under the hood with Go, especially if you have any familiarity with C and an interest in web design. Really easy to get a custom API framework off the ground with it for example.
I really think that try/catch is such an ugly wart on modern programming languages.
Ok returnval form or an Error err form. If you want to throw all caution to the wind and force a Result to return its Ok value (if you're confident that the code probably won't error), there's a function in the Result module that will do that and have the whole process panic if you're wrong.
Funnily enough this is one of the things I don't miss with try catch. For example the PHP generic Exception class works fine and dandy (mostly) for error handling, but if for some reason you go with the Throwable superclass you can pick up false positives, miss logs, and otherwise have a miserable debugging experience. A fellow dev thought he'd be imaginative and exclusively use Throwable without knowing this, leading us down multiple rabbit holes thinking sensitive code was seriously broken until we picked up on his error handling strategy. Gave me a much better appreciation for more rigid error handling lol.
A better "first language" than Python, by a long shot. I'd also argue TypeScript being a good first language because many jobs require TS and you're forced to use types, which should be standard.
Especially if you're trying to land that sweet $300K/year job at Jane Street.