sciurus

I think you're dramatically underestimating the scope and scale of the problems Twitter had to solve. See the thread below for examples of the sort of solutions they had to build because open source or cloud-hosted solutions weren't available or viable.

https://mobile.twitter.com/danluu/status/1592774269733601281

See https://twitter.com/danluu/status/1592774269733601281 for some of the examples of technical innovation at Twitter.

In your example, how did you install python 3.10 and 3.11? That's part of what pyenv solves for you.

There's definitely been some interest in using amateur HF activity for radar, e.g. https://www.rtl-sdr.com/nils-critiques-the-mh370-wspr-aircra...

Random employees don't get to make that decision in a WFH scenario either. They're hired while residing at a specific location. If they decide to move, they need to clear it with company HR first.

I'll mention this not to disagree with your overall point, but because I've seen it be a source of confusion for some people. In the US federal income tax system, the marginal tax rate varies depending on the tax bracket each dollar of your income falls in.

That is, someone making $200k would pay 10% on their first $9,950 of income, 12% on their next $30,575 of income, and so on. They'd only pay a rate above 30% for the last $35,075 of their income.

You can plug in numbers and locations at https://smartasset.com/taxes/income-taxes to get a sense of how this plays out.

I've personally worked with people who I know made 6-figures of total comp in Germany. Checking the relatively-new https://techpays.eu/, there are plenty of 6-figure entries for Germany. I'm not saying this means it's the norm, just that it's achievable for people whose posts make it to the front page of Hacker News.

You mentioned taxes. When people talk about comp in the US, we aren't taking out taxes. Effective tax rate (federal+state+fica) for a single individual making $200k of salary+bonus is ~30% here. That would turn $200k into $140k take home.

Did you reply to the right comment?

> The fundamental design of Ansible is that you do imperative steps to reach an end state.

No, the fundamental design of configuration management systems (Ansible, Puppet, Chef, Salt, CFEngine) is that they are declarative. You say "this software should be installed, this user should exist, these files should have these contents and permissions, etc" and they figure out the right steps to take on your OS to move from the current state to your desired end state.

You are right though that they can produce unexpected results since they do not describe the entire system from the ground up.

There's a lot of Web-accesible SDR's out there for 0-30 MHz. Here are some based on the KiwiSDR hardware:

List: http://kiwisdr.com/public/

Map: http://rx.linkfanel.net/

There are organizations that help with license enforcement, e.g.

https://en.m.wikipedia.org/wiki/Software_Freedom_Law_Center

https://en.m.wikipedia.org/wiki/Software_Freedom_Conservancy

For those like me who went familiar with it: https://containrrr.dev/watchtower/

Will Larson had a good post on this recently- https://infraeng.dev/efficiency/

This is made of separate codebases with new licenses, instead of being part of the MIT-licensed Redis, in order to prevent AWS from doing that.

For some examples of what to do, see

https://github.com/Yelp/dumb-init

https://github.com/krallin/tini

Yes, Amazon's managed Prometheus is based on Cortex. See the first question at https://aws.amazon.com/prometheus/faqs/

It looks like this is a fork of Cortex driven by the maintainers employed by Grafana Labs, done so they can change the license to one that will prevent cloud providers like Amazon from offering it without contributing changes back.

This is interesting, since Amazon offers both hosted Grafana and Cortex today. I was under the impression Amazon and Grafana Labs were successfully collaborating (unlike e.g. AWS and Elastic), but seems like that's not the case.

I was going to ask what the migration path was from Cortex to Mimir, but I see you've documented that at https://grafana.com/docs/mimir/latest/migration-guide/migrat... . Thanks for the work you've done to make this easy.

> It looks like Mozilla's average SDE salary is about $120k, so yes.

I'm not sure where you're getting that number, but it's much too low.

The figures at https://www.levels.fyi/company/Mozilla/salaries/Software-Eng... better match what I saw when I worked at Mozilla.

You can compare compensation at equivalent levels for Mozilla and peer companies at https://www.levels.fyi/?compare=Mozilla,Microsoft,Apple,Goog... . You'll see that Mozilla pays well, but significantly less than them.

This seems completely unrelated to the story you're commenting on.

> Does anyone actually have normal users run Python programs?

To give one example: Every Dropbox customer does, since their client is written in Python

It's not forking the process that's a concern, it's what happens next. How slow is Django to start up? Do you want to pay that penalty for every request?

I read over the article's links now and what I said service wasn't quite right. This looks like it's based on the stub attribution technique but expands it beyond what those links describe. You can see the server side of the implementation at the links below

https://github.com/mozilla/bedrock/issues/9830

https://github.com/mozilla-services/stubattribution/pull/103

You'll see references to bouncer as well, which is https://github.com/mozilla-services/go-bouncer

I believe you can opt out by having your browser send the Do No Track (DNT) header when you download Firefox. This applies to all analytics on Mozilla.org.

https://github.com/mozilla/bedrock/blob/a8ed6ae9c48c93474fbe...

It's sounds like this is describing the stub attribution feature. You can read more details at

https://wiki.mozilla.org/Firefox/Stub_Attribution

https://bedrock.readthedocs.io/en/latest/stub-attribution.ht...

Hi Anton,

I see at https://github.com/terraform-aws-modules/terraform-aws-eks/c... that you have dropped the additional terms of use. I think that should alleviate the concerns people had about a license change. I appreciate you listening to your contributors and users feedback on this emotional topic.

Putin khuylo!

This license change appears to affect not just the EKS module, but all the modules in the terraform-aws-modules organization.

For example, here is the same change in their VPC module: https://github.com/terraform-aws-modules/terraform-aws-vpc/c...

It's actually the opposite! To pick a representative example

    Current generation:
    m6i.large: $0.0960
    m6a.large: $0.0864
    m6g.large: $0.0770


    Previous generations:
    m5.large:  $0.0960
    m4.large:  $0.1000
    m3.large:  $0.1330
    m1.large:  $0.1750