Yep, screen is the easiest. Minicom often gets confused, or at least confuses me with its weird UI. With screen I just run "screen /dev/ttyUSB0 115200".
The biggest bummer of these machines is apples lack of vp9 hardware decoding in macos, it makes 4k youtube unwatchable. For high motion content (mountain biking videos) 4k is the only way to watch even on a tiny laptop screen due to youtube’s horrific compression. Its an absurd limitation considering the hardware has full support for it! I know it sounds insane but I returned mine for a quad core 13” mbp just to brute force software decode playback of these videos.
I wouldn't say it's the only reason. H264/5 are not royalty-free codecs. YouTube is a powerful tool Google can use to push a royalty-free codec, much like Apple used the iPhone to push people off Flash. It's one of few areas I agree with Google being heavy handed.
It's an open source, royalty free codec. I'd much rather use that than one owned and licensed by a private organisation, no matter whether Google develops it or not.
Does anyone know of a similar Safari extension? Battery life remains a concern, and switching from vp9 to x264 is great, but then having to deploy Chrome instead feels like a 1 step forward, 2 steps backwards situation.
I don't see the relation of High Motion Video, ( Sports ) to Video Codec and Resolution. Why cant H.264 not be used? ( Which is the standard used world wide now for All Sporting Events )
For 4k video, H.265/VP9 have better quality at the same file size, or equivalent quality at a smaller file size. Bandwidth usage matters for keeping people on the website and viewing Google's ads, so Google wants to ensure a smooth streaming experience. And since YT compresses so heavily, uploading in 4k increase the quality at lower resolutions (it seems weird but a 4k video uploaded to YT and streamed at 1080p will look better than a 1080p video uploaded to YT and streamed at 1080p).
And as xnyan said, high motion video really destroys video quality on YT, this video really shows how bad it can get: https://youtu.be/r6Rp-uo6HmI
It's a huge topic and I'm not a professional, but tldr Google's implementation of h264 compression is not suitable for high motion video and the changes they would need to make in order to make it suitable are not worth it in view of the trade offs of size and other factors.
Why can't a $1K general purpose computer efficiently decode a royalty-free codec (hint - it may have something to do with the fact that apple has a major stake in a competing for-pay closed codec). I really do like apple, but I see apple as microsoft 2.0 in this.
>Why can't a $1K general purpose computer efficiently decode a royalty-free codec
Well the Codec is Royalty Free but not Patents Free. You only get to use it as long as you don't engage in patent litigations against Google.
And Apple does not have an major stake in H.265 or H.264 or every H.26x codec. It has a very minor stake, in the an Open Codec, not closed. Comparatively Speaking every H.26x Codec is more open than VPx and even the new AV1 Standard [1] . So this is far from WMV or RMVB.
I wonder if Google will support EVC / MPEG-5 as it is Royalty Free.
Every link i’ve seen to this story annoys the hell out of me because they don’t explain HOW the elevator eventually stopped. That’s literally all I want to know.
The best book ever for understanding how Elevators work is a wonderful late 20th century work of fiction called The Intuitionist by Colson Whitehead, which was described by its author as what you would expect to happen if you let a child grow up reading elevator manuals.
There was an elevator hacking talk that went into the buffers at the bottom of the elevator. You may have seen them in elevators that have glass on the outside of the shaft like in malls and hotels. The elevator never rests on those. Those are to take the impact of an elevator that crashes. Inspectors will often test the buffers as well as part of routine maintenance:
The basic theory is that between the car and the wire there is a spring connected to brakes. When the car hangs in the wire this spring is loaded and the brakes disengage, if the wire breaks, the spring returns and brakes engage. All this is mechanical.
What I never understood is how elevators can travel downwards so quickly without such a system engaging. Can they block it somehow or are they never accelerating fast enough down?
Guess again. The cable could break at floor 84, and the elevator car could travel through the next 50 floors, and not slow it’s descent until the 34th floor, at which point, given ten vertical feet per floor, it would still have a total stopping distance of nearly 200 feet, or 2/3 (66%) of a football field.
So, 500 feet of freefall is still substantial. That puts the situation on par with a bungee jump.
Thank you for this it looks promising. Just a couple minor constructive criticism points that are personally keeping me on minihack.
1: I need the ability to swipe back from anywhere on the screen, i’m unable to reach all the way to the left edge most of the time.
2: The ability to up the density of posts/comments on the page. I really like seeing as much content as possible without a ton of dead space and scrolling.
2. That doesn't seem complicated to add! Seeing the feedbacks here really gets me motivated to improve the app, so I'll try to add this in an upcoming version.
You normally get it for free if you're using a UINavigationController, see interactivePopGestureRecognizer.
I've never touched it beyond letting the default one work, but it's probably done using UIScreenEdgePanGestureRecognizer. If there's another gesture being grabbed by the active view (like scrolling) you might need to tell your UIGestureRecognizerDelegate to allow the gestures simultaneously.
EDIT - Oh I see, parent comment doesn't like the system standard of swiping from the edge of the screen. So that'd be a regular pan gesture recognizer, and probably trickier to do at the same time as scroll view.
I'd be hesitant to take that suggestion, since it means you'd never be able to use a "swipe right" gesture on the individual list items, like what you see in Mail for marking a message as read/unread.
Here's another feature suggestion, shamelessly lifted from the Apollo reddit client. Long press on the navigation bar to toggle between light and dark theme.
I'd also point out that your "sliders" icon for the settings tab is rather unconventional on iOS. Users will expect a gear icon to represent settings.
Does anyone know how the virtio network performance is on this release when virtualized under qemu/kvm? I know that pfsense is moving to 10.2 soon and i've been unable to use it virtualized due to its atrocious virtio net performance.
While the linux based firewall alternatives are incredibly fast they just don't have anywhere near the ease of use/feature set of pfsense!
I had that same problem when I was proofing out FreeBSD to replace Linux at $work but found an errata that fixed everything by disabling hardware checksum offloading:
