Even though I understand this need, I'm still very keen on audio software that tries to break out of the 'everything is a knob' paradigm when it makes sense.
927 karma · joined January 31, 2013
Even though I understand this need, I'm still very keen on audio software that tries to break out of the 'everything is a knob' paradigm when it makes sense.
But isn't it still better to be using wind turbines 75% of the time when it's windy, and gas/coal only 25% of the time when it's not? Surely even without adequate battery storage that's an improvement?
Speed equals money. The same app running at twice the speed uses half the compute resources. You may also gain a lot of simplicity if you don't need to distribute your architecture so early on.
I agree that on the whole, people will continue to go for the free option, but I'm just glad that some options are appearing to pay, which rebalances the incentives a bit.
What really excites me is that is that I'm paying them. That sounds odd, but seriously. It's incredibly refreshing to know that the company providing my search results has an incentive to make things better for _me_ and not a legion of advertisers. With Google I can't help thinking about every keypress being logged to optimize sales pitches at me. I just don't feel that with Kagi, because I'm paying them.
Sure, they might be logging every keypress (I don't actually think they are, but you never can tell) but even if they were, I could be reasonably certain they were doing it to retain my subscription, which probably means making my search better, not selling me other stuff.
It's a priveleged position to be in, and the economic argument isn't watertight, but in the "search as a brain extension" space it still _feels_ premium, because it creates trust. And that frees up brain space for other things - like where the hell was that article I was looking for?
Of course, no ads or trackers must help - when I look at the Network tab in developer tools the comparison with a google search is stark. ~4 requests vs. google's ~50.
Still, it's a fascinating project, which I will watch closely.
Being able to work outside would be fantastic for my well-being, and I'd accept quite a lot of compromise to get that.
[1] https://en.wikipedia.org/wiki/United_States_antitrust_law#Ty...
I'm open to both views, and most importantly to trade-off one against the other according to other constraints and context. For me, using C++ allows me to do that, because it's (mostly) a superset of C. Acknowledging, of course, that this brings a trade-off of its own, because decisions must continually made (and enforced) about what std/external libraries to use and when.
I'm not an expert, so I won't claim to know who's correct. But the linked video provides lots of numbers, and you didn't, so I lean in favour of that conclusion.
This is why managed languages like Lisps are rarely (if ever) used for the DSP in audio applications. I am an audio programmer who loves all things lispy, so believe me, I wish this weren't the case.
How this relates to 10x or not I don't know - I'm not sure the discussion is a productive one without further context.
It might be that for some tasks, Elm really does provide a huge benefit in productivity. In that case, it's probably fair to call a developer that selects and uses the tool correctly a 10x developer - provided they are able to evolve the culture of their company so that others can take advantage of it.
For other tasks, or in other contexts, Elm might be a hinderance. If it's lacking an indispensable library, or if the company culture is not ready to accept it as a core language, it won't help anyone to rewrite in Elm.
As always, one of the key things that makes a good (even 10x) developer is the ability to select the right tool, and to wield it gracefully.
1. There isn't plenty of money
2. It's spent quite effectively
[1] https://www.ons.gov.uk/peoplepopulationandcommunity/healthan...
[2] https://www.kingsfund.org.uk/publications/articles/big-elect...