31–40 of 47 posts
Are these discards from the jet.com acquisition or actual critical path libraries?
Walmart acquired the online retailer, Jet.com in late 2016 which still has their own engineering team (using a lot of F#)
Stuff coming from @WalmartLabs is almost always real stuff that Walmart is using in production (website, apps, etc.)
Why a company the size of Walmart does this cross platform crap is beyond me. Do they not have the resources to actually write real native apps in actual Swift? Why is it desirable to code to the the worst common denominators for devices? Cross platform is just lazy. And React “Native” is inferior to actual native.
It's this assumption that "same experience on all platforms" (aka "branding") is desirable to "native experience on all platforms". Facebook wants facebook to feel like facebook whether you're on an iPhone or an Android or your PC. Same with Chrome - it eschews native platform UI on all devices in favor of looking the same everywhere. Good UI - by definition - doesn't get in your way. But "good UI" may not be "good m…
More than once I have encountered product people looking at the app on iOS in one hand & Android in the other and explaining that they should be the same.
99.9% of the time, normal users don't do that. What they do is switching from one app of the OS they are using to yours.
Using the same idioms as other apps of the OS is more useful because this is what users will have been trained to use.
Why a company the size of Walmart does this cross platform crap is beyond me. Do they not have the resources to actually write real native apps in actual Swift? Why is it desirable to code to the the worst common denominators for devices? Cross platform is just lazy. And React “Native” is inferior to actual native.
Ultimately the declarative way of writing apps is objectively better and more predictable than the old mutable way :) Now that said, I agree on the performance costs, and too wonder why Walmart is hellbent on this strategy, given the endless resources they have. But at the end of the day, they have a head of engineering and need to make their lives simpler just like everyone else. If you know how to squeeze the perfo…
how has this anything to do with RN ?
You can write declarative codebases in swift or kotlin, no need for RN to achieve this.
Earlier quoted context omitted.
I’ve done both native (Mac, Windows, iOS, Android, Gtk+, Tizen) and React. Your post comes off as condescending fanboy hype. I understand you want to promote React, but this approach does more damage than good. My personal experience is that “declarative” in this industry is a perennial silver bullet. What often goes unnoticed is that declarative languages are not very future-proof, as extensions are constrained by t…
> What often goes unnoticed is that declarative languages are not very future-proof [...] Surely that will not happen to React, you say, because it gets so many things right? Surely that will not happen to React, you say, because it gets so many things right? It is often not appreciated how simple React really is. Its simplicity is actually well suited to survive a long, long time. Forget classes, lifecycles, schedul…
When you pare it down to that, you're merely saying that GUIs are trees of configured objects. It's not a great revelation because the very first production GUI (Smalltalk 1972) already worked like that.
To get React from that idea, you need to add back all the stuff that you left out in the previous sentence. You add JavaScript, HTML-like syntax for defining trees and object attributes, component lifecycles and all that. And then it's not a generic idea anymore but a fairly specific implementation that will be superseded by something else eventually.
Are these discards from the jet.com acquisition or actual critical path libraries?
No, Walmartlabs is the SV based version of walmart meant to build a walmart.com 3rd party merchant amazon killer. They use a lot of node and JS. Jet.com is a NY based startup. They use F#. They have quite separate code bases, and as far as I can tell no plans to merge them.
Why a company the size of Walmart does this cross platform crap is beyond me. Do they not have the resources to actually write real native apps in actual Swift? Why is it desirable to code to the the worst common denominators for devices? Cross platform is just lazy. And React “Native” is inferior to actual native.
It's this assumption that "same experience on all platforms" (aka "branding") is desirable to "native experience on all platforms". Facebook wants facebook to feel like facebook whether you're on an iPhone or an Android or your PC. Same with Chrome - it eschews native platform UI on all devices in favor of looking the same everywhere. Good UI - by definition - doesn't get in your way. But "good UI" may not be "good m…
Apple fans like to see apple UI guidelines followed on Apple devices, and Android fans like to see Android design guidelines followed on Android, but the normal non-technical users who don't really care expect facebook to work the same way on their android phone and their iPad and their work computer. People don't want to have to re-learn how to use the wal-mart app after their grandson convinces them to give up their old Galaxy S3 and buy the new iPhone. Expecting all apps to obey the platform guidelines is just as much hubris as ignoring the platform guidelines is.
Are these discards from the jet.com acquisition or actual critical path libraries?
Walmart acquired a company called Kosmix in 2011 and spun it out as a research division called @WalmartLabs [1]. Walmart acquired the online retailer, Jet.com in late 2016 which still has their own engineering team (using a lot of F#) Stuff coming from @WalmartLabs is almost always real stuff that Walmart is using in production (website, apps, etc.) [1] https://en.wikipedia.org/wiki/@WalmartLabs
Earlier quoted context omitted.
No, Walmartlabs is the SV based version of walmart meant to build a walmart.com 3rd party merchant amazon killer. They use a lot of node and JS. Jet.com is a NY based startup. They use F#. They have quite separate code bases, and as far as I can tell no plans to merge them.
Walmart Labs also has a campus in Carlsbad, California. I've seen the Walmart crew in some JS and React meetups.
Earlier quoted context omitted.
Ultimately the declarative way of writing apps is objectively better and more predictable than the old mutable way :) Now that said, I agree on the performance costs, and too wonder why Walmart is hellbent on this strategy, given the endless resources they have. But at the end of the day, they have a head of engineering and need to make their lives simpler just like everyone else. If you know how to squeeze the perfo…
>Ultimately the declarative way of writing apps is objectively better and more predictable than the old mutable way :) how has this anything to do with RN ? You can write declarative codebases in swift or kotlin, no need for RN to achieve this.
@IBAction func setDefaultLabelText(_ sender: UIButton) { mealNameLabel.text = "Default Text" }