Oddskar

It doesn’t matter if the interviewers are sensible.

We don’t use Angular but we interview Ng devs anyway. If you’re smart enough to write maintainable apps in it you can learn e.g React or Vue quite quickly.

I’ll bite. Say you have a singleton service class that needs to be accessed throughout your SPA; where would you instantiate and keep this?

I have had that conversation multiple times in multiple teams. We adjust things when they don't work; e.g. if someone is obviously not making it to a meeting in the morning.

I don't see why you couldn't make that ask.

As opposed to the traditional networks the time you have to build that "large" audience is insanely higher. Who knows how long streaming services will be around for.

People are still watching Friends for instance.

I’ve watched five episodes. It didn’t get better.

I think this is a very outdated view of the way series and streaming platform have evolved. There’s no “slot” to fill. There’s no need for universal appeal.

“The Crown” is a good example. This would never have been made into a show before streaming.

The Foundation could have been a intellectually stimulating sci-fi show that appealed a lot to a smaller audience and it still would have been successful.

Both population control and a sustainable lifestyle.

Why can't it be both?

I've already substantially changed my lifestyle to be more sustainable.

I don't own a car, I don't eat meat, I consume very little and try to buy used things instead, I repair all my things as much as possible, I try to steer my investments away from anything close to fossil fuels.

Now you.

I think you've somehow missed the vital part: our lifestyle is not sustainable. We shouldn't aim to sustain something that simply cannot continue.

Will you recognize that it doesn't actually have to be a point to it, though? As long as you can spellbind investors there doesn't actually need to be something useful that's build at the end of the day. "Crypto" is a good example of this. A lot of the products and services that were build using Blockchain could just have used a normal RDBMS.

I think there's an obvious answer to that question: don't focus so much on profit and ensure that the net benefit of your product for humanity is greater than it currently is.

Such hogwash. Because people dismiss the latest lofty vision of a tech behemoth (that has a long graveyard of unsuccessful services behind them) we're now "legacy" and "old people yelling at clouds"?

Disregarding Meta entirely, I would say it's completely normal for people on HN to be sceptical of new things. Most new things don't work out. Most new things are either vaporware or snake oil. It's hard to tell the good from the bad sometimes.

> Another surprising finding is that there appears to be a certain cutoff for bedtimes, such that going to bed later results in poorer performance, even if the total amount of sleep is the same.

I would perhaps rephrase this as "people who stimulate themselves enough that they stay up late have poor quality sleep".

I for sure experience this myself when I don't properly wind down my mind several hours before going to sleep.

> And, it makes sense the VR/AR will be the medium to contain all other mediums.

In the same way that e-books will make normal books completely obsolete? I doubt it.

I read this three times and I'm still not sure what your point is.

I fail to see the appeal. Much like most modern architecture this style will be applauded by architects, meanwhile they all choose to live in much older style architecture because it's more homely and non-oppressive.

I guess architects are a bit like hedge-fund managers in that regard; they all keep their investments in index funds and not hedge funds.

Complete hypocrisy imho.

Maybe you missed the part where FB undermined the US election?

There can be no going backwards. Only forward!

Some potential answers:

* Original programmer has since moved on, and as per industry standard there was no hand-off and code is poorly documented

* The team in charge of this is busy delivering features/fixing bugs for whale clients

* The product organisation down prioritizes it because the PM wants to build a shiny thing that gets them promoted

Wow. Comparing with this addon and without is pretty jarring. I might actually start using the newsfeed again with this addon.

Holy cow do FB just shove a bunch of shit into the feed.

Oops. Should have been "trackpoint" and not trackball. It's a pimoroni trackpoint breakout board.

Niche software support? My keyboard and the analog addons works on Mac, Windows and Linux with excellent support since it runs QMK firmware.

The touch bar was fingers on glass. It's not appropriate for a professional device since it requires you to look down and doesn't lend itself to the "mechanical" use of devices that high-paced work requires.

Also, you can actually add the analog inputs yourself. The DIY keyboard community -- which is flourishing with options and new vendors -- has lots of options available. I myself have two analog knobs and one trackpoint on my keyboard. It's absolutely amazing.

> For example, I have implemented layers where GraphQL queries feed into mobx to manage some additional application state that never persists.

Not sure what you want to say with this because it sounds like you used Mobx for state management in that case. Or do I misunderstand you?

> I additionally think that it's a very light layer in terms of managing state

According to bundlephobia:

React + DOM = ~42KB Gzipped

@apollo/client = 39KB Gzipped

For reference redux + redux thunk is like 2KB

Xstate is less than 20KB

> what I really mean is knowing when the client-side cache needs to update

Aha, and that sounds sensible. I agree. There are lots of other things in Apollo though that you apparently aren't using.

I actually read this as sarcasm and then I depressingly remembered this was actually the case. What on earth happened to computers.

That's fair. Edited my post.

I'm not praising REST at all. REST as it was de-facto used was in my opinion a hot mess that was poorly understood and had developers focus on the wrong things (e.g. pretty urls).

I still don't think GraphQL as state management is a good idea for anything surpassing moderate complexity. And yes I've worked with both GraphQL and Apollo. I can see the merits for sure; for instance discoverability and being able to generate types from the API are great. I don't like overcommitting to Apollo though and using the overly sized client. Something is wrong when your state management is bigger in filesize than the SPA framework you're using.

REST? Didn't you get the memo? We've all moved on to GraphQL because Facebook use it and that means we all should use it.

It also enables our UI components to easily fetch data themselves. Because that's a great architectural pattern that we've discovered.

We didn't have APIs 10 years ago?

I agree with the article. As we build more complex products we need to be more specialized and work together.

Maybe not the case if one is working at a startup trying to cobble something together that looks like a working product by customers and investors.