161–170 of 176 posts
Earlier quoted context omitted.
That is just called your browser history?
The browser history contains a lot of junk and I don't want that saved forever. Curated tab history is a bit different. It's stupid for sure, but also a bit comforting to keep the most important articles and such. For anything I really care about, there's always ArchiveBox.
Earlier quoted context omitted.
Azure's going to suffocate github. I'm curious to see what's next. Will self-hosting the code repository come back in vogue or will another social-coding platform take off?
We should worry less about what everyone else uses, and more about what we use. I'm self-hosting Gitea and thinking of upgrading to Forgejo. What are you using?
Works great for small-medium scale
Earlier quoted context omitted.
I wonder what is this database, and why it is hard to fall-over automatically.
RDBMS replication and failover is way more difficult and manual than anyone would like. You can't just set up two postgres, tell them they're clustered and have it basically work; at a minimum you have to design the client to somehow know which one is currently the master, or use some sort of proxy (which becomes its own SPOF). RDBMS integrity basically requires that one master server is responsible for the whole dat…
Scaling is a dream or theory we think we solved. Distance between ... to practice. So ... should be reconsidered again.
This level of scale is extreme but it can be handled with proper time investment and careful engineering. But that doesn't fit into the "spend gobs of money as fast as possible so you can be a hypothetical feudal lord in a sci-fi dystopia novel you read when you were twelve" line of thinking.
Earlier quoted context omitted.
PMs deciding software infrastructure over the dev teams that the dev teams use, is wild.
From my experiences devs in large corp usually don't have a say in what kind of software infrastructure they can use ...
In the example, in my 20 year career, I've seen bitbucket in use once. I'm the one who usually manages that stuff since I'm an infra eng.
Earlier quoted context omitted.
i'll echo this sentiment. historically there's been a lot more flexibility with GL CI yaml syntax, including real yaml anchors https://frenck.dev/github-actions-yaml-anchors-aliases-merge... sys-admin-ing gitlab can be a bit of a maze of web menus tho.
What do you need real anchors for? Sharing of pipelines? Maybe I’ve been burned too much by pipeline maintenance (because we didn’t have yaml anchors?) but I rather have builds defined in make /bazel/etc than in yaml. So the only thing the pipeline does is optionally restoring caches, kicking off the build system, uploading PR validation results, and saving cache. Pushing artifact etc is all done from inside the buil…
Earlier quoted context omitted.
> Is all content in HN supposed to be professional and serious No > are humorous comments in fact allowed Yes Neither is what's going on here. It's reckless to share stuff you haven't even looked at yourself, that's fairly basic thing to care about. Sharing "here's a bunch of random GitHub repositories" isn't humor (I think?) nor would it been different if the text was "more professional and serious", whatever that m…
I found it quite funny that people develop extensions that track the availability of one of the most important building blocks of the software industry, because their reliability is so poor. You could have posted a warning to not actually install random extensions. Instead you came across as questioning why anyone would post links to them at all. The poster was clear they didn't actually recommend the extensions. Sha…
Sharing stuff we know are good is fun. Sharing just random stuff? No, why would you do that? The whole point is why would you share those extensions if you don't actually recommend them? It's noise, the opposite of why we all come here in the first place.
Do you also just submit whatever to HN as link submissions, without even reading it or checking it yourself?
Earlier quoted context omitted.
RDBMS replication and failover is way more difficult and manual than anyone would like. You can't just set up two postgres, tell them they're clustered and have it basically work; at a minimum you have to design the client to somehow know which one is currently the master, or use some sort of proxy (which becomes its own SPOF). RDBMS integrity basically requires that one master server is responsible for the whole dat…
Mongo will auto failover if you have 3+ replicas. Primary knowledge is abstracted into the driver or query router level depending on setup.
This can be implemented in front of any RDBMS as a separate layer. Traditionally they weren't designed for quorum-sensing since it hadn't been invented yet. I'd be surprised if something like pgbouncer couldn't do it.
Earlier quoted context omitted.
A browser extension to indicate githubstatus being yellow/red: https://chromewebstore.google.com/detail/is-github-down/lcfo... A VSCode extension: https://marketplace.visualstudio.com/items?itemName=RuslanRy... Firefox: https://github.com/matagus/github-status-checker Caveat: https://news.ycombinator.com/item?id=49450924 (disclaimer: none of these are recommended by me to use - merely sharing to build on for this dis…
Another useful disclaimer: all of these lets the developers push updates to your computer as they wish by default in most setups, these days you might want to decrease that kind of attack surface and just check the status in the official website when "git push" suddenly stop working. Especially when extensions and stuff sometimes changes hand and it's kind of hard to keep track of it, except for when something bad ha…
Overall, I disagree and think it's valid and responsible to share links to apps if I disclaimed that I don't recommend installing their linked applications in an environment that has access to private data.
One valid reason, to share links, is to illustrate that there are more than zero efforts to address this issue - the parent comment issue - through and even more convenient practice than firing up a web browser, following link, waiting for it to load, reviewing the material, to see if GitHub status is red or green today. So this reason attempts to build up the importance of the parent comment's idea, and suggests that legitimate verifiable work is advisable, to continue down that path of making it more convenient for developers have simpler, more human indicators about the reliability of their digital tools.
Pretty simple reason but that's my reason.
Earlier quoted context omitted.
> "Why would you recommend extensions to do this?" This is not my complaint though, my complain is: Why would you recommend extensions you haven't tried nor even read about yourself? The goal isn't to pick apart the message to piss someone off, the goal is prevent someone else than the author from getting hacked because they install some random extension, not understanding what kind of access you're giving others whe…
They didn't recommend the extensions. They linked them because they were "merely sharing to build on for this discussion". Is all content in HN supposed to be professional and serious, or are humorous comments in fact allowed when discussing a market leading company who has had regular outages for a year and a half? (Yes, I know the actual reasons why GitHub are struggling.)
I didn't say, and I probably should have said, "Use the fact that there are a number of these developer focused IDE/ browser extension tools as motivating information, about the emerging need to support human developers in there daily triage burdens, as is it's arguably a need .. a trend that is worsening."