Yes, it's down again

I marvel at the proficiency with which Microsoft tears down every piece of software it touches nowadays.
- I'll get downvoted for this, but I think they take good care of github and Minecraft. As for the rest though... not so good.
  
  If with "good care" you mean "the core functionality is up and running most times", yes
  
  I haven’t played Minecraft for a while, but I was under the impression that Microsoft was progressively turning the Bedrock version into a microtransaction hellscape. If I’d have to reluctantly commend Microsoft for anything, I’d rather go for Visual Studio Code.
  
  ... Didn't they revoke the Minecraft licenses people purchased because they didn't manage to migrate their Mojang accounts to Microsoft accounts in a short amount of time?
  
  Oh yeah, Minecraft fans will tell you just how much they love their handling of it...
  
  They deliberately removed code search for not logged in users almost immediately. Just recently they removed cloning without an account, so now updating my computer requires signing in to github.
  They have been awful stewards.
- Look what they just did to Notepad!!!
  MONSTERS!!!!!

My company owns their infrastructure and we don't have issues like this and our production servers are working like oiled machines and yet they want to move to 3rd party cloud services for reasons that have yet to be explained
- a brief conversation:
  Cloud good, very good for dynamic sizing up and down.
  but sir we don't need to scale up and down for our business.
  but cloud good.
  
  I'm worried that when the bean counters see the price difference between AWS and self hosted stuff they'll find AWS more expensive and we will have to deliver a year's work for 10 scaled agile teams again, but in our machines
- I'm guess you have a fully staffed infrastructure team team, so the reason that has yet to be explained is that they want to downsize that team.
  We use cloud services because we have never had a fully staffed infrastructure team.
- The explanation is guys in marketing buying fancy lunches and rounds of golf for the guys in C-Suite (Source: A tired IT admin that has had to talk his management team off of this cliff due to fancy tech demo dinners from unsolicited cloud/software companies)
- The fewer magic blackboxes are around, the
  (happy variant) easier it is to train new people and the less mental burden there is on existing staff
  (sad variant) easer it is to fire people.

Reliance on external services to build and test code is absolutely braindead design
- absolutely braindead design
  You've clearly not worked at my company
  Azure devops and pipelines but only that and nothing more (not allowed to deploy to azure/microsoft stuff)
  ONLY deploy cf to Aws
  write primarily c# for all services, even our websites (iis 7, cshtml)
  only exception is a new mobile app which is written in React Native, but even that is more bloated than the windows 11 start menu. It's the only exception.
  Projects are generally so poorly maintained, we're still using bootstrap 4, outdated framework versions. I know personally there's a windows server 2003 chugging along somewhere.
  "we know about this (medium) bug/vuln, we can work around it. Just add this new feature to the codebase" but imagine this times 100. I quietly fix the bugs because i wouldn't be able to live with myself otherwise.
  the projects are 95% boiler plate for the simplest of tasks (curl a thing and pass it to another service has about 40 different classes), no processing...
  "Aws Q first" company where none of the developers actually get access to write code with. Explicitly forbidden from using copilot: "it'll use our code for their training"... right. Won't someone think of our flawless, industry standard code. Also, that's not how that works.
  security none existsnt. Aws security tools used to scream at you every time you open the aws console. Solution at the company was to restrict views to those pages so (most) people don't see the security/vuln reports. To get reports, you'd have to ask cybersec.
  most developers are in a constant state of burnout.
  There's more but i'd violate my NDA too much at that point.
  we're expected to hit 1/2 b gbp profit in couple years
  i think we, the developers at our company, are the biggest clowns in the entire IT industry. And yeah, we're reponsible for your gov ids & loan applications.
  ggwp
  
  security none existsnt. Aws security tools used to scream at you every time you open the aws console. Solution at the company was to restrict views to those pages so (most) people don't see the security/vuln reports. To get reports, you'd have to ask cybersec.
  Not going to lie, that is hilarious. And forget red flags, you have a whole squadron of semaphores right there.
  
  Like I said, braindead
- Sometimes our internal CI tools break and I can't build either. I think GitHub actions syntax is actually valid in forgejo as well so I don't really think it's a problem.
- No, that's actually genius.
  How else are you supposed to get random paid break-time, which the boss can't stop you from even if a crunch is going on?
- It's not like internal build servers are 100% reliable, scaleable and cheap though. Personally I've found cloud based build tools to be just a better experience as a dev.
  
  Jesus Christ, can you not even conceive of the idea of building on your own machine?

What do they mean by "Carry On."?
It's already over. The guy in the left had both, the High Ground and the higher posture.
- He's liable to get top-heavy and just fall over. Guy on the right has a nice center of gravity.
  
  "But... but... My high ground 😭 "
  ~ Obi-Wan Kenobi
- In this case it means "nevermind".

Someday soon: Claude is down
- What are you planning? Downing the Dutch songfestival singer Claude? /s

This thread pivots hard from version control jokes into a somber discussion of the future of Minecraft.
I have found my people. You all are amazing.

ackshually you can run most of the CI locally
- Don’t tell the boss, jerk.
- Doesn’t matter if the mechanism that checks the repo and sends the trigger message to the runner is down.
  
  how does that affect running the CI locally? I don't mean triggering the cloud CI manually, I mean running the commands manually.

People forget git is a DVCS, you can send PRs to each other without relying on Github.
- Wait what
  
  Yeah dog pretty much everything on the github website is an interface to display info held in the .git folder of the website.
  Thats how theres github, gitlab, gitea, gitlab, forgejo, etc etc. There are even applications you can download to visualize info in git that run on your local machine, and only see youe local filesystem.

Interesting - I've been retired a few years but the way we used github was git commit, git push, usually at the end of the day. How has the workflow changed so people constantly need it to do any work?
- Unfortunately, the ecosystem around github has evolved so that most folks centralize their testing and deployment code into being executed on github infrastructure. Frankly a perversion of the decentralized design of git.
  Fortunately for my team, it doesn't matter because our process requires stuff that can't be done from github infrastructure anyway, so we have kept the automatic testing and deployment on premise even as github is the 'canonical' place for the code to live.
  
  Wow, that's such a classic Microsoft approach - "Embrace and Extend."
- GitHub added CI/CD pipeline functionality (called GitHub Actions). If it's down I can't merge code or deploy code anywhere since company policy requires analysis builds to run, and our deploys use the GitHub Actions to ship the code.
- GitHub actions is crazy convenient, but it's a huge pain to run a copy locally. I try not to depend on it too much, but sometimes it is simplest to just go refill my coffee while it figures itself out.
  (And it's almost never down. This week was unusual, to me.)
  
  I still use github for personal projects but have never looked into what the Actions do, since github serves my minimal needs as-is. But it also did when I was working. I would think if people find that depending on certain features ultimately disrupts their work, the smart thing would be not to use those features.

There's a reason we value the local development environment.
You can run everything locally, the only use for the cloud environment is for CD.
- I'll be honest. I just enjoy seeing my auto updater script work whenever I push to main and the Web page updates itself. FEELS SO GOOD TO JUST DO A PUSH AND HAVE YOUR CHANGES UP IN 3 MINS.
  
  Well yeah!
  That's the CD part :)
  We're rolling the same thing, except with all our cloud infrastructure, our code, and various integrations.
  Automatic deployments are so great, as long as you trust your integration process and test suites.

It works on my machine!

My general contribution to the conversation is GitHub should have a donation system. Once a week, some kind of donation raffle happens, and the winner gets GitHub taken down for "reasons" for 4 hours, then 5, 6, 8. Microsoft profits more, and it slowly becomes a technology-and-money-induced vacation day.
- Or and I know this sounds crazy, we (I actually mean you) collectively agree on laws that gives everyone a couple of paid vacation weeks a year.

Ironically, I find myself writing more code when CI is broken and I don't have to babysit it.