Apologies if this seems snarky but it would be far more useful if you could explain your point rather than a generic condescending "[you] haven't delved into Tailwind on a non-trivial project".
It's the case with most UNIX CLI tools and if the author's complaints are true, do we then have to change all UNIX CLI tools? Maybe? The reality is we can't and probably don't need to.
PS5 drives must also be pre-approved by Sony, supposedly due to strict hardware requirements, like 5.5GB/s[1] sustained bandwidth. I personally think it's silly, sure, bigger numbers mean better performance but I would be surprised if most games wouldn't work perfectly fine with a nowadays average SSD.
I was making an analogy in my mind between API function names and song titles. IANAL but I thought at first that it doesn't make sense to copyright song titles, they are generic and uninteresting most of the time but after giving it further consideration I realized that some can be quite meaningful, for instance everyone recognizes 'Stairway to heaven' and 'Bohemian rhapsody' therefore, even though it seems a bit silly I wouldn't be surprised if those song titles are in fact copyrighted which could mean copyrighting function names is not that different. I then decided to actually google this and found out that:
>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.
A clean history with proper commit names can work as a change log for you app. We actually did that and it worked quite well. In Azure DevOps the release pipelines have access to the list of commits since the previous release so one only has to simply take the titles of those commits to build it.
> 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.
I'm sure it did not or maybe it was not enabled by default. I distinctly remember having to turn 'condensed view' back on because the thumbnails were taking so much vertical space.
edit: Just noticed who I replied to. I guess you would know better.
> This may have been true a decade ago, but editors like Visual studio code now have remote editing abilities over SSH.
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.
No. Everything is 0s and 1s after all. Take for eg. a byte. It has 8 bits and by permutating all the 0s and 1s you end up with all the possible values of a signed byte; all the numbers -128 to 127. So now, if you were to copy a byte from a random memory location that byte will just contain a permutation of 0s and 1s which when interpreted as a signed int, will simply contain a number between -128 and 127.