dedsm

there are a couple of issues with "moving on", since the project is owned by pypa, it feels it should be the default for python projects, pipenv has a good idea, but in my opinion, a flawed implementation, and maybe all my issues are already resolved in those 600+ commits without release.

About the framing of the question, I think it's because of all the flame wars in the past when people criticized pipenv and maintainers took it a bit personal.

it's perfectly fine to use TimescaleDB alongside any regular tables.

CBS All Access is US-only AFAIK, so I don't think GDPR is a problem for them

Since quantum arrived, firefox developer edition is my browser of choice, and with the containers functionality it checks all my marks.

I owned a company that provided off-shore services to companies in the US, it worked perfectly.

If you are doing off-shoring, you really need to insist on the independence and the ability to speak up of the team, it doesn't work if you get yes-men, sadly that's the general case for India-based offshore companies

I've been using Gitlab CI for more than two months now, and it's incredibly simple to set up and really powerful specially with the integration with docker, also, self-hosted gitlab is free.

I also have Teamcity where I work and the comparison is not even fair, I set up gitlab in one day to serve as a continuous integration/deployment server

one of the issues I see with rails precisely is that most people won't ever know that 1.year is not a plain ruby method

The main difference is that Django does not rely on monkeypatching or magic methods, and for me the separation of concerns feels just natural in Django.

When I started with Rails it felt like magic, you didn't know why things worked.

I've always said Rails is good for short-lived build and forget projects, it's too "magic" for my taste.

I can't imagine what it must feel like to receive a mid-to-large sized Rails project to maintain.