They should definitely update UI of the website.
Why, what's wrong with the UI?
arXiv moving from Cornell servers to Google Cloud
11–20 of 178 posts
Re: arXiv moving from Cornell servers to Google Cloud
#12They should definitely update UI of the website.
Why? I'd argue most users of that site like the skeleton ASCII-style UI, which is also fast (at least when compared to the today's JS-riddled sites).
Re: arXiv moving from Cornell servers to Google Cloud
#13Job 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.
Re: arXiv moving from Cornell servers to Google Cloud
#14[deleted]
Re: arXiv moving from Cornell servers to Google Cloud
#15Job 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.
It’s still 100% LaTeX in my fields (AI, ML, robotics, telecom).
Re: arXiv moving from Cornell servers to Google Cloud
#16I'm sure many are going to hate on this, but a simple k8s setup (just container+deployment+ingress) is going to be good for preventing vendor lock in. Too bad it's US only, devops is actually a good role for full remote setups. If you can't make it work asynchronously across timezones you are doing it wrong :)
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.
Re: arXiv moving from Cornell servers to Google Cloud
#17They should definitely update UI of the website.
Why? I'd argue most users of that site like the skeleton ASCII-style UI, which is also fast (at least when compared to the today's JS-riddled sites).
I am curious too as to what needs changed as well.
It appears functionality efficient, well organized, and fast as you observed.
Re: arXiv moving from Cornell servers to Google Cloud
#18> 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 sold them CloudRun)? Anyway, goodbye simplicity and stability, hello exorbitant monthy costs for the same/less service quality. Would love to be wrong.
Re: arXiv moving from Cornell servers to Google Cloud
#19> 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…
I think this is more likely a move to prevent Cornell funding from getting tied up with dictations about what gets published.
But in all likelihood someone was probably just like "we're tired of doing ops on 2 decades old stacks"
Re: arXiv moving from Cornell servers to Google Cloud
#20> 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)