Poor Rob Pike. He always tries to make things simple, and over they time entropy always does its thing. You can hear his frustration in his cited comment.
Rewording your comment (and not commenting on its veracity), it sounds like you're saying that women can differentiate between what their consciousness and what their reproductive glands want better than men. That's a pretty common stereotype about men...
Depending on the hack, I’ll be using Haskell or C. Why mess with the things in between? (What’s up with everyone nowadays using a misbegotten child of the browser wars as their main language?)
What is it with so many Haskell folks being so full of themselves?
In short, with the iPhone X Apple took a platform with two primary means of interacting with the apps — a touchscreen and a home button — removed one of them, and created a better, more integrated, more organic experience. [...] Android handset makers seem willing to copy everything and anything from Apple they can get away with...
Fast scrolling of prerendered layers is what I mean with throughput. You can move layers around quickly as long as their contents don't need rerendering.
One thing the article doesn't mention is that modern devices push two orders of magnitude more pixels with one order of magnitude more color bits per pixel. That requires much higher throughput, which causes much of the added latency on the display end.
> The nice things we want to do in native code are complicated to implement in C because cross-platform C is hard. The standard library is inadequate compared to modern languages. While modern versions of C++ are nice, we still support Python 2.7 and thus need to build with MSVC 2008 on Windows. It doesn't have any of the nice features that modern versions of C++ have. Things like introducing a thread pool in our current C code would be hard. But with Rust, that support is in the standard library and "just works." Having Rust's standard library is a pretty compelling advantage over C/C++ for any project, not just Mercurial.
Sounds like the main reason for rust is that Python has a weird dep on a fixed MSVC version.
Great pr, but Quantum sounds like they finally ported some of chrome 1's tech over. It's great that they're multiprocess now, but it seems more like they've caught up after 9 years, not like they're ahead much. And the UI is still off on macOS.
Chrome used to do lanczos filtering, but moved to bilinear because it needs less energy and looks good enough, especially in high-dpi. Seems like an ok engineering decision.
You're describing the equity situation at startups. Big tech has fairly stable stock prices, so stock performance means the difference between taking home 400k or 600k total tops. 400k us still more than 300k. On the flip side, this also means no million dollar payday from regular salary+equity.
What a mess. My condolences to the Apple engineers who had to implement this. The notch is probably something that marketing thinks is really important for branding reasons, but I'd guess most engineers dislike it. Yet some of them had to add all this complexity to their codebase.
I watch all my video over Chromecast. Making the TV just a screen controlled by my phone is a model that works really well for me. Alas, I've never watched any Amazon video because of that. You'd think Amazon would be more interested in really hooking me on prime instead of pushing their fire products.
Either this guy was phenomenally stupid, or he's angling to become some kind of fringe reporter "personality". After this petition, Kickstarter for starting an online publication about "real diversity", culminating in him accepting a writer's position at some existing fringe blog.