byte1918
'unlimited backup and storage of the photos' was the market pitch, whether people read the TOS is another thing. I can see why some people would feel unhappy with this and I can't blame anyone for that but on the other hand I wish we would stop taking these vague market statements at face value. 'free', 'unlimited' and 'forever' can never go together in a capitalist market. And I'll abruptly stop here because I would derail into things like law and ethics which, I think, are out of my scope.
> while competitors to it went out of business
This is honestly a tragedy that happens all across the industry at the moment.
Wouldn't it be 'bait and switch' if they did that after less time, say 1 year? 10 years is more than reasonable. And if you disagree, that's fine, but I'm curious to hear what number of years would you consider reasonable then? I'm not excited about the news either but I think it's _fair_.
I agree with you for most part. Mixing unit tests with integration tests is a recipe for failure.
[1] https://www.pushsquare.com/guides/which-ssd-drives-will-be-c...
>Generally, copyright law protection does not extend to song titles because they usually are short and lack sufficient originality. Therefore, you can (and often do) have multiple songs with the same name, and the first to name their song, for example "Crazy," does not have the right to stop other people from releasing their own songs named "Crazy." An exception to this is that some long titles may be found to have sufficient originality to be afforded copyright protection. I suspect that my friend's song entitled "The Concept of the Quantum-Mechanical Bodymind Has Sparked a Great Idea" is one of them. [1]
The whole article from [1] is worth reading. I wouldn't be surprised if the final verdict will be similar to song title laws from the music industry.
[1]: http://www.askamusiclawyer.com/archive/is-my-song-title-prot...
> fetchData();
> updateBreadcrumbs();
> }, [location.pathname]);
> There are two use cases, the "data-fetching" and "displaying breadcrumbs". Both are updated with an useEffect hook. This single useEffect hooks will run when the fetchData and updateBreadcrumbs functions or the location changes.
Is this right? Wouldn't they only update when `location.pathname` changes? Also, there should be a whole discussion on `useCallback` which is not used here and it can be quite important, plus linters would complain of missing dependencies for the useEffect.
edit: Just noticed who I replied to. I guess you would know better.
> Thousands of subsequent experiments have confirmed (and elaborated on) this finding.
VS Code and vi have different use cases. Contrary to what you said, most people are not going to open VS Code to make a quick edit to a config file. If that works for you, fine, but the overhead of starting electron is significant.
> 1. The system does not require a central authority, its state is maintained through distributed consensus.
https://en.wikipedia.org/wiki/Cryptocurrency#Formal_definiti...
(1) - https://addons.mozilla.org/en-US/firefox/addon/leechblock-ng...
Edit: From wikipedia https://en.wikipedia.org/wiki/Set_(card_game)
> Three cards from a Set deck. These cards each have a unique number, symbol, shading, and color, and are thus a "set".
this reminds me of https://www.theregister.co.uk/2019/04/23/hertz_accenture_law...
https://www.apple.com/uk/shop/go/macbook_pro/select this 404s for me.
If you want to unpublish a package after 72 hours have passed, contact npm Support. For more information about why we don’t allow users to unpublish packages after 72 hours, see our unpublish policy.
https://docs.npmjs.com/unpublishing-packages-from-the-regist...