The $15 adapter is most likely of similar quality as the DAC and other audio components in the phone, so I don’t see the point. (Also, most people I know with $1000 headphones use an external audiophile-grade DAC anyway.)
They might, but why should they have to? That tiny ESS DAC in LG phones is measurably better than a lot of external "audiophile-grade" DACs. It doesn't compromise the design or the water resistance of the phone either and probably doesn't add much cost relative to other components.
This is basically an arrogant move that can't really be technically justified.
E.g. By arguing that better external options exist - better external cameras also exist, should we get rid of the camera too?
The Dutch and Danish approach to cycling is just from a different world. Even cities that I consider decent for cycling, like Berlin, pale in comparison to any larger Dutch or Danish city. And once you introduce cycling into commuting systems at that scale, yes, it enables you to design those systems in new ways.
It also requires a shift in focus away from prioritising cars to prioritising pedestrians and cyclists. In the Netherlands, you can be sure that every town planner owns a bicycle and commutes on it frequently. I live in Ireland. I've met regional town planners here. None of them own a bicycle.
Traffic planners here call the traffic state when pedestrians are crossing the road "dead time".
One of these days when I've got nothing better to I'm going to put together a little photo essay of the bike racks I know of in my city that don't even work. Using a conventional U-lock you can't even lock your bike to them.
Some are too fat for a U-lock to fit around. Some are placed so close to a wall that you can't fit your bike in. Others have these vertical slats that you can stick your front tire in between, but you can't lock your frame to anything secure.
The people who designed and implemented these things must have never used a bicycle for practical purposes. The stupidity is mind boggling. It's not a difficult thing to get right.
> Others have these vertical slats that you can stick your front tire in between, but you can't lock your frame to anything secure.
This is probably copied from Copenhagen, where it's by far the most common type of rack.
Bicycles simply aren't locked to anything secure, unless you bring your own cable lock. That's something you might do with a flashy, new racing bike, or any other very new bike left outside e.g. into the late evening or night, although insurance should cover theft anyway.
If you have a kickstand, you don't even need to use the rack.
> Others have these vertical slats that you can stick your front tire in between, but you can't lock your frame to anything secure.
If this is what I'm picturing, you can often just lift the bike over so the rear of the front tire is in the vertical slats, instead of the front of the front tire. Then the frame is close to the rack, and you can lock your frame to the rack.
Stick your rear tyre into those slats, usually this allows locking frame and rear wheel. Wirelock on the frontwheel if wanted.
Also, the foldable locks are much more practical than the U-style locks.
I'm pretty loyal to the U-lock, it's the fastest. When I was a messenger, locking and unlocking 50 times a day, we all used them. It takes 5 seconds when you got your system down.
Its really sad, not too long ago (60's) most of us didn't have cars and cycled.
Heres a great example of how badly we've fucked ourselves up in the last few decades.
https://www.flickr.com/groups/dublincyclelanes/
That's a good point. When I look at some stuff that's done for cyclists here in California I also have my doubts if any of the planners ever have used a bicycle.
I love Jupyter Notebook for experimenting and rapid creation of reports, but dislike it for not being able to use my editor and for intermingling inputs and outputs in a single file. So I'm working on an alternative frontend to Jupyter kernels, which is heavily inspired by KnitR: https://github.com/azag0/knitj It is still being developed, but it's functional and I use it every day.
This looks incredible! Does your project already support other language kernels than the Python kernel?
I use R for 90% of my work, but most of it has been happening in Jupyter notebooks (which I'm not a huge fan of, despite practically living in them for the past 4 years of my life).
I have not tested it with anything else than the Python kernel, but it uses Jupyter Client to communicate with the kernel, which is kernel agnostic. So you should be able to do just “knitj -k <kernel name> ...”.
True. Actually that's what I meant by "intermingling inputs and outputs". KnitJ still shows both code and its output in the rendered HTML, but unlike in Jupyter Notebook, the code is stored and edited separately in a single source file.
That's my biggest frustration by far with trying to use Jupyter for anything Serious Business. Will definitely check out your project; thanks for sharing.
We must use the phone in very different ways. I spend hours a day in a terminal, so I live by a file system on a computer. Yet I've never felt the need for a filesystem on an iPhone.
For one, as a package developer, publishing a source distribution of a package on PyPI is almost trivial. Publishing on Anaconda Cloud requires you to build the binary packages on all the OS's that you want to support (and for all Python versions you want to support) which most people delegate to some CI. So there is a whole new level of complexity involved.
For pure-python library projects, I found Poetry the best option these days (haven't tried Hatch). But it is still heavily under development, so it's not necessarily a black-box solution.
The biggest pain point of Pipenv for me is that it cannot as yet selectively update a single dependency without updating the whole environment.
