Nice work, it even has a deploy to Heroku button!

Honestly, I think it's pretty lame trying to profit from arbitrage on SW prices like that. $3 per alert? Really?

Great job making an OSS implementation.

They're providing you a service by coding it up, hosting it, dealing with customer service requests and Southwest's lawyers, etc. Seems fair to charge $3 to provide the service of saving you money. Also seems fair to try outcompeting them by providing that service for free at your own expense.

> pretty lame trying to profit from arbitrage

Lame? Possibly. Profitable? Probably.

> pretty lame trying to profit from arbitrage

It's actually quite stupid. If they did not ask Southwest for permission, they are asking to be sued, especially when you charge people money.

I think you are conflating multiple things. There's several JS styling libraries have literally zero configuration (and don't involve build tooling, etc). They "just work" out of the box.

Plain pseudo classes are supported (e.g. :hover), but since descendant/child combinators aren't supported, a parent :hover can't change a child style. But any element can still have :hover styles.

That seems like it would be a big roadblock to doing much useful with it. Is it impossible, not yet supported, or supported but not easy to do?

Someone submitted a proposal on how to support descendent/child combinators. It's certainly possible, but I wrote a response on why it would would potentially involve tradeoffs: https://github.com/rtsao/styletron/issues/27#issuecomment-26...

At-cost version web version of this using Lob API: https://github.com/scott113341/post

This is awesome!

For generated HTML docs or websites, this is still not ideal because you have to commit generated code into your master branch.

You can even use Travis to automatically generate and deploy your docs/website, which I find much cleaner and convenient than manually publishing or committing generated code.

https://github.com/L33T-KR3W/push-dir makes it easy to publish a directory to gh-pages (even .gitignored directories i.e. build/).

Agreed. I use https://readthedocs.org to take care of building and hosting documentation, and it's really handy.

The generated code is going to be "committed" somewhere, so I am not sure this is much of a down side. I suppose one might worry about storing too much history. Is there a way to pair down history for everything in docs/ ?

Slightly related, I push my site's generated code from the `public` directory of my repo directly to the `gh-pages` branch using git's subtree push:

  $ git subtree push --prefix=public origin gh-pages

It's not a $7 billion "exit". It's an investment for a 20% stake in Didi for $7 billion, which presumably will increase in value as Didi continues to expand in China, especially with less need for ridiculous spending on driver incentives since they will no longer be competing with Uber.

Uber probably had something in the ballpark of 20% market share in China so it sounds like the two decided to simply make peace and become profitable together instead of duking it out for years on end and throwing away billions.

Its not a 20% stake.

"Uber Technologies will receive 5.89 percent of the combined company with preferred equity interest equal to 17.7 percent of the economic benefits."

You answered your own question? You don't - it's sunk costs.

As a loss obviously, a sunk cost is exactly that: sunk

Didi and Uber have been raising outrageous amounts of money to outspend each other on driver incentives. Seems like a smart deal for both sides.

This is very similar to https://github.com/Khan/aphrodite and https://github.com/rtsao/react-stylematic

One of the biggest differences between ReactCSS and other solutions is that all of the style merging is done in the style object and not in the HTML. This keeps the markup clean and puts all style and style logic in one place.

<span className={css(styles.blue, styles.small)}>

vs

<span style={ styles.button }>

This is awesome. I've been using Electron for browser tests which has been a big improvement over Phantom, but setting up xvfb can be a pain.

I actually don't like this change.

Private contributions don't benefit the greater community unless the project is eventually open sourced.

The contribution graph was a nice way to show off how much one contributes to open source, thereby encouraging folks to contribute to open source projects. It's a vanity metric in the first place, so why not use it to help motivate more contributions to open source software?

Because Github has a different incentive: they want as many hobbyist developers as possible using private repos.

They are definitely working on strengthening their value proposition for paying customers. And I really can't blame them, as they are competing against free. GitLab is free. Bitbucket and Microsoft Visual Studio Team Service (VSS) are free for 5 or less users.

What they (GitHub) really need to work on, if it isn't on their radar is a marketplace/extension system. And this is where I think Microsoft may leap frog everybody.

I've only spent a day looking at building extensions for VSS, but I'm really impressed by how much thought they put into making 3rd party solutions, first class citizens. And I think this comes from the fact they understand enterprise.

In enterprise, there are so many crazy edge cases and if you don't have a reasonable answer to how you can address them, customers will pass on you.

We released this last October as a way of broadcasting the work we've been doing in the ecosystem thus far: https://github.com/integrations. There's lots more to be done in that area, and we're learning a ton from our integration partners along the way. Enterprise readiness is one of the big areas we want to keep refining too.

I hope supported injection points is something that will be supported in the future. The way of integrating on top of GitHub with a browser extension, is really a hassle and it's the reason why I'm going to discontinue my Chrome extension.

I would like to bring advanced Git analytics and search to GitHub, but it's not worth the effort considering how easily I can drop it into Bitbucket and VSS.

I like it because if a potential employer were to look at my github it'd look pretty lame. Seeing a boatload of anonymized activity sends the message "hey, what you see mught not be indicative" instead of them saying meh and moving on

I agree. Unfortunately I thought the same was with GitHub's "private repositories are paid" idea, until they switched to unlimited ones.

Anyway as a friend of mine says : "GitHub is Facebook for developers", so I guess the social features are still playing a role in the decisions.

It also makes it somewhat obvious if you quit or got fired from a job (that uses github).

You don't get green boxes for repositories you no longer have access to.

Actually, I found after enabling the new feature I regained a lot of squares from a private organization I am no longer a member of. These squares didn't even show up when I was logged in before.

This is so weird. -.-. I'm having the opposite.

Only if you remove your work email from your account. I still have green boxes for things I don't have access to. But I made sure to leave my work email in my account settings, if you remove it, then you lose all the green boxes.

Do you mean that the committer email is used? (so, if you use your personal email on your work .gitconfig, you're fine already)

Yes, or if you you use the hidden <user_email>@users.noreply.github.com.

I did some contract work for several months where they just gave me access to the organization and removed it when I left. I have nothing for that time.