He has a show about consumer rights ("Joe Lycett's Got Your Back", which I suppose will be "Hugo Boss's Got Your Back" next season) so it's in his wheelhouse.
178 karma · joined October 11, 2015
He has a show about consumer rights ("Joe Lycett's Got Your Back", which I suppose will be "Hugo Boss's Got Your Back" next season) so it's in his wheelhouse.
Cheap and easy: buy a 2 TB drive and keep it at home. If some disaster affects your home -- flood, fire, burglary -- it can take out your data and its backup.
Cheap and reliable: buy a 2 TB hard drive and keep it somewhere else. Keeping the backup up-to-date means regularly bringing the drove home, updating it, and putting it back.
Easy and reliable: pay for a service like Backblaze that automatically backs up all your files to a remote server.
There are other benefits to services like B2 especially, namely being able to access your backed-up files from any device or location, or being able to link people to your files on a high-speed server.
https://ryanplant.net/love.wav
Its only mistake was missing the "you" in "you want to be."
Codec2 remains fairly clear down to human ears down to 2.4 Kbit/sec but I had no luck getting it recognised, even with much simpler and clearer samples.
This individual anecdote tells you nothing about the state of the art, but I wanted to note it anyway because I was astonished at how well 6 Kbit/sec is handled.
It's interesting because it's no longer just filling a gap in textual communication, but using textual communication to express a thought or joke that you can't really express with the same interpretation in any other conversational medium. Responding to "and Dave will be there" with blank-stare + man-fleeing expresses something you could only really express otherwise by drawing a comic strip on the spot and handing it to someone.
The co-inventor of Unix, Ken Thompson, and the Unix team engineer and author of The Unix Programming Environment, Rob Pike, are both big advocates of static linking. They designed Go and made a big point of emphasising static linking. Pike: "Shared libraries are obviously a good idea until you've actually used them. Whether it's obvious or not that they're a bad idea is mostly a matter of how close you are to trying to get them to work." He wrote the first windowing system for Unix, which surely qualifies him as a greybeard.
"... In that Empire, the Art of Cartography attained such Perfection that the map of a single Province occupied the entirety of a City, and the map of the Empire, the entirety of a Province. In time, those Unconscionable Maps no longer satisfied, and the Cartographers Guilds struck a Map of the Empire whose size was that of the Empire, and which coincided point for point with it. The following Generations, who were not so fond of the Study of Cartography as their Forebears had been, saw that that vast map was Useless, and not without some Pitilessness was it that they delivered it up to the Inclemencies of Sun and Winters. In the Deserts of the West, still today, there are Tattered Ruins of that Map, inhabited by Animals and Beggars; in all the Land there is no other Relic of the Disciplines of Geography."
I think Elm makes a better introduction to FP concepts because there's much less you have to absorb before you reach the point where you can start practicing by doing useful work. Obviously part of that is the fact that Elm removes or hides certain things Haskell has, but an even bigger reason is that you can just say "...and then 'main' returns the HTML element or Html.program that actually gets displayed" and not have to go down the road of IO actions, functors, etc. You can stop at that point and start making working useful applications while getting comfortable with immutability, purity, the type system, and control flow and iteration under those constraints.
Learning Haskell first, you don't have that opportunity to stop and start practicing. You need to move on an understand at least IO actions, functors, applicatives, typeclasses, and other higher-level concepts before you can construct even a simple practice project. Dreaming up a coherent program structure/flow in this weird new immutable and pure world seems hard enough to a beginner without also having to understand how applicative functors fit into the equation. Having that opportunity to stop and stretch your legs by actually doing a project is a major help to a lot of people, that's what makes all the difference. And then 95% of what you've learned transfers directly into Haskell.