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

621–630 of 671 posts

Re: Hello, GitHub

#621

Post by krylon »

Wurdan wrote: post #573
snowwolf wrote: post #21

Earlier quoted context omitted.

I’ve seen many acquisitions commit to 2) only to slowly walk back from that “in the interests of operational efficiencies”. And next thing you know you have to change over to using a Microsoft account to log in...

Having seen a big Microsoft acquisition from the inside, I can also tell you that this dynamic occurs: Microsoft is a gigantic organisation with very good working conditions. This leads to people with very long tenures working in highly defined and specialised roles within the company. Career development does happen, and is actively encouraged by Microsoft, but you're usually moving into a role which is just as niche…

> organisational osmotic pressure

OT, but I love that term!

Re: Hello, GitHub

#622

Post by glenneroo »

snowwolf wrote: post #21
ericabiz wrote: post #7

I’m going to be a bit contrarian to “the sky is falling” posts on HN and say: I think Microsoft is handling this really well. 1) They’ve acknowledged the skepticism around the acquisition. 2) They’ve expressed their commitment to keep GitHub an independent platform (like they did with LinkedIn.) 3) Nat Friedman, although I was not familiar with him prior to this, seems like an ideal candidate to run GitHub. This, ove…

I’ve seen many acquisitions commit to 2) only to slowly walk back from that “in the interests of operational efficiencies”. And next thing you know you have to change over to using a Microsoft account to log in...

...which one year is a Microsoft account, the next it's live.com, then msn.com, then passport.com, then outlook.com. And what about that 20-year old MSDN account, which was always associated with Hotmail? You can login but it hangs on some obscure error message. Googling suggest to associate with a non-Hotmail address, but that one doesn't let me access MSDN subscriptions. Next forum suggestion: create a VisualStudio.com login and link with Live.com... but it still doesn't work. Several support emails later, I just need to delete all existing associated MSDN email accounts and start over with my work email address. I just wonder how long until I need to migrate again to the next email/login-flavor-of-the-year. Maybe I'm just an edge case?

Re: Hello, GitHub

#623

Post by glenneroo »

baldfat wrote: post #609
executesorder66 wrote: post #595

Earlier quoted context omitted.

> their present has been so good - Putting adverts directly into their OS (which people pay for by the way) - Forcing their shitty updates, (and restarts) at the most inconvenient times - making it impossible to permanently and easily turn off telemetry Wow, you have low standards. I bet if you ate dog shit, you'd say it's not so bad.

So Windows 10 isn't leaps and bounds better than Windows 7 or Windows 98???? Seriously Windows 10 is the first Windows I have ever actually liked. I got my OpenSUSE terminal open and using ranger and my other terminal programs working in Windows (At work I have to have Windows due to many issues on one computer) > Forcing their shitty updates, (and restarts) at the most inconvenient times Weird I have a pop up that s…

So you haven't been getting the Candy Crush Saga, One Office trial, et al. games/software installed to the top of your "Start Menu" after every major OS update? It's only 2 clicks per app. And I'm sure it's part of why the last big update took 2 hours to finish (with only a warning, this may take a while... good thing my deadline was the next day and not in 2 hours... still ended up being a very long night, since the update broke other things). Also this last major update (Content Creator?) bricked a bunch of PCs... I had to do a "system reset" with USB stick to get things moving again.. but I'm still getting BSOD about once a week since then.

What about them mucking up the Spectre/Meltdown patches which bricked a bunch of PCs? In my case I wasn't bricked but I had to rollback a patch.

What about re-enabling of disabled services (e.g. Firewall, Defender) after some updates?

Going back a couple years ago, what about downloading/pre-loading Windows 10 on Windows 7/8 computers, without the user asking first? Can we forgive them for that? It used up several GB of space and burned sometimes expensive bandwidth? Happened to my laptop while I was traveling, I only noticed after I started getting low disk space warnings.

If I had a real list of the all the actual problems I've ever encountered with Windows, Windows 10 is definitely approaching Windows ME levels of incompetence.

Maybe some of us are just having more issues because we have unique hardware configurations which don't play well with Microsoft's newest foray into OS experimentation. Or perhaps our expectations are too high?

Re: Hello, GitHub

#624

Post by zao »

rmason wrote: post #308
politician wrote: post #233

Earlier quoted context omitted.

Ah yes, Apache Foundation, the place where ambitious but under-resourced projects go to die. /s

I've got a few friends that are still very involved in the Flex community which is now at the Apache foundation. Adobe if I remember correctly is still funding staffers to work on Flex many years later. I believe Flex is either the second or third most successful project at Apache in terms of downloads.

Thought you were talking about the good old lexical analyzer "flex" there at first.

How silly of Adobe to name it like that. :D

Re: Hello, GitHub

#625

Post by grumdan »

k__ wrote: post #582
grumdan wrote: post #580

Earlier quoted context omitted.

> I had the impression VSCode had the technical superior plugin system From my very limited exposure to VSCode's plugins, it seems they are a lot more limited in how they can change the editor's behavior compared to elisp code in Emacs[1]; if Atom plugins are similarly flexible, then I'm not sure you can say it's (strictly) technically superior if you can only implement a small subset of what you can do in competitor…

I meant superior to Atom and not to Emacs. As far as I know, the VSCode plugins run in their own process, which makes the editor much more responsive when it loaded many plugins.

I was assuming that Atom extensions were similarly powerful as in Emacs, if that's not the case, then my point is moot.

I agree that restricting what plugins can do can lead to better stability and speed at the expense of extensibility.

Re: Hello, GitHub

#626

Post by luckydata »

jacquesm wrote: post #615
luckydata wrote: post #322

Earlier quoted context omitted.

That's, like, your opinion man. Most of my jobs and most of my friends jobs have come through (or discovered thanks to) Linkedin. Before becoming an employee I used the site to find cofounders, people to interview for product feedback, check the background of possible hires... You don't use it or like it, fine. Linkedin has created economic opportunity for so many, it's kinda ridiculous to dismiss it out of hand.

Says the guy working for Linkedin. https://news.ycombinator.com/item?id=17232483

LOL, you caught me, so cunning. Almost like I didn't say "before becoming an employee" right in my comment.

Re: Hello, GitHub

#627

Post by luckydata »

swayvil wrote: post #326
luckydata wrote: post #313

Earlier quoted context omitted.

Other than being the biggest developer-focused company in the world? Having an extremely complete set of developer tools that can integrate with github? A cloud computing service to deploy apps? I guess nothing, it brings nothing to the table.

I think that Microsoft is money-focused, not developer-focused. Correct me if I'm wrong, but the mass of open-source developers vastly outweighs Microsoft. These "developer tools" are the property of Microsoft. Which suggests an obvious and worrying path in Github's future. Tell me that I'm wrong. Everybody and his dog has a cloud computing service these days.

Do you think Github wasn't "money focused"? I'm sure you felt mighty smart making that comment, but businesses are by default focused on making money. HOW you make the money varies, but the final goal doesn't.

Re: Hello, GitHub

#628

Post by ethbro »

Piskvorrr wrote: post #616
kthejoker2 wrote: post #598

Earlier quoted context omitted.

Serious question: do you think your company has better security than the Azure cloud? Or is it a trust issue with the cloud vendors themselves?

Better is relative - especially in one metric: many eggs in one basket make that basket exponentially more attractive to evil actors. Bigger attack surface and whatnot...

Flipside (pro-cloud pov): if the work to protect one egg applies to all eggs, then cloud providers will always hypothetically be able to spend more on security due to economies of scale

Essentially, choose your vulnerability: cloud provider single point of failure or in-house lack of resources

Re: Hello, GitHub

#629

Post by jonny_eh »

rad_gruchalski wrote: post #441
jonny_eh wrote: post #356

Earlier quoted context omitted.

Especially those that compete with MS or their subsidiaries. But then again, Netflix uses AWS, so who knows?

I don’t understand your comment about Netflix using AWS. AFAIR, Netflix is a reference customer for AWS. Every re:invent is full of Netflix people. Care to elaborate?

Amazon is Netflix's largest competitor.

Re: Hello, GitHub

#630

Post by phillipcarter »

praneshp wrote: post #553
phillipcarter wrote: post #284

Earlier quoted context omitted.

MS employee here: Long before the acquisition, we've been hosting important stuff in private GitHub repositories. Including having strategic discussions in those private repositories. We've also done a lot of that stuff in public too. Some might say a bit too much, given that we've had things leaked and/or misinterpreted w.r.t product direction in the past. I still agree with your point, but I believe more of this so…

I'm almost sure you mean private repos on github.com, but just wanted to confirm it. You don't mean corp github right?

Yep.
Post reply on HN