matterhorn2000

Question is not whether they were designed to be addictive (of course it was - that’s the product), but whether it can be proven.

Had a use case recently where a vendor dataset of approximately 1.5 million companies needed to be searchable. Fiddled around with Postgres for quite a while, not really managing to get good results while keeping query times below 1 second on average. Ended up going with elastic search instead but I hate the additional complexity. Anyone with similar experience or who actually made a similar setup work with pgsql?

Tried the same thing with Jumpcloud. Used it for a while. Disabled all users and moved on. 3 years (!!) later some debt collection lawyer contacts me about my $8000 bill. Wtf. Good luck collecting that.

I know they’ve said it’ll be integrated into the main GitHub site, but the way it’s pitched on the landing page makes me wonder if they’ll roll it into an individual subscription like the Copilot product.

Yes. Initials of authors and contributors.

The imperialist approach you have may be better suited for a different century.

Contrary to everyone else I really like the new design.

The metadata is placed to the right as it should have always been. The languages are in the sidebar and are visible without me remembering that typescript is somewhat dark blue.

Also the new look is more modern and unlike most people here I am not afraid of change.

I don’t really see the reason to credit here. As a product developer you obviously draw inspiration from your competition, and do whatever you need to keep up and hopefully get ahead. This is in my opinion exactly the same as Instagram implementing stories from Snapchat. Doing so is perfectly fine, entirely legal, and in this sense being a gentleman and not implementing the feature will cause you to be set back compared to the competition.