295 karma · joined September 28, 2014
meet.hn/city/ca-Smiths-Falls
You almost always want somewhere in the middle, but it’s often much easier to move back after a large jump in one direction than to push towards the middle.
At grid-level, battery tech is challenging, requiring technologies like pumped storage that require particular environments (e.g. damming a river) and can't really be transported.
If this works out you could use excess solar during the day to deoxidize the rust produced, and then run the iron reactor overnight, or on cloudy, windless days.
This makes me want to make a generational/chronological slang chart now
Organizations/universities could compute on data provided by a custodian organization without having to care about data handling.
More around versioning itself, but having a single big merge is a single high risk point. Releasing everything all at once is more likely to have larger and more severe bugs than many small releases, even if you gate the deployed releases behind feature flags.
For one part of the org, occasionally doing 100x data transfers may not be out of the ordinary, while for others it may be exceptional. But it might be anomalous if its 100x data transfer and hitting services no one on your team has ever hit (indicating perhaps scanning/scraping and exfiltrating data, but you don't need to explicitly specify that as an alert).
It’s hard for many to get over the fact that JetBrains is infinitely more expensive than VS code in dollar terms.
I think their goal is to prove that Meta’s negative impact was so broad that most investors had some sort of negative impact outside of their Meta holdings.
Many people expect free things to stay the same forever, which obviously isn't realistic, but this is still going to have a damaging effect on their brand. As well with the free tier, there are a ton of OSS projects, community groups, etc. that will no longer be using Slack, and the network effects will drop substantially. This has been seen a bit with Discord, so maybe they are going all-in on dropping these types of customers.
There can't be _that_ many people who are on the free plan that will now be migrating to paid with this change. If anything, it now incentivizes larger groups (which would generate more revenue) to use the free plan since data is gated by time, not by usage. A slack instance with a few thousand active users on the free plan was basically unusable, 10k messages can be eaten up rather quickly. Now if you only care about the last 90 days (which honestly, isn't a bad idea with Slack to not use it as permanent storage) you can have a much larger group on the free plan.
Just because something is possible doesn’t mean that making it harder isn’t worthwhile. Perfect is the enemy of good, after all.
Custom themes allow you to template on top of the Shopify front end, giving you less control.
1. Mallory registers an account for alice@example.com using a password.
2. Alice receives an account activation email, but doesn’t do anything about it.
3. At a later date Alice registers an account on the service using a social login/SSO (e.g. Google, GitHub)
4. Alice properly activates the account (may or may not be required, depending on the service).
5. The service merges the password account together with the SSO account since they have the same email.
6. Mallory can access Alice’s account with their original password from step 1, while Alice continues to use social login, unaware they also have a password set.
I'm hoping this will make it much more approachable for less "hardcore" users since it can be made to look good, without having to worry about the risks that come from complex UIs.
Growth rate slows after birth, so that would account for some of that. Mother’s also would not need to carry around the weight of the baby, and would be more able to provide for the child.