499 karma · joined April 17, 2012
"I dislike the syntax and semantics expressed in PEP 634. I see the match statement as a DSL contrived to look like Python, and to be used inside of Python, but with very different semantics. When you enter a PEP 634 match statement, the rules of the language change completely, and code that looks like existing Python code does something surprisingly very different. It also adds unprecedented new rules to Python, e.g. you can replace one expression with another in the exact same spot in your code, and if one has dots and the other doesn’t, the semantics of what the statement expresses changes completely. And it changes to yet a third set of semantics if you replace the expression with a single _.
I think the bar for adding new syntax to Python at this point in its life should be set very high. The language is already conceptually pretty large, and every new feature means new concepts one must learn if one is to read an arbitrary blob of someone else’s Python code. The bigger the new syntax, the higher the bar should become, and so the bigger payoff the new syntax has to provide. To me, pattern matching doesn’t seem like it’s anywhere near big enough a win to be worth its enormous new conceptual load."
This while we have elephants in the room such as packaging. Researching best practices to move away from setup.py right now takes you down a rabbit hole of (excellent) blog posts, and yet you still need a setup.py shim to use editable installs, because the new model simply doesn't yet support this fundamental feature.
I can't afford to spend days immersing myself in packaging to the point of writing a PEP, but would help pay someone to do it well. I can see no way to fund packaging efforts directly on the PSF donations page (edit: see comment). It's great to see Pip improving but there is still not even a coherent guide that I can find for packaging using up-to-date best practices. This appears to be because the best practices are currently slightly broken.
[0] https://discuss.python.org/t/gauging-sentiment-on-pattern-ma...
Excellent documentation, but as others have said docs are everything with charting, so expanding that and adding a gallery are probably the best ways to get people onboard. Looking forward to giving this a try.
My only frustrations are a missing default handler for --version, and that I can't use argument names colliding with builtins such as 'input'. All the flexibility of argparse without boilerplate.
[0] https://twitter.com/moranicly/status/908710539500642304
[1] https://leftfootforward.org/2015/05/daily-mails-racial-scare...
"The UK does not undertake mass surveillance".
Make of this what you will.
This is what we're doing. We're working on approaches for performing nucleotide sequence alignment using approximate time series representations of vectorised DNA sequences. There are some really elegant lower bounding similarity search methods for time series which generate no false negative alignments, allowing use of more expensive alignment algorithms later on in the search to prune out the false positives.
We've tested a few transformations including Haar wavelets, DFT and PAA and implemented an indexing structure in C++.
Preprint: https://www.academia.edu/12575290/Alignment_by_numbers_seque... (slightly outdated... Email me for more info)
This strikes me as a reasonable fine. Well done FCC.
[1] http://www.techradar.com/news/phone-and-communications/mobil...
It takes some discipline to write elegant, loosely coupled code that is self-tuning. I work on scientific software, where reproducibility and reusability is (…or at least should be) paramount, and where black boxes are evil. It's hard not to build black boxes when you're writing self-tuning software.
This discussion is very reminiscent of the debate over skeuomorphic user interfaces. As with the transition from physical interfaces to virtual ones, which has drawn interface designers towards the use of skeuomorphic elements to varying extents over the years, we are in another period of technological transition away from normally aspirated internal combustion towards quieter, more efficient means of making motion. To ease the transition for the conservative masses, some degree of skeuomorphism will be needed at first (although I personally think that creating synthetic engine noise is a horrible, horrible idea!).
In response to your edit, the difference between the two companies is that Apple generally backs up the superficial appeal of its products with very good, if not market leading user experience, engineering and manufacturing. The iPhone is relatively expensive (part of the reason I own a Nexus device), but its quality is undeniable.
The cultural values of these two companies couldn't be much more different. While both are extremely image-conscious and fashionable, Apple has nevertheless built its reputation by delivering innovation and quality to its customers. Beats on the other hand has a built a reputation by selling very expensive headphones of highly questionable quality whose value, I would argue, is primarily superficial.