I’m working on a macos virtual microphone app that lets you take a real microphone input and apply audio processing effects on it like raising the gain, reverb, etc, then using that as your microphone in other apps, like for video calls
Comes from my own desire for something like that. Right now I’m using a hacked together solution using blackhole and a random vst. It was a pain to set up initially, trying to make it easier for other people.
I know there’s loopback but it costs too much for what i need and has a lot of extra features i don’t care about, plus i’d still need to bring my own vst to it
conditioned in buddhism refers to the fact that anything that exists, originates from something else.
so any one thing you examine will be “conditioned” on the previous things that cause it to appear
cause and effect basically
this has some philosophical implications, since all you are as a person is a bundle of emotions, mental patterns, etc that are ultimately conditioned
this leads to the buddhist view of no self, where there isn’t something that makes you “you”. just a bunch of responses to stimuli. some of those responses are thoughts of a self.
the diamond sutra's point aiui is that what we call a self isnt a self in that a true self does not exist independently (from the causes, such as its essential nature, its foundation, and its environment)
i might even say a self has an essential nature defined by an origin which is composed of relationships. you can find all examples in nature if you look a little.
Very similar API to React but the reactivity system is nicer. There's no hooks rules like not putting them in if statements or inside other hooks.
Very cool and I think this is the future. It also helps that the performance is crazy good and it doesn't re-render everything all of the time like React.
I've used both extensively and what makes me lean towards Vue on new projects is the reactivity system. It seems that with React you always have to wrestle with it to not do too many re-renders, but Vue is more likely to update only the parts of the dom that need updating out of the box.
With composition API and Vue 3 bringing typescript support and hooks to me it's a no brainer to choose Vue.
One other thing is that I've seen people who are normally doing only backend pick up Vue in a day or 2, but React takes longer to grok. You're probably likely to find more people who have already learned React than Vue though, due to its popularity.
React also has a bigger community but I haven't felt that I was lacking when looking for Vue libraries.
I prefer fixing performance bottlenecks later over having any doubt about the correctness of my view or debugging why this one property only sometimes becomes reactive. But I can see how others would feel differently.
In my experience those optimisations tend to never happen unless they make the app unusable, leading to tons of WebApps working like crap.Probably you work on a company that budgets a lot to eorgormsnce optimisation, etc or you just care a lot about it, bit in my experience most companies and most developers don't have the time or motivation for it. I'm tired of sluggish crap.
I agree. The reactivity system is definitely less verbose in Vue compare to React. And when you start working with things like Redux it gets very layered and complex very fast.
Don't have any references for you but maybe I can give some perspective on it.
The things that still trip me up with CSS after a few years of full time frontend work are the following:
1. Dynamic 2D stuff
CSS kinda sucks for most 2D dynamic layouts. Especially when you have heights that are dependent on widths or the other way around. With CSS grid and the upcoming aspect-ratio things are better but I still run into some limitations in especially dynamic web apps / data visualizations I make and I usually resort to calculating the widths/heights in javascript so I can have full control.
2. Going into the third dimension
I'm not a big fan of the z-index / position absolute / relative stuff going on in css.
I'm not sure what a better way would look like, but every so often I run into weird issues where a parent somewhere is relative and it messes up an element I'm trying to absolutely position.
Most things can be worked around but it's still annoying and usually take longer than what I feel they should.
Apart from these, most of the quirks of CSS are very mild and can be worked around easily. I actually find writing CSS quite enjoyable day to day.
Made this to scratch my own itch. I had a giant web project on which purgecss would take 10 minutes to remove all unused css. I thought rewriting the main functionality in a multi-threaded native extension would make it much faster.
C felt too cumbersome and I personally don't like C++, so that's where napi-nim came in, since I wanted to use Nim.
The native purge-css extension is still in early stages, but napi-nim is already quite usable.
For the IDE part, you can look into the Language Server Protocol spec and write an implementation for your language. Would then work with most editors like VS code, vim, etc. out of the box and remove the leg-work of making the rest of the editor.
Not sure if it counts, but I consider the blog an ongoing project