Meta Pauses Employee-Tracking Program Following Internal Data Leak

You don’t work at Anduril to make bread, at least not as a software engineer. It’s a long hours startup with worse pay than FAANG in high CoL areas. The people that work there fundamentally believe in “improving the defense of the west”.

It is the private sector equivalent of joining the military. If you want to bag on people in the military, go ahead. But they are not in the same category as people just doing things for convenient good money.

I've quit jobs over ethical boundaries. It's not an easy decision, and "integrity" doesn't quite pay rent, but helped me to sleep better at night and let me live with myself.

In any case, it's quite simple. If you work at Meta, you certainly have other options. Similar-tier companies pay just as well, and lower-tier companies will interview you readily.

We're not talking about someone scraping by here - working at Meta is a choice, and takes hard work to get into. That does not absolve you from the damage the company has done to the world. If you work there, you contribute to it (no matter how small the capacity) and you benefit from it literally through wages and share ownership. Your vested interest is in the company growing. Historically, that has meant via very dark patterns.

There is no “make things harder for the dictator” at Meta/Fb and never has been.

And the native Windows app was a post-Facebook introduction, but it was also Facebook that canned it in favour of the current web wrapper turd.

Well, yes, but... its popularity is not completely accidental. It's good - even by today's standards, but certainly by the standards of the time.

Arguably React does have a 'disadvantage' in the sense that it doesn't do two-way data binding, and chooses to update as little of the DOM as necessary to render a change (which it's good at, and gets right), but that's sometimes more than just changing a text node or a value. I suspect that if React hadn't come along there'd be lots of homegrown frameworks doing something similar in a worse way. React is well thought-out and well designed.

Also, every reactive framework can have the same problem. It's not a React thing; it's a library-that-tracks-changes-and-updates-the-DOM thing. Used poorly you'll end up in a re-render loop.

We could just have static HTML pages and that would eliminate the whole problem, but then we'd be complaining about the electricity used on network roundtrips and people using badly coded desktop apps instead. Ultimately, libraries can be as bulletproof and fool-proof as you like, and developers will find new and novel ways to use them to build crap software. The responsibility (mostly) lies with the developers much more than the library.

Rich Harris makes the point that React isn't actually reactive: "React doesn’t have any understanding of the values running through your app. It is not Reactive."

Rich Harris - Rethinking reactivity:

https://www.youtube.com/watch?v=AdNJ3fydeao

>Modern JavaScript frameworks are all about reactivity. Change your application's state, and the view updates automatically. But there's a catch — tracking state changes at runtime adds overhead that eats into your bundle size and performance budgets. In this talk, we'll discover an alternative approach: moving reactivity into the language itself. Your apps have never been smaller or faster than they're about to become.

He starts with spreadsheets as the archetypal reactive system.

Defines reactivity as values automatically updating according to dependency relationships.

Contrasts that with React's model of rerunning component functions and diffing virtual DOM trees.

Argues that React "doesn't understand the values flowing through your application" and therefore isn't reactive in the traditional sense.

Virtual DOM is pure overhead:

https://svelte.dev/blog/virtual-dom-is-pure-overhead

>But it turns out that we can achieve a similar programming model without using virtual DOM — and that's where Svelte comes in.

React tracks component renders; reactive systems track data dependencies. React doesn't react, it repeats.

I think React should have been called "Repeat", "Re-Run", "Regurgitate", or "Retch".

It is in fact better to be employed arms manufacturer then be member of SS - regardless of which position they put you in. You knew this is fascist organization as you was entering it and that everything you will do is to advance those goals.

SF and Meta make sense if you are going to try to be the cutting edge of conversations and tech.

If you just want to live your life?

As of Germany, I don’t follow currenct politics over there (not a German here, Finnish), but you guys have time and time again show that you can produce pretty much anything for the global markets as well or better than anyone else. Your problems are political, and you are your own worst enemy. Germany has enormous possibilities as a society, if you just get your shit together.

Not for any length of time there aren't

Compared to say seattleLA/Newyork, the number obviously homeless is vanishingly small. Yes, tubes will have a beggar, but there won't be more than one of them. They also are rarely aggressive.

Even in Soho, where one of the main london hostels are for homeless people its not that bad.

There are a small number of FAANG-ish companies who pay very high salaries in Berlin, London, Dublin, etc etc.

(And of course Zurich, but Zurich is Zurich.)

> Paying >100k is already super good, so they do probably around that.

I assure you that they pay more than that for halfway senior roles. Note that a lot of it would be in equity; the base salary would likely be in the 100-150k range, but one might get that again in equity.

if you are moving countries you keep your RSU allocation, but your wage is adjusted down/up based on local levels. (ie for london its .85 or something)