Earlier quoted context omitted.
You deal with emergencies with international on call rotation?
"Follow the sun" rotations are a common way to handle 24h oncall rotations. Three regular shifts (8 hours of work plus some lunch break that gives you time for a short overlap at the beginning/end of the shift) during that region's local daytime hours, in three different regions with time zones roughly 8 hours apart. That way nobody has to work nights and you still get 24/7 coverage.
arXiv moving from Cornell servers to Google Cloud
21–30 of 178 posts
Re: arXiv moving from Cornell servers to Google Cloud
#22Re: arXiv moving from Cornell servers to Google Cloud
#23Re: arXiv moving from Cornell servers to Google Cloud
#24> We are already underway on the arXiv CE ("Cloud Edition") project... replace the portion of our backends still written in perl and PHP...re-architect our article processing to be fully asynchronous,.. we can deploy via Kubernetes or services like Google Cloud Run...improve our monitoring and logging facilities Why do I smell someone from G was there and sold them fancy cloud story (or they wanted VMs and reseller s…
They are already using VMs but one of the things it'll do is:
> containerize all, or nearly all arXiv services so we can deploy via Kubernetes or services like Google Cloud Run
And further state:
> The modernization will enable: - arXiv to expand the subject areas that we cover - improve the metadata we collect and make available for articles, adding fields that the research community has requested such as funder identification - deal with the problem of ambiguous author identities - improve accessibility to support users with impairments, particularly visual impairments - improve usability for the entire arXiv community
Re: arXiv moving from Cornell servers to Google Cloud
#25Crap, there goes privacy.
Re: arXiv moving from Cornell servers to Google Cloud
#26> We are already underway on the arXiv CE ("Cloud Edition") project... replace the portion of our backends still written in perl and PHP...re-architect our article processing to be fully asynchronous,.. we can deploy via Kubernetes or services like Google Cloud Run...improve our monitoring and logging facilities Why do I smell someone from G was there and sold them fancy cloud story (or they wanted VMs and reseller s…
This.... I bet arXiv was run on server hardware costing under $10k before... And now it'll end up costing $10k per month (with free credit from Google which will eventually go away and then arXiv will shut down or be forced to go commercial)
Re: arXiv moving from Cornell servers to Google Cloud
#27Re: arXiv moving from Cornell servers to Google Cloud
#28Re: arXiv moving from Cornell servers to Google Cloud
#29> We are already underway on the arXiv CE ("Cloud Edition") project... replace the portion of our backends still written in perl and PHP...re-architect our article processing to be fully asynchronous,.. we can deploy via Kubernetes or services like Google Cloud Run...improve our monitoring and logging facilities Why do I smell someone from G was there and sold them fancy cloud story (or they wanted VMs and reseller s…
Re: arXiv moving from Cornell servers to Google Cloud
#30Job opening for the rare perl+latex hackers.
Perl is becoming rare, but is LaTeX also falling out of use for technical papers? Most of the scientific and CS papers I’ve seen lately still seem to use it, even those coming from Microsoft. That said, it's often generated via Org-mode or WYSIWYG tools these days.
All the conferences I'm looking at have word and latex templates. Word clearly isn't going to replace LaTeX for many reasons.
Truth to be told: As long as you're given a template and have to stick to that template, LaTeX is all you could ever want. With overleaf there's barely a tooling learning curve either.