862 karma · joined April 20, 2025
Anyway, here's few videos of interest:
https://www.youtube.com/watch?v=WwkuAqObplU
https://www.youtube.com/watch?v=IroPQ150F6c
Odin also supports SoA natively https://odin-lang.org/docs/overview/#soa-data-types
But more on the topic, i would say calling ffmpeg as external binary to handle some multimedia processing would be one of those cases where simple is better.
Generally, I would say that implementing your own solution over an external one(like a library, service or product) will always fall under this umbrella. Mostly, because you can implement only what you need and add other things that might be missing or adjust things that do not work exactly as you'd needed them to, so you can avoid any patches, translation layers or external pipelines.
For example, right now I am implementing my own layouting library, because Clay bindings for Go were not working or manual translations were missing features or were otherwise incomplete or non-functional. So I've learnt about Clay and on what principles it was built, by Nic Baker, and wrote my own version in Go. It has little over 2k lines of code right now and will take me about two weeks to finish, with all or most features I wanted. Now I have a fully native Go layouting library that does what I need and I can use and modify it ad infinitum.
So I would say that I equal a "dumb solution" with "my own" solution.
PS: looking back, when I used to work in advertising/marketing/web agency, we used to make websites in CMSs(I did Drupal, colleague did Wordpress). Before my departure from the job in general, I came to a conclusion that if we would be using static website generators, we could have saved unimaginable amount of work hours and deliver the same products, as 99% of clients never managed their websites as by nature of the job, we were doing presentational websites, not complicated functional ones. And when they did, they only needed such tiny changes that it would make way more sense to do it for them for free upon request. For example, imagine you charge someone 5000€ for a website that takes you two months to ship, because you need to design it, build it functionally, fit the visual style and tweak whatever is needed. If you'd use static website generator, the work would take two weeks - a week for the design and a week for coding the website itself. Now you've saved yourself 6 weeks of work while getting paid the same amount of money. Unfortunately, I did not have a chance to try this out and force a new direction at the company as it was at the end of my career.
I do not think this has gone away. Yes, market saturation waters everything down to the common denominator. Podcasting is no different than any other commercial or public market. But there will be always outliers. The only difference is that back in the old days(early 2000s and 2010s), your choices were limited, which made it easier to pick. Today, you have to invest time and effort and hunt down those good podcasts that match your interests by sifting through a ton of the noise(badam, tssss).
I was big into podcasts, even started my own. Until I realised that without interesting guests to bring in week after week, there is no point in it.
But I think that the main issue is, and has been for a very ling time, that there is really not a single good user interface for consuming podcasts, especially offline, managing podcasts or discovering new ones, keeping tabs on what is going on with individual shows or even getting recommendations on and being able to purchase your own podcasting kit, so that you don't have to research and learn about audio, video and other related things that might detract someone from thinking about starting their own podcast. And also all of this in packaging suitable for different consumption situations - walking, driving a car, riding a bus, being at work or at home. Yes, there were many various apps and websites, but they all suck and lack in any useful feature. They essentially just aggregate podcasts and offer RSS feeds. That's kindergarten bs.
There's your $1B idea.
Good times, I'm glad it is still around.
martial arts
serious running
non-web programming
cigar smoking
shaving my head
growing my beard
carnivore / keto / nutrition education
using soap for showering instead of gels
dressing for comfort(now i wear only sportswear)
buying larger shoes
grounding my own coffee instead of buying grounded coffee due to much lower variety compared to whole bean coffees
getting rid of google and all its services(i have YT account but i have no "channel")
not wasting time commenting on YT videos or tweeting as it's a fool's errand
investing
Also, disregard any "success stories", as they are 99.999% funded by a massive piles of money and immeasurable amount of connections in high and right places, that you never hear of.
HTML DOM uses retained model as it would be unimaginable to completely throw out the entire DOM and rebuild it anew with every frame. But React, Vue and other libraries use immediate mode to communicate with HTML DOM. They might internally have retained mode, but in the end they only perform mutations based on their internal differences.
So the whole web ui is layer upon layer of immediate, retained and hybrid modes all talking to each other. Now imagine how much wasted resources all of this layering implies :)
Another interesting fact is that when you have opacity or translucency in web ui, the browser render the background elements off canvas and uses it as background for the element with the opacity in order to avoid issues with various elements seeping through in many unexpected ways.
tl;dr this topic has been thoroughly discussed in here https://www.youtube.com/watch?v=XYFBOIr6n_s