lol, yes, sure. But why don't you sound horrified?
Version control at least is essential for something of any size with any number of people working on it. You must be able to "revert" a set of changes quickly and reliably if the application has any importance at all.
I can't help but feel it is heavily impacted by ambience of the recording as well. The midi is of course a very rigid and literal interpretation of what the model is hearing as pitches over time, but of course it lacks the subtlety of realizing a pitch is sustaining because of an ambient effect, or that the attach is is actually a little bit before the beginning of the pitch, etc.
If it could be enhanced to consider such things, I bet you would get much cleaner, more machine-like midis, which are generally preferable.
Yeah, articulation should be standardized in the midi specification. It's always a custom mapping to control it even when proper articulations are available. "Oh cool, custom mapping?!", you might say. Wrong. It sucks, because it tends to make old old scores utilizing articulation unusable because the mapping was stored in some obscure plugin configurations divided amongst many plugins.
It would be great if articulation messages were standardized, and then you could just expect them to be there, and if they are absent, the soundfont can simply fall back to the closest thing available. That kind of helpful logic is not possible with custom mappings.
I think you are right in many respects. I would not consider myself one of the accused luddites, but in their defense, this ethos isn't baseless.
First and foremost, the luddites you speak of are programmers or sys admins. They have been using terminals and are still using terminals daily, and they see the benefits that those tools have to offer. Namely, they see composable, interoperable programs that abide by the philosophy that programs "should do one thing well" as the bench mark for real progress. I would say I agree with the merits of this perspective. But I still use VSCode in addition to vim, because I'm not a zealot and there are times when I want to edit something in a very flexible way that VS Code better facilitates.
Both ways of doing things have their merits I suppose. It just hurts a bit to see something simple and powerful be wrapped and rewrapped in progressively less helpful proprietary systems and given a JS front end that lacks all of the focus and freedom that charmed us with the systems to begin with.
I think it is perhaps a function of the way we train ourselves to be workers that passively accept tasks to occupy our attention. Much of school and many jobs provide anywhere from a drip to a torrent of regular units of work for us to focus on, and this occupies a huge part of time and training.
In the past, we used to criticize television for its passive, zombifying effect on the viewer. Games are more engaging. In truth, people like being actively engaged, and they are very accustomed to being actively engaged without the cumbersome work of directing their own activity.
Completing complicated tasks is, in a way, relatively easy. Defining tasks, reflecting on priorities, and allocating time to work on them--and importantly, suffering the emotional consequences of real world success or failure--is sometimes less pleasant. Games are maximally engaging and minimally taxing. That is their magic.
The competition for the best schooling so that you can get the best job can indeed yield significant benefits for the winners. The private sector judges prestigious universities to be high-value; those universities use SATs to judge which students are high-value; and students judge universities as high-value based on their perception of what the private sector values.
All of this is apparently a filtration system designed to find the best and brightest candidates. Presumably, as many have mentioned, these are people with high IQ. And indeed, high IQ people are extremely noticeable when you are around them. They are frequently faster, more incisive, and have a knowledge base that is both deep and wide.
...And many of them are unproductive, valueless fuck-ups with poor temperaments for almost any work requiring a social component (i.e. almost all work). They have substance abuse problems. They have personality disorders. They lie. And many of them are also wonderful people.
I'll take a medium-bright, tenacious, responsible worker with a degree from a state school or community college any day of the week over some moneyed primadonna who is too busy trying to display their own cleverness to focus on the task at hand.
All of this judgement is stupid because it discounts character. Medium aptitude coupled with hard work can and does produce excellence. Focus, care, and attention to detail are at least as important as intelligence. The filtration process closes doors for these people.
Lastly, though this only an anecdote, anyone who's worked in the professional world has had the pleasure of running into idiot attorneys from prestigious schools. People who send e-mails full of misspellings, careless factual errors, and incorrect legal assertions beyond their specific scope of legal knowledge. Trust me, these people exist, and it's extremely difficult to explain how they exist if the filtration system is really the meritocracy it claims to be. It is frequently hacked as a vehicle for privilege.
The problem is that our legislators famously do not write or even read the legislation that they vote on. Sometimes it's strategic and intentional that a party will try to hold a vote on some 1000+ page piece of legislation with 24 hour notice. Other times, they simply don't care to read it, so they do not.
Actual lobbyists write actual legislation, in fact. And our politicians vote on them without having read it. It's a really stupid system.
It's easy to say that, but what do you expect the platform to provide? If the platform makes operating your business so trivial that they provide all functionality baked into the product, I would suggest that your business may lack novelty, and therefore it may also lack competitiveness.
"No code" doesn't mean you don't have to implement things yourself. You are simply limited to the platform's baked in abstractions in exchange for "not having to write code".
Your services may eventually not map well to the capabilities of the platform, and it may cause problems. In such cases, the easiest and likely best solution is to offload functionality to a private server running custom code that interacts with the interfaces to the existing platform.
The whole "no code" thing is spun as "empowering entrepreneurs", but there is a philosophy underlying it that implementation details don't matter, and programmers aren't needed. It may be true for some businesses who are in non-technical sectors, but if you are selling digital services themselves "no code" will only take you so far.
Why? This is not a completely novel concept, and a daemon is not a particularly complicated thing. You can use shell scripts to easily "daemonize" small programs. It's both fun and effective to do so.
Eh, I don't find this argument compelling. Insurance companies already have significant influence in the government, and the line from sugar consumption to health care costs has already been established. So if this is the concern, well... guess what... it's already the case.
Also, while there are examples of behavioral engineering taxes (tobacco, etc.), this can't really be applied so easily to a basic food item like sugar, which is in practically everything in varying degrees. People have revolted over taxes on tea, mind you. A coffee tax, sugar tax, etc. is nearly unthinkable.
Furthermore, this type of taxation is not correlated with already existing examples of socialized medical systems, and this concern over pleasure taxes is not typically expressed by opponents to socialized medicine. Rather, the issue I hear expressed is that people who have good insurance already are scared they will wind up with something worse, and will have no other options at that point. This belief seems to be related and magnified by the xenophobic tendencies of the American political right (the more vocal opponents of socialized medicine; though so-called moderate liberals don't really entertain it either). They believe that if we let marginalized groups have equal access to good medical care, it will dilute their own access, creating scarcity and resulting in longer wait times to get treatment. These people also generally fear 'big government', and characterize anything run by the government as inefficient and costly. Therefore, they essentially believe they will pay more in taxes than the cost of their existing insurance; that they will be subsidizing the cost of care for peoples they generally contempt (HIV meds for homosexuals; abortions for women); and will have worse care for themselves. That's pretty much the argument in a nutshell. It's extremely petty and self-serving.
But, it's not so much that their belief is fully incorrect. While it is likely that health care would cost much much less overall for everyone, it could reduce their presently-VIP access to essential medical treatment in some instances. They believe their money entitles them to better access to medical treatment.
In conclusion, the more realistic (and actual) good faith argument is that insurance companies already do lobby the government to prevent any legislation that would pose an existential threat to their industry, which has vast wealth and power. Socializing medicine is good for medicine, and bad for medical insurers. So, they pay politicians who perpetuate the beliefs I described above and resist meaningful regulation and reform of the medical industry.
This is simply a fact. No need to construct unrealistically contrived stories about pleasure taxes. Ask these people in private what they believe. They will certainly tell you!
It's crazy. I started writing why I disagreed based on my visceral reaction to the topic. But as I constructed my arguments, they were not sound. So I suppose I agree? Hm.
The above paragraph is sincere--that did happen. And interestingly, it shows the power of consuming the opposing view point. We all know that the government is currently spewing lies, and it is indeed a disgusting and corrosive thing. I want to silence it, but it's easy enough to contempt it from a distance. Let the truth and the lies be heard so that we as a people will grow wise to it all.
This isn't really vendor lock-in, though. It's simply a technical/design lock-in. Going from unstructured to structured data presents problems, and if you do that, it's rightfully up to you to fix.
It is different from the vendor lock-in that prevents one from migrating from AWS to Google Cloud because all of your code uses their APIs and libraries specifically.
However, the effect is the same, of course. You are locked in! It's not necessarily a bad thing, but this is why you must choose your poison carefully.
That's crazy, IMO. This view supposes that the workers simply extract wealth from the company, rather than exchanging wealth for their time, which also has innate value to the worker.
Per this view, if a worker worked 100% of their time, they would have achieved their optimum goal of extracting the most wealth possible. But nearly all people who have made that trade would tell you they are depressed, feel run down, and probably think about blowing their brains out on a regular basis.
At some point, the plumber wants to go home, too. Now, maybe it's true that they'll take 1 hour to complete a job at a comfortable rate rather than the fastest-possible rate of 45 minutes, and maybe 4 jobs get completed that day instead of 5 as a result. But it is also true that the 4 jobs may be done with a greater attention to detail. Ever have a maintenance worker track filth into your residence with reckless abandon? What is the value of a more rested, present, and thoughtful worker?
You may argue that for a plumber, there is no value added in that. But I would argue that the value is there, even though the business owner can't extract it as revenue. It is there in the quality of the work, the happiness of the worker, and the happiness of the customer. It makes for a better world, and if you value your employees and customers as people, you'll see that interests are aligned.
All of that said, the economy is a thing. If your business is in a highly competitive market, it's easy to wind up with thin margins in a race to the bottom. But if that's the case, is it not the responsibility of the business management/ownership to either find a way to be competitive short of exploiting workers, or otherwise exit the market and pursue another venture?
At the lowest level, workers will be trained for and work the jobs that are available to them, and the jobs available will be dictated as a function of the the local demand for that service or product. If a small, poorly run, exploitative plumbing company can't find the margins to operate because they are competing with better services, they should cease to exist. The demand will remain the same, and their exit from the market place will result in growth for their competitors, and the jobs will be recreated.
If you are a plumber by trade and run your own plumbing company and can't find a way to exist without exploiting your workers, you should exit the market as a business owner and work for another company. Otherwise, your business isn't plumbing, but exploitation itself.
The "confidence" of senior people to push back is greatly enhanced by the fact that they won't be expediently fired for doing so. And even so, plenty of senior positions suffer from this situation as well. I'm living this hell right now.
For scripts requiring any degree of complexity regarding data structures or architecture, for sure, use Python.
But like, you can't just use Python to interact with your system. It will be such a pain in the ass.
Piping and redirection in Bash is a million times more concise and expressive. Working with streams like this is what it excels at. But if you need to to populate some data structure and access data by key... python is better.
Python's import system requires multiple lines. Python's spacing requirements require multiple lines and awkward spacing when typing directly in the shell. Sometimes you are writing a script, and sometimes you just want to do ${action} to ${file}_${i} in the directory.
You owe it to yourself to be proficient in bash if you are working a lot in a unix-like environment.
Version control at least is essential for something of any size with any number of people working on it. You must be able to "revert" a set of changes quickly and reliably if the application has any importance at all.