Subtractive synthesis has a particular meaning in common use whether it’s right or wrong.
983 karma · joined November 20, 2010
[ my public key: https://keybase.io/timchild; my proof: https://keybase.io/timchild/sigs/1G_1ylOlBiwERzFp9FLyK33erxfO4TXl1iFr4HCozOQ ]
Subtractive synthesis has a particular meaning in common use whether it’s right or wrong.
Today I have no idea about SQL server but if the support is as good today as it was back then it can be worth it.
Edit: add planting trees
10gbase-t ethernet is harder to pick, a lot of those cards run incredibly hot particularly the ones that expect server style cooling. Heard bad things about all of them.
Also heard that Windows has a hard time reaching 10G anyway.
I started the first way in the early 80s and did the second and have a life long love of synths ( I don't even know how many I have now but probably around 30-40 hardware synths, samplers and drum machines).
Not sure I would class it as jungle though.
Dual power supplies is a nice to have.
We built up a partner network worldwide, so we had to find relevant partners who would help serve our potential customers in the relevant way that already had those customers. They are easyish to find and approach because they are trying to achieve a similar goal, although sometimes more generically if they are integrators (selling software, hardware and services). Sometimes they sell a competitive product so our USP had to be tight - such as not requiring a year of services to start up but maybe an hour or two.
Others were complimentary tech partners and very kindly helped spread the word, and got a foot in the door for direct engagement.
If each partner has 10 good customers, then thats 10 partners you have to engage with. We were more often than not involved with the relationship with the customer, and got direct knowledge of the customer problem, how well we fit solving the problem, identify UX issues, sales issues, support issues etc..
It’s been a successful way to start.
OmniOS I basically run as an appliance and has been trouble free since the start.
I prefer BSD because to me it’s more logical, it rarely changes, the documentation is first class and it’s very stable (yes more so than Linux). Plus I like its networking stack and PF
I prefer Linux when I need to run something popular and want a community.
I prefer Solaris clones for storage.
I prefer macOS for doing music, graphics and every day work and for laptops.
It’s no problem jumping between them. BSD is my favorite though.
Certainly for some use cases speed and low CPU matter but not all.
Fibre is cheap and you can get it cut to whatever lengths, and it’s somewhat future proofed.
TP-Link and omeda is probably an alternative, but after spending time trying to figure out what they offer and what their alternatives are for my needs I just give up with their confusing model numbers and half hearted explainations.
The problem I really have with Ubiquiti is when I look at their offerings and what I need I am immediately put into their Enterprise offerings and I am running 48 ports.
And I disagree that AWS is less complex. Managing services across AWS is complex, K8s is as well but I would rather manage K8S on bare instances.
And thats fine, you have features on top that can be worth paying for certain customers and expenses of your own to pay. Those of us that have been around in this business for 30 years know how expensive PAAS and IAAS can be and how easy it is to roll your own solutions and when not to do that.