Flask (Python) for super simple stuff with no db (I have a custom ldap user and groups manager for example) with semantic ui frontend and crude html.
Ktor in kotlin for any API thing that needs to last.
Spring boot in kotlin for stuff that require auth and db with vue.js in front using type script. (Makes developing one week viable products doable)
Bioinformaticians use Python,R,Java,Julia,Groovy,Js and more (I use kotlin and python mostly but that's in a niche of bioinformatics I don't touch genes nor proteins)... Same as in software dev, there are a lot of beliefs. So you have the club of the js people that hate java, the club of pythoners that hate R, and people that just use what allow them to solve their problem and they are the ones that achieve the most but also that you hear about the less.
I wish we would have the equivalent of the language servers but for collaborative editing. That way you could edit with one user in emacs, one in vscode, one in intellij etc.
I once used something called Floobits[1] that was capable of this. In practice collaborative editing wasn't that much more useful vs screen sharing and the additional constraints of managing Floobits workspaces didn't make it worth it for us.
I did pair programming on XEmacs in the 90's by opening a new frame on a second X server. It worked surprisingly well as long as both people stayed out of the minibuffer.
That looks nice, however for those interested, only the plugins are opensource and usage is not free. The good thing is that it shows what is possible.
i find collaborative editing most useful for online docs, like wiki pages, etc. not having to worry about locking makes a big difference when editing is fast paced
That is such a great idea. The need for a service like overleaf to provide an entire front-end + text editor is just ridiculous when there is already so much existing software out there. Multiple editors with realtime shared data + shared previewing tools totally should be a thing.
Memory initialization is really slow. On servers there is that, plus the fact that you usually don't want to do a fast ram check like you can afford on a laptop. Add to that initialization of the remote management, SAS/raid,... A server does a pretty thorough quality control when it boots. Also if you have a lot of mechanical drives, there may not be enough power budget to spin them all up at the same time, so they start progressively.