IMO it doesn’t matter, learning go from Java should not be what excludes you from an offer. Of course if the employer has a choice between two otherwise even candidates then maybe it’d help.
I think the problem is working with both in a production environment is what is going to set you apart.
I’d say learn a language that’s really different like a functional or a logic language.
Otoh I’ve not been interviewing lately so maybe my take is totally off base
Go pay rates are lower? Not in my experience, any source for this?
On osx I use alt (option I believe) for copying from the terminal, and that carries over with nvim. Admittedly I tend to use pbcopy for larger amounts of text
Ctrl+c works in terminal and nano but not neovim?
Search for “copy from nvim to clipboard” you should get something right away.
I’d your highlighting text and copying that then it’s your terminal not neovim
Go has an idiom like so https://github.com/hashicorp/vault/blob/8da4386caceb3fdfaa90074bb29c77e8a99c7dad/api/kv_test.go#L27, when i mention name i’m referring to that string.
I get what your saying, we’ve all worked in terrible code bases, i’ve also worked in code bases where this kind of article was enforced. What you wound up with was something that was very wordy.
Almost always use parameterized style tests, always have a name field, I don’t use full sentences tho, that seems like too much. Don’t believe I’ve ever seen a test like that either
These toy examples feel like strawmen to me
For this kind of thing i usually go by popularity (active repo/popular repo), mostly to have the most other people in your boat. It doesn’t always work but generally if other users have to migrate at least you can ask them questions.
On the face of it i’d go with the csi driver version, only because we use alternative csi drivers ourselves, and haven’t seen any issues (ours are pretty aws vanella though).
We use storage classes (for our drivers) the “dynamic provisioning” section of https://juicefs.com/docs/csi/guide/pv, you’ll need to make one of those, then create a statefulset and mount the pv in there.
I do find statefulsets to be a bit of a not as well supported part of kubernetes, but generally they work well enough.
I guess i shouldn’t have answered, I do have experience with multiple storage-classes, but none of the classes you mention (so like i don’t really know anything about them). I envisioned you dealing with pod level storage issues and thought that’d be something most programs would have lots of difficulty dealing with, where as a more service oriented approach would expect remote failures (hence the recommendation).
All of the things you mentioned don’t seem like they have provisioners, so maybe you mean your individual nodes would have these associated remote fs’. At that point i don’t think kubelet cares, you just mount those on the machines and tell kubelet about it via host mount
Oh shit look there’s a CSI driver for juicefs https://juicefs.com/docs/csi/introduction/, they kinda start out recommending the host mount https://juicefs.com/docs/cloud/use_juicefs_in_kubernetes/.
We make some use of PV’s but people i find my team often tend to avoid them.
I probably should have shut my mouth from the start!
My gut says go multi cluster (or not) at that pointbut treat the remote as a service, have a local container be a proxy
Hate this title, how about:
“A novel by author Lena McDonald, accidentally leaves AI prompt in published version.”
I had to containerize an older java app. It sucked, java would take all the memory you gave it regardless, so it was hard to determine memory requirements/limits. It had pretty slow start although this wasn’t an issue for us, logging formatting was a pain. All this was overcome (not by upgrading), it was just a pain.
I suspect this isn’t true of modern java though - I’d suspect with the hype kubernetes went through a few years ago that it’s just fine now a days.