891 karma · joined February 6, 2011
$ mpv --vo tct https://www.youtube.com/watch\?v\=PA4InNa0NSQ
[1]: https://mpv.io/manual/master/#video-output-drivers-tct* Saving the project resets the undo history. A someone who frequently saves, this is super frustrating.
* No normal zoom controls. You have to use the "minimap" at the top.
* Only a single project can be open at once, which makes copying from old projects tedious unless you shuffle files around into your current project.
* Tracks can only be grouped one level deep, i.e., no subgrouping. Most DAWs give you arbitrary grouping depths.
* No way to overlay multiple tracks in the piano roll. I end up starting in one group and extracting to individual buses afterward. This doesn't work well the other way around.
My biggest wish for the next version is project versioning. It's an absolute nightmare managing so many save "checkpoints", especially, as I mentioned, you can only have a single project open at once.
[1]: http://wccftech.com/blow-checkerboard-rendering-ps4pro-isnt-... [2]: https://en.wikipedia.org/wiki/Checkerboard_rendering
The downside of this and the Trezor is that you need a cable to connect it to a device.
[target.arm-linux-androideabi]
ar = "arm-linux-androideabi-ar"
linker = "arm-linux-androideabi-gcc"That seems to be a mistake in the article. $52 billion market cap is of all currently tracked cryptocurrencies, not just bitcoin.[1] Bitcoin is ~$28.7 billion right now.[2]
For the tv comparison, choosing the first 55" 4K tv on Samsung's site: "Typical Power Consumption: 65, Maximum Power Consumption: 170".[2]
[1]: https://www.asus.com/us/Commercial-Monitors/PA328Q/specifica...
[2]: http://www.samsung.com/us/televisions-home-theater/tvs/4k-uh...
* otree: https://i.imgur.com/AnqaTLE.png
* mindiff: https://i.imgur.com/2UMzyub.png
I've always found it funny that DefinitelyTyped's tag line is "The repository for high quality TypeScript type definitions", but it's an absolutely disastrous system. If it's not a well-used library, definitions there will be woefully out of date. Versioning is a huge issue with it, so it's hard to figure out what definitions actually match the version library you're using. I can only admit that it's an effort that's better than nothing.
The few projects I added types to, the original project owners gladly accepted them into their main repos, which is great since types will "just work" without fuddling with @types packages.
http://hothardware.com/news/amds-ryzen-7-1700x-delivers-i7-6...
[1]: https://www.archlinux.org/news/phasing-out-i686-support/
Cassettes weren't _that_ bad. The problem is that there were essentially different grades of tapes and players that supported different noise reduction techniques, and people tend to remember the ones played back with low end gear.
Here's a great video on the subject: https://www.youtube.com/watch?v=jVoSQP2yUYA
[1]: https://www.ruby-lang.org/en/news/2013/12/21/ruby-version-po...
[1]: https://github.com/rails/webpacker [2]: https://github.com/rails/rails/pull/26836#issuecomment-26424...
Maybe the go devs see them as traitors for using rust for their core components. :P They were having memory consumption issues with go, so I'm not sure that would be the best thing to add to a list of success stories.
[1]: https://blogs.dropbox.com/tech/2016/06/lossless-compression-... [2]: https://news.ycombinator.com/item?id=11283685