🌱 Advice for How To Make Sure You Never Create Anything
Are you sometimes at risk of creating? Personally I, from time to time, come very close to writing something, so my advice here is geared towards that. However, it can hopefully be extrapolated to help you if you’re tempted by other creative endeavours as well.
- If you get an idea while writing a post, you should always finish this new idea before finishing the original one. This, of course, cascades to new ideas you get while working on the second one, etc.
- This also applies to expansions within an idea. You can always increase the scope of a project!
- Let every piece of work be your Magnum Opus.
- However, if as much as a single piece of your idea doesn’t materialise quite like how you wanted it to, scrap the entire thing. No matter how much work you’ve put into it, and no matter how much value there’s still left.
- Don’t post anything, unless you’ve covered every nuance, use case and possible objection. Don’t post ideas or thoughts — post rigorous conclusions.
- You can’t mention a concept/item without also explaining everything about it, in case someone isn’t familiar.
🌱 A Shortcut for lite-youtube-embed
YouTube embeds take up way too much on a site - so luckily someone has made lite-youtube-embed.
“Renders faster than a sneeze.”
Provide videos with a supercharged focus on visual performance. This custom element renders just like the real thing but approximately 224× faster.
First you have to include some CSS and JS on your site. 1 And then when you want to embed a video, you could just add this piece to your post/page:
<lite-youtube videoid="CItvhGl__Mk" playlabel="Play: Beatenberg - Wheelbarrow (Official Music Video)"></lite-youtube>
This will embed the video, but over 200x faster - nice!
However, you have to manually add the videoid and the video title.
And they’ve also made a variant named “Pro-usage: load w/ JS deferred (aka progressive enhancement)”, which I think is even more optimised. But then you have to add all of this:
<lite-youtube videoid="CItvhGl__Mk" params="controls=0&rel=0&enablejsapi=1" style="background-image: url('https://i.ytimg.com/vi/CItvhGl__Mk/sddefault.jpg');">
<a href="https://www.youtube.com/watch?v=CItvhGl__Mk" class="lty-playbtn" title="Play Beatenberg - Wheelbarrow (Official Music Video)">
<span class="lyt-visually-hidden">Play Video: Beatenberg - Wheelbarrow (Official Music Video)</span>
</a>
</lite-youtube>
Why I Don’t Love Web Apps
And a call for help
I absolutely get why companies make web apps instead of native apps. Why juggle tons of platforms and languages if you don’t have to? Furthermore, being on the web makes you free from platform gatekeepers!
It can also benefit users, by giving the same experience everywhere, making more software cross-platform and accessible on more niche platforms, and more.
And if a developer has 100 hours to develop a client for their service, the user experience very well might be better if they spent all of it on a web app, instead of spending 25 hours on four different native clients.
There’s also a bunch of terrible native (or “native”) apps. One example is phone apps that simply are terrible web wrappers that just want to be able to track and notify you more than they can in a web browser. 1
When I say that I prefer native apps, I don’t mean that there are no great web apps (like Figma) or bad native apps. My point is that the ceiling of the latter is higher, and that all the best apps I’ve tried are native.
Chromium and Nested Backdrop-Filters
If you’re like me, you sometimes get these small (often technical) problems, that you work on for so long — and you refuse to surrender.
I had this with CSS a couple of months ago:
I had a menu, that had transparency and blur, and then I also had a submenu that I wanted to have the same. But the submenu just. wouldn’t. blur!
It works perfectly in Gecko and WebKit — but after countless hours, I found the problem: If an element has a backdrop-filter, Chromium won’t let its children have it as well. 1
I had to design around it, and moved on with my life.
A few moments later…
I recently moved to Micro.blog. And one day I was scrolling down my timeline…
Then I opened the submenu:
There it was — the same bug! I’m not alone!
The fix
✉️ 🌱 To SigmaOS’ CEO: This Is What I Don’t Like About Arc’s Direction
I really, really like the Arc browser. But as I alluded to in this post, I have some reservations regarding it, and don’t feel like it’s going in a direction that I like. In the post, I said that I might try SigmaOS again — and I am. 1
I mentioned this in their community Slack, and their CEO, Mahyad, asked me what about Arc’s direction I don’t like. I must say, the dev team seems very active, nice, and open to input! So this post is my reply to his question.
(And here’s a link straight to the TL;DR at the bottom.)
Hi, Mahyad — and thanks for asking! I wrote a blog post called «I Just Want A Nice Browser!», which might give you a hint, heh.
And let me also say that I’m a bit worried about your direction as well — but I’ll come back to that. 😉
Two fundamentals I don’t love, but that I don’t need to go too much into
- I don’t love that Arc is built on Chromium — as I think Google has more than enough power over the web as it is.
- I’m not against supporting any VC funded company — but in combination with an unclear business model, I become more skeptical and worried if our incentives align. 2