sciurus

Are you going to stop signing up new customers because you've scaled enough?

You act like this policy was intended as punishment instead of as risk mitigation.

Mandating full disk encryption is easy for IT to enforce. A policy of not putting sensitive information on laptops is valuable, but difficult to enforce. Encryption is a sound way to reduce the risk of harm when that policy is inevitably broken.

Full disk encryption also been the company-wide policy of everywhere I've worked in recent memory, fwiw.

For anyone who hasn't read the rider: https://github.com/ddol/rre-rms/blob/master/rider.txt

Right. 2019 should be out later this year.

https://blog.mozilla.org/blog/2019/11/21/state-of-mozilla-20...

I think about a year of lag is normal, e.g.

https://blog.mozilla.org/blog/2019/11/21/state-of-mozilla-20...

https://blog.mozilla.org/blog/2018/11/27/state-of-mozilla-20...

Newer submission with discussion: https://news.ycombinator.com/item?id=24166385

> Which is why Mozilla exec leadership is still in place after a decade of losing market share to Chrome and flailing about trying to find a business model that works.

In the 2+ years I've been at Mozilla, I think there's been almost complete turnover at the C-level.

For example, Chris Beard was CEO of Mozilla from 2014 through late 2019.

There's a frequent sentiment in these comment threads that Mozilla leadership is failing and facing no professional consequences, but I think that sentiment is misplaced.

Tangentially, there's a similar post from the devtools team at https://twitter.com/FirefoxDevTools/status/12936787391175761...

"Hi friends, Firefox Developer Tools will not be going away. We will be a smaller team and will share more details later when we have them."

I find the crowdsourced data at levels.fyi to be a good reality check on what dev compensation is like at large tech companies.

Let's take three others that make well-known desktop browsers: https://www.levels.fyi/?compare=Apple,Google,Microsoft&track...

According to that data, senior developers at Apple (ICT4), Google (L5) and Microsoft (64) make on average $320k, $352k, and $225k. Their fully-loaded costs (benefits, payroll taxes, office space, etc) to the company will of course be even higher.

These are examples of peer companies Mozilla is competing against for employees. As I explained at https://news.ycombinator.com/item?id=24138083 , Mozilla does not try to attract people solely via compensation. However, you can only offer so much less before you're no longer able to hire and retain the talent you need.

First of all, you probably will get less total comp at Mozilla than you could elsewhere. You'll still be paid well compared to many developers working outside SF/NYC/etc, though.

Second, instead of stock you'll get a higher potential bonus. The bonus percentage increases based on your level.

Third, benefits are generous. Being able to work remotely was a particularly unique and valuable one for a long time.

Fourth, the class and scale of the problems Mozilla is solving are interesting and challenging, which is a motivation for some employees.

Fifth, the mission and the commitment to open source are a motivation to many employees as well.

(These are just my personal observations as a current employee)

FYI the official talent directory is now online at https://talentdirectory.mozilla.org/ and I expect people will be adding themselves to it over the coming days.

I believe what you saw was a promotion of https://addons.mozilla.org/en-US/firefox/addon/facebook-cont...

That extension is described as:

"Prevent Facebook from tracking you around the web. The Facebook Container extension for Firefox helps you take control and isolate your web activity from Facebook."

You are, it's at https://blog.mozilla.org/wp-content/uploads/2020/08/Message-...

I'm sure there are lots of other engineering teams at Apple focused on security, build systems, developer tools, infrastructure, etc that the Safari/Webkit team relies on.

Then there are all the non-engineering functions like HR, marketing, etc.

Mozilla has to do all of that.

Something to consider here too is that Chris Beard was CEO of Mozilla for over 5 years ending late 2019. Mitchell Baker only took over within the last year.

https://blog.mozilla.org/blog/2019/08/29/thank-you-chris/

https://blog.mozilla.org/blog/2020/04/08/mitchell-baker-name...

> 250 FTE's is probably in the neighborhood of $25 million/yr

Mozilla is very engineering-heavy. While I don't know other people's salaries, I do know that the fully loaded cost of a developer almost anywhere is much higher than $100k/yr.

250 people, roughly 25% of the company, were laid off today.

This is on top of the 70 laid off in January (discussion of that at https://news.ycombinator.com/item?id=22057737)

> But a year and a bit later, the software is already starting to slow down even with a reset (switching to video from photo incurs a good 5-10 second delay, opening the camera itself takes a few seconds)

FWIW that's really not normal. Sounds like I got my pixel 3a around the same time as you, and I haven't had any problems like that. I wonder if you have a hardware defect of some sort.

> Coupled with Google's terrible implementation of work accounts

What's special about work accounts? I added both my personal and work Google accounts without any issues and can see events from both in my calendar, switch between them in google drive, etc.

They did have some layoffs recently.

https://www.oregonlive.com/silicon-forest/2020/07/new-relic-...

This is a good move. I wonder why now, though? Possibly they didn't like to see things like the OpenTracing project adopting Datadog's APM libraries.

https://www.datadoghq.com/blog/opentelemetry-instrumentation...

Sometimes it is. I was heavily involved with a decision between Datadog vs New Relic (plus a few others) at a former "unicorn" startup. We definitely did not want to run the server-side ourselves, but having the client libraries be open source was a major advantage for Datadog. It let us extend them to support our very old Django version and homegrown SOA framework

I agree with 2. I have a presentation at https://www.polibyte.com/2019/02/10/pytennessee-presentation... which goes into how to get started with Prometheus. Not as in "how to set it up", but more about what to instrument and why, how to name things, etc. Despite the title, there's very little in it that's specific to Python.

This is not correct. Both the old Firefox for Android(codename Fennec) and the new one(codename Fenix) use Gecko, Mozilla's rendering engine.

What has changed is that Fenix uses Gecko via https://mozilla.github.io/geckoview/

This is actually pretty straightforward. For example,

`DELETE FROM "foo" WHERE time >= now() - 2d AND time < now() - 1d`

It could also be less than $100k a month (e.g. 2500 c5a.large with a 1-year reservation). At that point you'd wonder why your monitoring bill was 40% of your compute bill.

Also, of course their salary is relevant. The cost of an engineer's time is an important factor to consider when making build vs buy decisions. Usually it's one that argues in favor of "buy", but not always.

Based on my experience at two companies with thousands of hosts on Datadog, this is not true. You'll only be able to negotiate a small discount.

You'll also experience their habit of launching new features, waiting a while for customers to adopt them, then starting to charge extra for them.

Don't get me wrong, Datadog has great products. But they're also great at extracting money from their customers.

Although I've successfully used collectd in the past, I would choose telegraf over it now. This is especially true if I'm sending data to InfluxDB,s ince it and telegraf are primarily developed by InfluxData.

Both telegraf and collectd are mature programs with a large base of well-documented plugins. However, telegraf development is more active, and I find its golang codebase much more approachable than the C codebase of collectd. Obviously, YMMV.

In general though, I wouldn't advise adopting the entire TICK stack. Chronograf is inferior to Grafana. Kapacitor has a super-steep learning curve and is being deprecated by InfluxData. TIG (telegraf, influxdb, grafana) can be a good choice. Prometheus plus Grafana is worth evaluating as well; there's arguably more momentum in that ecosystem than in InflxuDB's.

For better or worse, sure. Here's one case study- https://stripe.com/blog/operating-kubernetes

In my experience the sysadmins would be running in the opposite direction.