Yes. I have one. Mine was ordered in Feb 2019 for shipping in August 2019. Come February 2020 it finally came in.
Biggest favorite is that I love they keyboard. I run the LineageOS 17.1 simply because I've been too lazy to flash LineageOS 18 unofficial. tdm the primary developer did a great job making the keyboard act well, and other developers made it behave via an app in Stock Android.
Second biggest favorite is that it has the trifecta of features I require from any phone: unlockable bootloader, microsd card, headphone jack. I prefer a removable battery but alas those are as thin as hen's teeth.
My biggest beef with this phone is that it has spotty voice reception. I have to stand in a particular spot in my house to not have my UDP packets drop off. Data reception is fine and when I do calls over signal or duo (wifi) it works a treat.
My second biggest beef would be the lack of snap-on case options like the old Nokias. I'm trying to figure out if someone does a 3d printed case or what, but with this curved screen, I'm nervous that each day could be this phone's last with just one fall.
I was positive I could not draw objects from life. But some of the tricks in that book showed that even I really could (in the right frame of mind) trace/render/copy/draw from life. Now I just needed practice.
Get this book, go through it, then look into drawabox if you are looking to draw from life.
For constructivist illustrations or styles like manga, I'm still learning.
Followed by "rewrite UWP for Reunion, sorry about the left turn with Windows 8, and don't use that C++ Builder like tooling any longer, IDL without VS support rulez".
> because the tool forces them to do the job properly
I'd argue the same restrictions on "setting handwave to maximum" and "XHTML doc has one missing brace, no web page at all now" are two extremes that have their parallels in the 'dynamic vs static typing', 'immutable pure vs mutable impure functions', 'XML vs JSON (oh wait!)', and 'web app vs native program' arguments that we HN readers love to debate.
The trick is finding the happy medium between both extremes. Training some 'slackers' to "do the job properly" and convincing some 'purists' to be more pragmatic to the limitations of the world around them.
After all, we need something to occupy us during this Eternal September.
It's a trap. You only need to find the happy medium if you accept the constraints that generate the trade-off in the first place.
And in at least three of the four antagonisms you list, it comes down to the DX of the tooling. Static typing isn't so much of a pain if your type errors are helpful and descriptive. The missing brace in the XHTML doc is easily found when using proper and easy to use XML linters. And I don't see why writing native apps shouldn't be as simple as writing web apps. At least there are attempts that seem to get some mileage out of the idea (e.g. Revery, Flutter).
The trick is to make the toolset more approachable.
The Win32 counterpart to the UWP-centric design guidelines are here[1], titled "The Windows Interface Guidelines — A Guide for Designing Software".
Much more practical to designing native desktop software, whether you are using Win32/WinForms/QT or otherwise for your rendering engine. IMHO this is what makes a program 'intuitive' and 'natural' to many working adults ages 25+, which is often the target demographic, even if the program will not look 'modern' or have high "design award" value.
EDIT: and is even available in dead tree form: [2]
> Can a Birdy client with internet access serve as a gateway to other Birdy clients without internet access?
That's so far unclear to me as well. I will say, if they can crib some code or at least hints on how that might be done (provided they even want to support that feature), there was an old app out there called EnsiChat[1] that IIRC had internet relays running on servers, but was P2P-first.
So: if Alice could see Bob directly via P2P, they could chat. Or, if Alice could see Bob indirectly, they could still chat.
No idea if it supported meshing P2P connections to get Alice's message to Bob via Alice -> internet relay -> Frank -> Dmitry -> Bob
> “I was thrilled with those results,” says Neuman. “Even though we were hamstrung by the lower clock speed, we made up for it by just being more efficient.”
So besides the lampoon-ability of this article as inventing new words for old concepts (hardware acceleration) which I am not qualified to lob (and therefore only hint at ;) ), how much more software efficiency is out there to 'mine' out of standard CPU/RAM/Storage Von Neumann-style computing devices?
Some people claim that moving things from Electron to native would be a huge speedup, and I don't disagree with that, somehow a Windows 98 box provided 95%+ of today's computing experience (I can't speak for older things like Amigas, Apple ][s/Lisas/etc) at like 1% of the computing power.
But what do I know, maybe all the software efficiency in the world has been wrung out and there is no more low-hanging fruit? And/or that is the case for robotics but not for general computing.
Correct. That's why I sought it out and may or may not have baffled / actively disregarded the Best Buy sales guy who wanted to sell some other routing hardware that was 'newer'.
This message delivered to you with its help, and I am definitely going to be looking for its descendant when the time comes to replace this one....IF it is still open-source-ready.
Biggest favorite is that I love they keyboard. I run the LineageOS 17.1 simply because I've been too lazy to flash LineageOS 18 unofficial. tdm the primary developer did a great job making the keyboard act well, and other developers made it behave via an app in Stock Android.
Second biggest favorite is that it has the trifecta of features I require from any phone: unlockable bootloader, microsd card, headphone jack. I prefer a removable battery but alas those are as thin as hen's teeth.
My biggest beef with this phone is that it has spotty voice reception. I have to stand in a particular spot in my house to not have my UDP packets drop off. Data reception is fine and when I do calls over signal or duo (wifi) it works a treat.
My second biggest beef would be the lack of snap-on case options like the old Nokias. I'm trying to figure out if someone does a 3d printed case or what, but with this curved screen, I'm nervous that each day could be this phone's last with just one fall.