Live data from Hacker News

GitHub to lay off 10% and close all offices

twitter.com

241–250 of 907 posts

Re: GitHub to lay off 10% and close all offices

#241

Earlier quoted context omitted.

They even had a full-scale replica of the Oval Office there https://twitter.com/harrymccracken/status/710956599477534720...

Uh wtf I want to have something more useful to say to contribute meaningfully here. But my brain segfaulted.

They got angry when Trump was elected so they forked the Oval Office.

Re: GitHub to lay off 10% and close all offices

#242
post #183

Earlier quoted context omitted.

I'm quite confused because almost all conversation in my company's slack happens in threads. Maybe your impression of Slack was formed in a time when they didn't have threads?

I think they’re just saying that teams forces you into using a thread, and make a choice to create a new one if that’s what you want. In slack by default you’re writing a top level message (ie creating a new thread)

Indeed, never underestimate the power of defaults. There’s a tendency on HN to say “well, everyone should just use threads on Slack then.” There is, of course, a way Slack could make that happen: make it the default.

(For what it’s worth, I much prefer Slack for communicating, but when I have to find something, I wish I were looking for it in Teams.)

Re: GitHub to lay off 10% and close all offices

#243
post #187

Earlier quoted context omitted.

vscode would be dropped like a stone

It's nowhere near good enough that people will pay for it. IntelliJ it is not.

No kidding if I have to pay for it I am going to pay for something that is way better. I use it because it is free (me being a cheap fool) and better than eclipse.

Re: GitHub to lay off 10% and close all offices

#244
post #100

Earlier quoted context omitted.

Teams is the result of Microsoft taking a look at Slack and saying, how can we make this feel more like Excel?

I don't see where is that a problem? People who will be using Teams are people using Office 365 daily. Having a cohesive ecosystem makes complete sense. From a UX too.

The problem is that its very top heavy and is not well done, has lots of UI bugs and really is a pain to work with

Re: GitHub to lay off 10% and close all offices

#245

Earlier quoted context omitted.

>i) Effective immediately, we will be moving laptop refreshes from three years to four years. ii) We will be moving to Microsoft Teams for the sole purpose of video conferencing, saving significant cost and simplifying cross-company and customer conversations Layoffs and having to use teams? Talk about a morale hit

But what's wrong with Teams? It works well enough for me in Firefox on Linux. But OK, I only joined customer-initiated meetings, and was never presenting, only watching and talking, so maybe never used some important but non-working feature.

The code display is utter shit, no proper markdown support and teams (what other chats call "channels" forcing threading for one.

Writing bots for it is also painful.

Re: GitHub to lay off 10% and close all offices

#246

Just wait till Microsoft starts charging a license for vs code and developers heads implode.

i'll just go back to notepad++. although i must say it's been in decline for the past year or so. they removed a theme i liked to use and i don't care for the UI changes at all. But it is still functional, at least until the next downgrade from the developer. Eclipse is also still a great IDE with tons of plugins.

The LSP stuff has actually unlocked a lot of fringe editor choices. Even new editors with tiny communities can provide a lot of IDE like features by just implementing the client side of the API.

Re: GitHub to lay off 10% and close all offices

#247

Earlier quoted context omitted.

They even had a full-scale replica of the Oval Office there https://twitter.com/harrymccracken/status/710956599477534720...

The dojo was cool, and the roof garden, plus the Western themed poker room and the Victorian drawing room with secret book cases that led to other rooms. It was the most extravegant place I ever visited, and as stated, it was almost empty. Still I got to have a couple of free beers and walk off with branded t-shirts, hoodies and even a baby-grow.

There is no reason to have this. Imagine how many lives they could've improved if they just donated a chunk of the money that allowed them to have offices like this to charity

Re: GitHub to lay off 10% and close all offices

#248

wild how so many companies are laying off 7-15% of their workforce in such quick succession

I assumed that once a critical mass of other companies in this industry make these moves, investors expect this kind of cut from all of them. They'll presumably invest elsewhere if your company doesn't make this cut.

But what’s odd is Microsoft owns GitHub and already did a massive(ish) layoff. Why the separate ones?

Re: GitHub to lay off 10% and close all offices

#249
post #227

Earlier quoted context omitted.

We have done the same at Zendesk. We've reduced our office footprint but have kept our hubs open with large enough offices open for the occasional large on-site and for easier team collaborations, as well as space for anyone that prefers to work in an office environment. I like the model, but I question long term economic viability of owning that much office space with mostly low utilization and only occasional spike…

Could rent it as co-working space on the rest of the days

> Could rent it as co-working space on the rest of the days

Or just downsize the office to the point where utilization is high and rent out co-working space themselves during the "spikes".

Re: GitHub to lay off 10% and close all offices

#250

Just wait till Microsoft starts charging a license for vs code and developers heads implode.

Hold on that could actually happen? It's not officially open source or anything?

I think it is, but there is also a fork call VSCodium without the telemetry, I guess people could just pivot to that?

https://github.com/VSCodium/vscodium

Post reply on HN