Hacked News

Comments from Hacker News https://ift.tt/30l28an via

Article URL: https://github.com/caseykneale/VIMKiller Comments URL: https://news.ycombinator.com/item?id=23306514 Points: 19 # Comments: 6 from Hacker News: Front Page https://ift.tt/30l28an via

Comments from Hacker News https://ift.tt/2TE07DZ via

Comments from Hacker News https://ift.tt/36iiwLP via

Article URL: https://www.nytimes.com/2020/05/25/opinion/online-college-coronavirus.html Comments URL: https://news.ycombinator.com/item?id=23307202 Points: 14 # Comments: 7 from Hacker News: Front Page https://ift.tt/2TE07DZ via

Article URL: https://github.com/tootsuite/mastodon/pull/13820 Comments URL: https://news.ycombinator.com/item?id=23307053 Points: 23 # Comments: 2 from Hacker News: Front Page https://ift.tt/2TA4yje via

Comments from Hacker News https://ift.tt/2TA4yje via

Comments from Hacker News https://ift.tt/3gjGFGi via

Article URL: https://blog.pragmaticengineer.com/the-developer-culture-test/ Comments URL: https://news.ycombinator.com/item?id=23305460 Points: 37 # Comments: 12 from Hacker News: Front Page https://ift.tt/3eePZdE via

Comments from Hacker News https://ift.tt/2APGwKu via

Article URL: https://sod.pixlab.io/ Comments URL: https://news.ycombinator.com/item?id=23306480 Points: 14 # Comments: 2 from Hacker News: Front Page https://sod.pixlab.io/ via

Comments from Hacker News https://ift.tt/2B1zCCa via

Comments from Hacker News https://sod.pixlab.io/ via

Comments from Hacker News https://ift.tt/RPC5O1 via

Comments from Hacker News https://ift.tt/3eePZdE via

Article URL: http://lea.verou.me/2020/05/todays-javascript-from-an-outsiders-perspective/ Comments URL: https://news.ycombinator.com/item?id=23306382 Points: 8 # Comments: 1 from Hacker News: Front Page https://ift.tt/2B1zCCa via

Article URL: https://tanay.substack.com/p/lies-damned-lies-and-stock-based Comments URL: https://news.ycombinator.com/item?id=23306104 Points: 41 # Comments: 2 from Hacker News: Front Page https://ift.tt/2TDTSQA via

Comments from Hacker News https://ift.tt/2TDTSQA via

Comments from Hacker News https://ift.tt/3gniUNK via

Comments from Hacker News https://ift.tt/2X1S324 via

Comments from Hacker News https://ift.tt/2yvkj3D via

Article URL: https://www.sciinc.com/remotevms/vms_techinfo/vms_news/OpenVMSOnX86-64.asp Comments URL: https://news.ycombinator.com/item?id=23305598 Points: 4 # Comments: 2 from Hacker News: Front Page https://ift.tt/3gniUNK via

A common way of deploying a web application database at scale is to setup a MySQL or Postgres server, create one table for all customers, and have an account_id or owner_if field and let the application code handle security. This makes it easier to run database migrations and upgrade code per customer all at once. I’m curious if anybody has taken the approach of provisioning one database per account? This means you’d have to run migrations per account and keep track of all the migration versions and statuses somewhere. Additionally, if an application has custom fields or columns, the differences would have to be tracked somehow and name space collisions managed. Has anybody done this? Particularly with Rails? What kinda of tools or processes did you learn when you did it? Would you do it again? What are some interesting trade offs between the two approaches? Comments URL: https://news.ycombinator.com/item?id=23305111 Points: 26 # Comments: 31 from Hacker News: Front Page https...