I've been running GitLab internally on k8s for 6 years, it handles code, CI, security scans, build artifacts, helm charts, etc. It runs a nightly backup to a GCS bucket.
Monthly upgrades are painless. Once a year the major versions (18 to 19, for example) bump external dependencies and we need about an hour on it.
I've been using GitHub for other projects and for the life of me I can't see a single area where its better. Actions is worse without versioned and self documenting components, there's no concept of a project hierarchy or inherited permissions, even simple things like setting up deploy keys are more annoying than they need to be.
I can't speak for GitLab.com - I've never used it.
Gitlab.com used to be slightly less available than GitHub but recently I think the tables have turned and Gitlab saas is relatively stable.
I also enjoy Gitlab as a platform. It's got everything, good board, good repo, good issues, good CI, extremely good registries. It's got the equivalent of gists and pages... It a better product all things considered.
GitHub just wins because of popularity. It's WordPress all over again, the thing people use because it's a thing people use.
> I've been using GitHub for other projects and for the life of me I can't see a single area where its better.
Triggering github actions manually is way, way cleaner. Also the pipeline configuration feels cleaner to me bit that might be personal preference more than anything else.. Otherwise I agree. =)
We switched to Valkey two years ago. I haven't really looked back. I think both projects have done a lot of nice stuff since the split but it's not really impacting anything I use. The feature set was fine five years ago and I don't think we're using anything in Valkey that wouldn't work in Redis. There are probably a lot of projects that never switched over because they had no real need.
But most of the cloud providers now offer Valkey because of the license changes. Of course, cloud providers not offering Redis was the intention of the license change from the Redis point of view. So mission accomplished for Redis.
But the flip side of course is that if you want to deploy on standard infrastructure rather than self hosting Redis, Valkey is now the easy, low risk path that probably should be the default for most companies that target AWS, Azure, GCP, etc. Same with Elasticsearch vs. Opensearch and a few other products where the community forked because of license changes.
Mentioning Elasticsearch because I know people in both communities and I'm deeply familiar with the stack. A few years on, Opensearch has taken a lot of the momentum from Elasticsearch.
Valkey, because our cloud provider is hosting it and that's obviously what they prefer.
I feel like we're using about 1% of its features at this point - really just as a fast K/V store - so it would be easy to switch if needed, but I can't see a case where we would.
We use almost exclusively Valkey now, mostly because we host on AWS and Render, which both use Valkey. It's faster, cheaper and compatible. I'd consider Garnet too but I believe it doesn't support LUA(or didn't at the time we needed it).
We switched to Valkey after the Redis license kerfuffle happened, discovered we were saving money on our AWS bill, and have no motivation to go back to Redis.
Valkey continues to be the real redis, released under a permissive open source license like redis originally was. The fork of redis known as redis because those that decided to fork it had the trademark at first wasn't under an OSI-certified open source license and now is under a non-permissive OSI-certified open source license.
We got my daughter a Yoto and it's a great device. She sticks a card in and it plays music or an audiobook. There's a "screen" but it's a low resolution pixel grid that shows pixel art of the current track.
We use luuni which is similar (except that it also enable choose your own story with audiobooks). Even then, we limit it because otherwise he would want to listen to it every time before sleeping (and it prevents him from sleeping)
Thanks for the correction, but I'm going to leave my original post alone even if I could still edit it.
I've no more use for Ronny Chieng's ideas as to what I should do with my life than I would Conan O'Brien's or Eric Schmidt's. Let them live their own lives according to their own ideas.
But right now we have games that you have purchased for a one-time price, the developer revokes your ability to play it years later, and you have no recourse.
Why would you be entitled to infinite support? For a game with an online component? Why does the game's purchase price extend to infinity instead of "for as long as the developer supports the game"?
You aren't entitled to infinite support. You are entitled to keep using the thing you paid money for. If the publisher can't support the online service, they're obliged to make the game still playable by either releasing server code or offline modes.
If you sell a product for money, you don't then get to later take the product away and keep the money.
You still can sell X months access, if that's what you plainly state is being bought.
I don't think you could sell "for as long as the developer supports the game" specifically, since that'd be an illusory promise (no actual obligation if the product can be revoked immediately), making the contract unenforceable and the customer entitled to restitution (a refund).
"infinite support" is pretty much just "leave the customer with the product they bought working". There doesn't need to be any ongoing costs.
It's not endless support but more "Don't stop me from playing the game". For example, win xp is no longer supported. You can still use it.
For a lot of games the current situation is essentially the same as "The OS is no longer profitable enough, so the developer prevents you from using it"
It doesn’t have to be completely unsupervised for the driver to realize huge improvements in quality of life. I don’t even notice when people drive slow or cut me off. I’m just relaxing, fiddling with the music or talking to my family. And managing two toddlers is a lot easier when my brain doesn’t have to run a constant background job.
I do hope that unsupervised comes soon though. The tech is there, or at least far enough that I consider it better than my own driving. The hurdle is regulatory now.
If you're distracted and not actively monitoring an SAE Level 2 autonomous system then you're a hazard to yourself and others. Don't do that. You need to be ready to actively intervene with zero advance notice.
You're technically correct of course, but the fact of the matter is every driver gets distracted/tired and having the FSD safety net only makes things safer, assuming you don't go out of your way to get distracted. I've lost count of the times I looked over at a "dumb" car being driven by someone on their phone. Would you rather that person be in a Tesla using FSD or in their Subaru Crosstrek?
Unfortunately, even if we'd prefer to not accept it, we live in a world where those people exist. So I hope that they are being driven by their self-driving car when they inevitably drink and drive or fall asleep at the wheel. And to mitigate the impact of the ones driving a non-self-driving car, I'm going to use my self-driving certified-safest car to drive my family around.
So far I've been impressed enough with the HW4 Teslas that I haven't had them do anything that I had to intervene to correct or prevent. It's pretty amazing at how well it handles all kinds of things - construction, weird merges, road debris. This morning, there was a tire in the middle of the road, which caused traffic ahead of me to slam to a halt. Mine had to brake hard enough that ABS engaged, and then navigated around the tire. I was impressed.
Monthly upgrades are painless. Once a year the major versions (18 to 19, for example) bump external dependencies and we need about an hour on it.
I've been using GitHub for other projects and for the life of me I can't see a single area where its better. Actions is worse without versioned and self documenting components, there's no concept of a project hierarchy or inherited permissions, even simple things like setting up deploy keys are more annoying than they need to be.
I can't speak for GitLab.com - I've never used it.
reply