Twitter | Pretraživanje | |
Nathanael Anderson
DevOps, SecOps, Author, Speaker, Father, and general nice guy.
1.164
Tweetovi
243
Pratim
1.010
Osobe koje vas prate
Tweetovi
Nathanael Anderson 31. sij
Odgovor korisniku/ci @LinguaBrowse @cyanapps i 4 ostali
But the better question is what Native API would be better supported by Promises than it is now? Remember creating a promise has considerably more overhead than directly returning the value if you can. Really curious where you would use something like this in practical use.
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 31. sij
Odgovor korisniku/ci @LinguaBrowse @cyanapps i 4 ostali
Well, technically I can't think of a reason this couldn't be supported. Moving to the common runtime is a major step forward. Having two runtimes created a lot of other insidious bugs (code worked great on one platform, but had weird side effects on the other).
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 30. sij
Odgovor korisniku/ci @Matt23Morris
As someone who has played since Warcraft I; very disappointed in how this was handled. Is their a way to get the original classic client to re-install. It appears the classic client now forces an update to reforged which is of course very broken compared to the classic client.
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 29. sij
And this is why I created -- so very true on every part of open source development..
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 24. sij
you can do way better! Seriously, you didn't bother to ship the fix for the extremely annoying ghost window () in the new release of ? Very disappointed in my choice of editors right now, 3+ months dealing with this idiotic bug...
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 24. sij
Odgovor korisniku/ci @LinguaBrowse
- No easy way to suspend/resume and save your state. - Currently a different widget tree for iOS vs Android to make app look the like the OS - Flutter Widgets have some weird inconsistencies to standard platform widgets -- In some cases kinda like Cordova vs Native look/feel.
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 24. sij
Odgovor korisniku/ci @LinguaBrowse
You missed: 😀 - Camera using app; a ticking time bomb for your app. - Inability to use ANY API synchronous callbacks in the dart side. (major issue imho) - Major keyboard issue on Samsung devices in non-english languages. - No easy access to native widgets
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 22. sij
This should be Awesome! Nathan is an awesome presenter -- Mobile UX using , at .
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 22. sij
Odgovor korisniku/ci @DougWeinfield @therealfitz i 2 ostali
What happens when your favorite music service adjusts its API a just little? None of your speakers, _including_ your new ones gets any future updates to allow them to play from that API. Hence the argument is that they will all be bricked until you disable the old devices.
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 17. sij
Makes it (imho) a lot easier to not worry about it in the future, still have "tns5" still installed that way. I nuked my tns2 a couple months ago, after I was finally able to move my last client project off of it.. 🥳
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 17. sij
Yeah, that is why I do a npm i -g nativescript@5.4.2 then manually rename it to ns54 so that I don't download it ever again. :-) This way I have the latest of the 5.x and the stock `nativescript` is the current version 6. Did the same thing with NS 2 also. :)
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 15. sij
Odgovor korisniku/ci @LinguaBrowse @emiltabakov i 3 ostali
I can tell you, v8 is a much better engine than JSC for NativeScript. Not only does it have more es6+ support, it eliminates a whole class of bugs that can occur in NS apps because of differences in the runtime. From a low level perspective, this is HUGE step forward for NS.
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 15. sij
This is awesome news, getting both runtimes on the same engine will eliminate a whole class of weird differences between JSC and V8 in applications.
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 14. sij
Odgovor korisniku/ci @GI_Fucken_Jack @jrssnet @arstechnica
If you add the additional features like snapshots, compression, and even the new file system level encryption -- I can't think of another FS I'm willing to trust my data with. I personally use it on my primary development machine, not just my servers.
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 14. sij
Odgovor korisniku/ci @GI_Fucken_Jack @jrssnet @arstechnica
I would disagree; been doing Linux for many years. Played with lots of file systems over that time. I had the same type of hd drive failure happen to ext4, btrfs and zfs. ZFS no files had _any_ corruption, btrfs, ext4 had to use a backup. I know what FS I trust on Linux...
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 14. sij
Odgovor korisniku/ci @alasdairrr
Switched to zfs as part of the recovery. Had the same thing happen, and even though a drive was failing in the same way; ZFS kept chugging along fixing things until I could get a replacement drive. Replacing the drive; not a issue. ZFS = Peace of mind. 😃
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 14. sij
Odgovor korisniku/ci @alasdairrr
Years ago; I decided to try BTRFS; it was supposedly ready for Raid5/6 type usage, kept it up to date. Then had a drive go out "paritally" (lots of read errors). Corrupted lots of files; had to use a backup to recover... 1/2
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 10. sij
Wow what a picture , yeah that is basically all the mainstream media today. It is crazy how they twist facts and propose so much fiction...
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 10. sij
This is a fairly good article about comparing how to implement native calls with (>289 lines for Android & iOS) vs (32 lines total) for something extremely simple. Implementing NATIVE calls in is much easier because it is designed for it.
Reply Retweet Označi sa "sviđa mi se"
Nathanael Anderson 6. sij
Odgovor korisniku/ci @DEGoodmanWilson
You see in EVERY open source license the ability for EVERYONE to use said software, that is the ethos! I totally disagree with what INS is doing, but this is just as wrong -- 2 wrongs won't make it right, it will create addition negative side effects for everyone later.
Reply Retweet Označi sa "sviđa mi se"