September 25, 2017 Marc Hogan writes:

> Hit-making songwriters and producers reveal the ways they are tailoring tracks to fit a musical landscape dominated by streaming.

> Throughout the history of recorded music, formats have helped shape what we hear. Our ideas about how long a single should be date back to what could fit on a 45 RPM 7" vinyl record. AM radio meant mono recordings, rather than stereo, and producer Phil Spector’s Wall of Sound—with its cavernous echo and massed instruments—was built for it, offering plenty of depth through a single speaker. Video killed the radio star. Ringtones birthed the quick-hit digital chirps of snap music. The requirements for American Top 40 FM radio, in particular, grew so byzantine by the early 2010s, when blaring, mathematically precise hits reigned supreme, that an industrial-strength supply chain of super-producers and songwriters emerged to fulfill them. > > And now, streaming’s promise for listeners is also a gauntlet thrown down for creators. With tens of millions of songs just a few taps away, artists must compete or be skipped. The unprecedented wealth of data that streaming services use to curate their increasingly influential playlists gives the industry real-time feedback on what’s working, but this instant data-fication in turn risks feeding back on itself. While streaming has undoubtedly coincided with a shift in the pop charts away from the caffeinated bravado of several years ago, streaming-era hits appear to be as rigidly defined and formulaic as ever—if not more so.

Read Uncovering How Streaming Is Changing the Sound of Pop

https://github.com/ahrm/sioyek

In the command-line window the command line can be edited just like editing text in any window. It is a special kind of window, because you cannot leave it in a normal way.

There are two ways to open the command-line window:

1. From Command-line mode, use the key specified with the 'cedit' option (default CTRL-F).

2. From Normal mode, use the "q:", "q/" or "q?" command.

• This starts editing an Ex command-line ("q:") or search string ("q/" or "q?"). Note that this is not possible while recording is in progress (the "q" stops recording then).

When the window opens it is filled with the command-line history. The last line contains the command as typed so far. The left column will show a character that indicates the type of command-line being edited

> A new kind of computer architecture that's more elegant than 1s and 0s, being based directly on Mathematics. > > Note: Everything in here is real (IEEE-754), but the target is computer scientists and the troll level is set to ULTRA. > > Source code and stuff: http://tom7.org/nand/

LOL

> @ciscoserrano > > I actually do have some advice for people on this topic. If you want to learn programming here is a very important concept: Every piece of software you've ever used can be broken down into 4 simple ideas. What I call The Four Friends of Programming. > 1. Save data and use it later. (example: variables, memory allocation) > 2. Conditionally execute things. (example: if statement, switch, match, jump) > 3. Repeat yourself. (example: loops, recursion) > 4. Organize the first three things. (example: structs, functions, classes) > > Thats it. Thats every program you've ever used. The next tip, is that every programming language is someone's opinion of HOW you use those four friends. programming languages are made by people who have opinions about how to program. What makes different languages interesting is that you get see/discover new ways of using those 4 simple rules to solve problems. The people that wrote Java believed that all data should be contained in a type. The people that made Lisp believed you only need lists and recursion to compute anything. But in the end its the same four rules wrapped in an opinion of computation. > > So. If you want to learn programming, pick a language, any language. One that you think will make you money or one that you think will enable to build what you love easily. Then MASTER the four friends in that language. When you do that and move on to the next language you can peel away syntax and jargon (because those are a someones opinions of how code should look) and really peer into the big ideas of the person that designed it.

The video itself is pretty good too.