Well, there's also the bit about not having to deal with a long list of fees and onerous requirements like many states have, when all you're trying to do is start a business, build a product and hopefully find some paying customers.
tl;dr Uninformed rant about the evils of blockchain and crypto-related endeavors
No nuanced analysis of an emergent technology and its growing pains and no mention at all of the benefits of decentralization.
Oh, and the author also fails to point out that there are NFTs which go beyond simply representing ownership. They are used for unlocking premium content, making game assets portable across games, acting as a proxy for real-world assets and many other use cases not yet as high profile as art and sports NFTs.
One oft-overlooked aspect of NFTs is their scarcity and authenticity by virtue of license rights. For instance, NBATopShot moments are desirable because they are licensed by the NBA. So if you were to clone great basketball moments and create an alternate, it would neither be authentic nor legal.
If NFTs gave you copyright, that would be something. Even owning part of the copyright would be valuable, you (with your co-owner) would be able to decide how that piece gets used, sub-licensed, adapted, and maybe even collect royalty.
Cryptographically-verifyable bragging rights attached to a JPEG don't sound as interesting.
Looks promising, but it's hard to tell without a more full-featured demo.
I'm comparing this to Node-RED [0] which is pretty robust and has a large ecosystem. Ultimately, I think the value in diagramming platforms is not just in the software, but the community around it that creates plugins/extensions for different use-cases.
Hal's post was so inspiring – thank you for sharing.
The bit about having to finish the documentation was particularly noteworthy. Even when writing code laboriously through eye moment, Hal didn't lose focus of the importance of documentation.
This was a great article and I learned a few new tricks.
I learned CSS over the years by gradually solving problems I encountered building apps. Compare this to people learning CSS now as evidenced by the #100DaysOfCode tag on Twitter. The learning technique is comprised primarily of using gradient-heavy, absolutely positioned HTML elements to create a photo-realistic, 3D rendering of objects.
The results are pretty amazing, but I have my doubts about whether these skills are easily translatable for building an interactive, responsive UI. Some examples:
I posted this all to a community called "Forrst" (think of it like twitter, but curated for developers and designers).
I spent time giving feedback on other peoples work, I tried to ask insightful questions https://twitter.com/umaar/status/823915022917271552 to have an open discussion, I spent hours replying to comments every few days.
Then one day, Forrst got acquired by Zurb https://zurb.com/blog/zurb-acquires-forrst and later on it got shut down, and with that, I lost access to huge amounts of my work which I hadn't stored anywhere else (some stuff has been archived online, but not everything).
When it comes to web development tips, I now self-host on my own website and it's a really good feeling knowing that it'll be preserved: https://umaar.com/dev-tips/
A lot of people make games or fun projects for #100DaysOfCode when their job might be updating a CRUD MVC app using Y framework. I think as long as it puts them in the "coding" mindset it's worthwhile.
I agree with that 100% — if it isn't fun, it's work. And if you build enough knowledge about how CSS works in general, when it comes to implementing specific layout or responsive design techniques you have a good understanding of the basics to build upon.
https://developer.chrome.com/blog/new-in-devtools-73/
https://developer.mozilla.org/en-US/docs/Tools/Debugger/Set_...