• 6 Posts
  • 115 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle


  • So what do they make of people like me who who use Linux on a Mac, with e.g. Colima or Rancher desktop - doing cloud/kubernetes/python development? I moved to a Mac a couple of years ago after 20 years of using Linux as my daily driver because frankly Bluetooth audio on Linux sucks and because I was tired of getting endless different video conference / screensharing solutions working at short notice for interviewing.



  • Ok. I missed which sub I was in, sorry. There is a Linux desktop Jellyfin app but I haven’t used it myself. In my own case I am running Jellyfin on Linux. I use various clients, including web browser (laptop), Android and Roku (TV) and find it works really well. In the past I had tried with the ‘connect directly to the server’ route with XBMC (as Kodi was called then) and it never worked well, with similar issues those described in other comments.







  • You could consider

    • Cord: had some contact from companies leading to interviews but also some contact me and then ghost on response
    • Otta: more manageable search than LinkedIn
    • Hackajob: been a waste of time for me

    Linkedin is still the big gun. Really don’t like how they game everything around job hunting, or the endless sea of Indian recruiters from Hyderabad pretending to be in UK/USA who can barely speak English and ‘have a requirement…’ but clearly have no concept of geography.










  • GitLab just doesn’t compare in my view:

    To begin with, you have three different major versions to work with:

    • Self-Hosted open source
    • SAAS open source
    • Enterprise SAAS

    Each of which have different features available and limitations, but all sharing the same documentation- A recipe for confusion if ever I saw one. Some of what’s documented only applies to you the enterprise SAAS as used by GitLab themselves and not available to customers.

    Whilst theoretically, it should be possible to have a gitlab pipeline equivalent to GitHub actions, invariably these seem to metastasize In production to use includes making them tens or hundreds of thousands of lines long. Yes, I’m speaking from production experience across multiple organisations. Things that you would think were obvious and straightforward, especially coming from GitHub actions, seen difficult or impossible, example:

    I wanted to set up a GitHub action for a little Golang app: on push to any branch run tests and make a release build available, retaining artefacts for a week. On merging to main, make a release build available with artefacts retained indefinitely. Took me a couple of hours when I’d never done this before but all more or less as one would expect. I tried to do the equivalent in gitlab free SAAS and I gave up after a day and a half- testing and building was okay but it seems that you’re expected to use a third party artefact store. Yes, you could make the case that this is outside of remit, although given that the major competitor or alternative supports this, that seems a strange position. In any case though, you would expect it to be clearly documented, it isn’t or at least wasn’t 6 months ago.