Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hello, GitHub

natfriedman.github.io

Post reply on HN
Print view View original

491–500 of 671 posts

Re: Hello, GitHub

#491

Post by chrisweekly »

Klathmon wrote: post #129
justadudeama wrote: post #101

Earlier quoted context omitted.

This is my thinking as well. Do I bail ship to gitlab and support more open software, or do I try to stay centralized?

Personally, I'm not "bailing" from anywhere. I am however using this as an opportunity to rely on any one single place less . I'm in the process of mirroring my git repos on GitLab, and trying to think of a way to signify that both the GitHub and GitLab repos are "canonical", and that issues/PRs/contributions can happen at both.

I do not think the word "canonical" means what you think it means.

Re: Hello, GitHub

#492

Post by Klathmon »

chrisweekly wrote: post #491
Klathmon wrote: post #129

Earlier quoted context omitted.

Personally, I'm not "bailing" from anywhere. I am however using this as an opportunity to rely on any one single place less . I'm in the process of mirroring my git repos on GitLab, and trying to think of a way to signify that both the GitHub and GitLab repos are "canonical", and that issues/PRs/contributions can happen at both.

I do not think the word "canonical" means what you think it means.

> accepted as being accurate and authoritative.

> synonyms: recognized, authoritative, authorized, accepted, sanctioned

That's what I meant for it to mean anyway...

Re: Hello, GitHub

#494

Post by pheon »

Am seriously pissed at this. MS has been slowly acquiring all the tools used for my business, its like surround and siege warfare. Skype, Linkedin, now GitHub..

The time horizons on these kinds of acquisitions are 5 years out. In that time you`ll log into Windows 20, single sign in to Skype, Linkedin, Github all re-branded, all re-written code, with messed up ELUA and a shitty product.

Dont believe todays fluff and BS, the end game is many years out.

Re: Hello, GitHub

#495

Post by rapind »

sequoia wrote: post #259
Klathmon wrote: post #64

Earlier quoted context omitted.

I agree, my biggest concerns are: 1. What is happening to Atom? I have tried VS code and don't really like it due to the difference in how the 2 systems are designed to work (Atom being more "plugins are king", VSCode being more "kitchen sink included by first-party"). I'd hate to see my favorite editor lose it's major backing. If MS makes a commitment to continue to develop Atom, or they work with someone else to "t…

> Atom I could be wrong but my perception is that Atom is losing market share to VSCode all on its own– new devs are much more likely to adopt vscode & no growth ~= decline for an editor. Couple that with the fact that no one pays for Atom... IMO They don't need to "kill" atom, they just need to wait a couple years, at which point it will just Yet Another Editor down the list with TextWrangler et al., if the next Ato…

Anything that came out after vi is just another editor.

Re: Hello, GitHub

#496

Post by CydeWeys »

timv wrote: post #469
CydeWeys wrote: post #443

Earlier quoted context omitted.

I don't understand by what metric Netflix is included but Microsoft is excluded. It should really be FAAMG, or maybe FAMANG.

Well in this very specific context, it's hard to imagine that Microsoft will be avoiding using GitHub just because it's owned by Microsoft.

FAANG is used very generally to refer to these five companies. It's not just in this specific context. I'm wondering why Microsoft is excluded.

Re: Hello, GitHub

#497

Post by hinkley »

adrianmalacoda wrote: post #255
Klathmon wrote: post #64

Earlier quoted context omitted.

I agree, my biggest concerns are: 1. What is happening to Atom? I have tried VS code and don't really like it due to the difference in how the 2 systems are designed to work (Atom being more "plugins are king", VSCode being more "kitchen sink included by first-party"). I'd hate to see my favorite editor lose it's major backing. If MS makes a commitment to continue to develop Atom, or they work with someone else to "t…

Fellow Atom user here. According to Lee Dohm, Open Source Community Manager at GitHub, "Atom remains key to GitHub. Our product roadmap is set, and the team will continue all of their work." [0] [0] https://github.com/atom/atom/issues/17454#issuecomment-39442...

In a buyout, always be sensitive to situations where promises of status quo come from someone who is not in control of the situation.

Quite common for new owners to let old employees make promises they can’t keep and then make them disappear and change plans.

Re: Hello, GitHub

#498

Post by zeth___ »

baldfat wrote: post #227
snowwolf wrote: post #59

Earlier quoted context omitted.

Because it’s an indicator of a loss of independence. And if you went through the Skype changeover you’ll know exactly what a fiasco that change to a Microsoft account was.

You mean from 2011 when Microsoft had totally different management and business model? I don't see the Steve Ballmer Microsoft has much bearing on today's Microsoft. Also it wasn't the Microsoft Account change as much as the they had the weird MS Store or Local account sign in options. I removed the Store sign in and only used local and had no issues. Am I missing something?

Jesus Christ. Is everyone here a teenager? Microsoft in the 80s might bot be a valid comparison today, but something that happened 6 years ago is barely yesterday. Institutions do not change that much that quickly.

Microsoft 15 minutes ago isn't the Microsoft of today is just as true a statement and one just as vacuous.

Re: Hello, GitHub

#499

Post by hinkley »

pbarnes_1 wrote: post #394
adrianmalacoda wrote: post #255

Earlier quoted context omitted.

Fellow Atom user here. According to Lee Dohm, Open Source Community Manager at GitHub, "Atom remains key to GitHub. Our product roadmap is set, and the team will continue all of their work." [0] [0] https://github.com/atom/atom/issues/17454#issuecomment-39442...

Until the deal closes. Then... who knows.

The really nasty changes always seem to come at the beginning of the second fiscal year after acquisition. So meet me back here in 18 months and we’ll talk.

Re: Hello, GitHub

#500

Post by Shank »

pknopf wrote: post #53
pkfrank wrote: post #6

While the submitted link resolves: https://natfriedman.github.io/hello/ This doesn't: https://natfriedman.github.io/ Might be worth redirecting...

> https://natfriedman.github.io/hello/ Wait, is that a one-off custom landing page? Something that normal users can't do? I don't see a "hello" repo in his list of repositories: https://natfriedman.github.io/hello/ Can private repos have publicly accessible pages?

I think it’s the gh-pages branch on a private repository.

If you look at Nat’s account right now [0], he doesn’t even have the telltale “GitHub Staff” badge, probably because his hiring is contingent upon the deal closing.

So he’s definitely not an admin at the system level, which just makes him a normal account.

https://github.com/natfriedman

Edit: I’m on a roll today. No, I’m mistaken — it’s not gh-pages. This is the repo: https://github.com/natfriedman/hello

By all measures I don’t see how this is a pages repo at all.

Post reply on HN