s3cur3

The biggest thing missing from this analysis is "is there a business case for supporting those 2% of users?". (Maybe, maybe not.)

The second biggest thing is progressive enhancement. The author picked a CSS feature (nesting) that is basically all-or-nothing: the site will basically be entirely broken for those 2% if you swap Sass for native nesting. Most features aren't like that; maybe the site won't look pixel-perfect on old browsers, or one bit of functionality won't work, but by and large it will still be functional. In those cases, I think it's a much easier decision in terms of where to draw the cutoff.

Having been a happy customer of Blacksmith, Depot, and Ubicloud at various points (all three of which offer GitHub Actions runners at cheaper prices than GitHub themselves), I agree the billing here is weird. It's worth pointing out, though, that you have to use a lot of CI minutes to incur a $1000 bill. You're well outside of hobbyist levels, and that same level of usage would have previously cost double from GitHub themselves. This a business with serious compute needs, being asked to pay real money.

I dunno… it’d break a looooot of code if structs were suddenly not also maps. My bet is this becomes a new option you have to manually migrate to.

No sweat, I get it! :D

Author here! I've not been compensated by the Petal Pro devs at all. I've interacted with them exactly twice—once in support and once to submit the world's tiniest PR. I'm just a happy customer.

(If that's not enough, you can dig in to the Petal Components repo and see I'm not a contributor.)

I had no idea Gumroad et al. took their percentage on top of taxes. Seems shady.

It's... kind of his¹ thing. :) For instance: https://austinmeyer.com/why-does-god-hate-lancairs/

¹ Austin Meyer, creator of X-Plane

Enbala | Denver, CO / Vancouver, BC / Remote for strong candidates | Full-time | https://www.enbala.com

We're working to make the future of energy production more sustainable by helping energy utility companies balance the grid. This includes everything from helping lower peak energy usage (removing the need to, say, build an expensive new coal power plant that would only be run a few days a year) to balancing decentralized production from household solar.

Our back-end is written primarily in Elixir, and our front-end is Elm. We also have microservices running Python on AWS Lambda. We have a strong cultural focus on things that make devs' lives better day-to-day—things like testing, being kind & helpful to one another, code reviews that are valuable for both parties, continual improvement in our processes, etc.

Selected open roles at the time of this writing:

- Software Development Engineer in Test (SDET)

- Senior DevOps Engineer

- Senior Security DevOps Engineer

- Senior software engineer (Elixir)

- Senior software engineer (Python)

- UI/UX product designer

More info here: https://www.enbala.com/about/careers/

Enbala | Denver, CO / Vancouver, BC / Remote for strong candidates | Full-time | https://www.enbala.com

We're working to make the future of energy production more sustainable by helping energy utility companies balance the grid. This includes everything from helping lower peak energy usage (removing the need to, say, build an expensive new coal power plant that would only be run a few days a year) to balancing decentralized production from household solar.

Our back-end is written primarily in Elixir, and our front-end is Elm. We have a strong cultural focus on things that make devs' lives better day-to-day—things like testing, being kind & helpful to one another, code reviews that are valuable for both parties, continual improvement in our processes, etc.

Selected open roles at the time of this writing:

- Software Development Engineer in Test (SDET)*

- Senior DevOps Engineer

- Senior software engineer (Elixir)

- Senior software engineer (Python)

- Product owner

- UI/UX product designer

More info here: https://www.enbala.com/about/careers/

* On a personal note, we really value our QA folks and treat them well. (I think the posted salary range hints at that.) We want QA deeply involved with the whole software development lifecycle, rather than something that gets tacked on at the "end" (ha!) of development.

Enbala | Denver, CO / Vancouver, BC / Remote for strong candidates | Full-time | https://www.enbala.com

We're working to make the future of energy production more sustainable by helping energy utility companies balance the grid. This includes everything from helping lower peak energy usage (removing the need to, say, build an expensive new coal power plant that would only be run a few days a year) to balancing decentralized production from household solar.

Our back-end is written in Elixir, and our front-end is Elm. We have a strong cultural focus on things that make devs' lives better day-to-day—things like testing, being kind & helpful to one another, code reviews that are valuable for both parties, continual improvement in our processes, etc.

Selected open roles at the time of this writing:

- Senior devops engineer

- Senior software engineer

- Software engineer

- Product manager

- UI/UX product designer

More info here: https://www.enbala.com/about/careers/

Enbala | Denver, CO / Vancouver, BC / Remote for strong candidates | Full-time | https://www.enbala.com

We're working to make the future of energy production more sustainable by helping energy utility companies balance the grid. This includes everything from helping lower peak energy usage (removing the need to, say, build an expensive new coal power plant that would only be run a few days a year) to balancing decentralized production from household solar.

Our back-end is written in Elixir, and our front-end is Elm. We have a strong cultural focus on things that make devs' lives better day-to-day—things like testing, being kind & helpful to one another, code reviews that are valuable for both parties, continual improvement in our processes, etc.

Selected open roles at the time of this writing:

- Senior QA test automation engineer*

- Senior software engineer

- Software engineer

- Product manager

- UI/UX product designer

More info here: https://www.enbala.com/about/careers/

* On a personal note, we really value our QA folks and treat them well. (I think the posted salary range hints at that.) We want QA deeply involved with the whole software development lifecycle, rather than something that gets tacked on at the "end" (ha!) of development.

Enbala | Denver, CO / Vancouver, BC / Remote for strong candidates | Full-time | https://www.enbala.com

We help energy utility companies balance the grid. This includes everything from helping lower peak energy usage (removing the need to, say, build an expensive new coal power plant that would only be run a few days a year) to balancing decentralized production from household solar.

Our back-end is written in Elixir, and our front-end is Elm. We have a strong cultural focus on things that make devs' lives better day-to-day—testing, being kind & helpful to one another, code reviews that are valuable for both parties, continual improvement in our processes, etc.

Selected open roles at the time of this writing:

- Product manager

- QA test automation engineer

- Senior software engineer

- Software engineer

- UI/UX product designer

Learn more & apply here: https://www.enbala.com/about/careers/

Griefing, yes. The audience for our mobile app skews young and, shall we say, less "serious aviators" than the desktop sim, so to some degree people like that you can buzz a 747 on short final in an F-22. :D

Long-term we've talked about things like a reputation system, where flying responsibly would earn you points to get into a separate "world" filled with people who also want to do more serious flying.

In general, we send each player all the planes that their in-game map could possibly show (which is usually something like 140 statute miles by 140 statute miles).

We could one day be smarter about this and only send you everything if your map is actually open, and otherwise limit it based on your field of view. That hasn't been a priority yet, though.

The core of the X-Plane server is our RakNet UDP protocol, which is open sourced under the MIT license here:

https://github.com/X-Plane/elixir-raknet

It's not a full game server, but the "Usage" section of the README provides a sketch of what the rest of the server (the part that implements the business logic) looks like.

Correct! Sorry about that. :)

The limitation is more about the number of players we can have in the same area—if you had a bunch of players equally spaced around the globe, I'm pretty sure we'd saturate the Ethernet link before running out of CPU on a big (say, 32-core) VM. The CPU cost (and outbound network bandwidth) of a player scales with the square of the number of other players who can potentially "see" them.

In my scalability testing, we could handle upwards of 1000 players in the same 50 nm by 50 nm square on my 8 core dev workstation. That's pretty far beyond the limit of what would actually be _fun_ to fly the sim with. It becomes pandemonium even with 100 planes in the same area. We could easily do a dozen pockets of 100 planes in the same area even on our current 8 core VM.