This gets even worse if your software is an integration layer between two services you do not control.
2,750 karma · joined February 2, 2011
This gets even worse if your software is an integration layer between two services you do not control.
Also, "commandeering" an IP of a small hosting might be easier than you think. It depends entirely on how they recycle addresses.
The functionality of 99% of all websites I see these days can be replicated with simple DB calls, string concatenation and a handful of straightforward progressive enhancement libraries on the client side. Some developers simply choose complexity.
The fundamentally complex aspects of web development aren't solved by the stuff people are fatigued by anyway.
Easy to use documentation. "Batteries included" standard library that specifically caters to web dev. Shared-nothing architecture. No separate compilation step. Easy deployment via source code. Ability to use PHP files as configs and templates. In more recent times, autoloaders and APC cache.
As far the language goes, I also like their approach to dynamic invocations via __call. Very simple and powerful.
"The conditioning was applied by feeding the speaker ID to the model in the form of a one-hot vector. The dataset consisted of 44 hours of data from 109 different speakers."
Am I missing something?
The problem with unexplainable AI isn't just the lack of explanations. It's the fact that the entire model is a black box, so you cannot somehow tweak a single part of it without retraining.
You're assuming that learning the framework will make understanding actual workload code completely effortless. In non-trivial applications this is never the case. You still have to understand... stuff like this, for example:
http://mikehadlow.blogspot.com/2010/04/custom-aspnet-mvc-mod...
When someone writes code from scratch the quality of the code depends on their ability. When someone uses a framework the quality of the code depends on their ability, the quality of the framework and fitness of the framework for a particular problem.
If the developer is not very experienced but sufficiently disciplined, and the framework is well-designed and fits the chosen task well, than yes, you end up with better code. If any of those conditions fail, the code is usually just as bad or worse than vanilla.
Unless they spend most of their code fighting the framework to accomplish their actual task. Which happens rather often.
Not to mention that learning a new framework is not fundamentally different from learning some person's approach to doing things. Whether or not it's easy depends on the quality of code and documentation. Given equal size of the code that does the job, reasonably written framework-free code is probably going to be easier to understand, because it doesn't have external dependencies.
I never understood why after years of dealing with dozens of competing and rather poorly constructed web frameworks in Java, PHP and now JavaScript people still believe that those things have some kind of inherent value. Remember Struts, anyone? PHP Nuke? WebForms? Would you rather maintain something that used either of those over something that was written in vanilla Java/PHP/C#?
http://www.amzi.com/AdventureInProlog/advtop.php
There was a great PDF that explained how unification and substitution of symbols worked in a concise and readable fashion, but I can't find it right now. Hm, maybe this one:
http://www.cs.ubbcluj.ro/~gabis/plf/Doc/SWI-Prolog/AnIntrodu...
Which leads me to another idea. If websites supported separate email accounts for messaging and authentiaction/resets and kept the second account name hidden from general public it would (somewhat) help in a lot of cases.
Also, I would be much more likely to do 2FA on more accounts if websites gave me the option to use printed lists of tokens instead of my phone number.
On most of my accounts the probability * cost of getting hacked is much smaller than the probability * cost of loosing access.
When an expert system beats some human in a complex real-life problem the comments are about how it is narrow, boring, not sufficiently tested and ultimately doesn't matter.
When a neural network (with the help of MCTS and an entire data-center full of servers) beats some human in a board game the comments here hype it through the roof and jump to conclusions about the coming dawn AGI.