105 karma · joined March 29, 2018
Engineering @ ShareBuilder 401k | Seattle, WA | he/him
Now overnight it's just gone.
That being said, I also play golf and use a Golf GPS tracker, Pokemon Go, and social media most of the day. Coming from an iPhone 11 Pro which had incredible battery life, it is a major change. BUT, the lower battery life is manageable. I have external battery packs, I prepare for these types of things. I can make it last when I need it to.
---
Locking up, I think it comes from moving from my old iPhone 11 Pro to the non-pro variant. I felt a little spoiled with the Pro model.
Sure the battery sucks and the phone locks up from too many things happening sometimes, but those are perfectly fine trade offs for a phone that fits into my life and isn’t my life.
When I bought my 13 mini I also bought the new iPad mini to have a larger device for content consumption and the combo is lovely
---
I have created a few NFT / Web3 pages using that template. For the most part, a lot of Web3 UIs are just client side sites that connect to on-chain data, so another super lean use-case for simple HTML pages.
I also love Vue and the simplicity of remote html resources/dependencies for simple sites. I created a single html file VueJS template that has a bunch of resources out of the box for things that I commonly want if I want to create a quick simple site.
Check it out -> https://vue-template.spaghet.me
The beauty of the site is its basically a quine. You can get started by just running: curl https://vue-template.spaghet.me -o index.html
I had never seen some of this IP charting and stuff and in his video he does a lot of similar stuff.
Being able to scan https://github.com/avelino/awesome-go, https://github.com/bkrem/awesome-solidity, and https://github.com/gianni-dalerta/awesome-nft for general resources, projects, guides, or just general information was a nice resource to have in my back pocket.
I think your point is valid, but it's also a personal expectation of what you get out of the resource. I think the fact that they are open ended helps both developers who are trying to reach an audience and people who are browsing for new tools, ideas, etc.
I like to make websites with the Spotify API to interact with my music in silly ways. If you have a Spotify account give it a try!
How it works
When you log into the site using Spotify, I load all your Liked Songs from your account and categorize them alphabetically. From there I simply pop elements from the letter arrays as needed to spell out the words.
I have data mined 20,000~ of the top songs on Spotify to have a fallback dictionary of songs so that anyone with an account can at least create something.
Everything is done client side in the browser and I do not collect any information whatsoever. Just a little side project.
Other Spotify Apps
SpotifyTelevision - 2018 - https://immannino.github.io/SpotifyTelevsion - Easily stream the music videos for your Spotify Liked Songs & Playlists
Tv-Lite - 2020 - https://tv-lite.spaghet.me - Similar to above, but lets you control your music through Spotify, and will find the music video and seek to the appropriate part of the video as you're listening to the song.
[You can read more about why from smart people on StackOverflow](https://stackoverflow.com/a/8942455/10783165)
Websites like https://devdocs.io/ do this exact thing through desktop Progressive Web Apps.
Basically you keep your markup & source as static as possible, and allow a serviceWorker to cache those files locally. This can also be done with a SPA, but if we're talking docs, you get the benefit of only having to update a specific page if its raw html.
I think theres some validity to "you're the most productive with whichever tools you're most comfortable/familiar with", but I think people don't realize the levels of abstraction that come with web development.
( My learning path was: Angular 2 -> 7 + sucking at CSS, Angular + Tachyons (learning how to style), -> Angular + Custom CSS for everything, to Vue + Custom css -> Plain HTML + Plain CSS. )
Its like the more you learn the more you understand the boilerplate of libs/frameworks, but also understand what these large tools accomplish for you, and then you learn to appreciate how powerful & simple the "vanilla" web can be if you open your mind to it.
I think its a great tool for someone not comfortable in the space. As you use it more and more you get a good understanding of what the properties are (using margins, paddings, headers, centering text, etc) + couple that with the VSCode plugin, it gives you the real css snippets for what the properties mean. Then over time you start to understand what properties make your html look that way, and then get comfortable writing css from scratch.
+1 Tachyons
I started typing a reply out to someone's criticism of this, and it had me think of it this way.
I have my own personal stylesheet that I use as a plugin for overriding blog styles (just because I like to read text formatted in a specific way, a lot of blogs aren't very readable IMO). This style of library kinda extends that where the end user can "customize" or make the site look how they want it to (not that it's something people should be considering when building their blogs, but I think its fairly normal for people to have opinions on these things).
---
I especially like it for quickly prototyping internal tools/sites at work. A lot of times I want something to look clean but don't have the bandwidth to really customize a lot of stuff. This allows you to write CSS for what you need, but have the overall page styled for you with minimal effort. (Also building your own css templates like this helps teach generic css. I think it's a good skill if anyone is within proximity of the web).