Re:Google’s ML Kit makes it easy to add AI smarts to iOS and...
by erk__ on Tuesday May 08, 2018 @03:21PM
(#17023927)
Google are good at choosing names... http://www.elsman.com/mlkit/
[ Parent
| on HN ]
Re:Google’s ML Kit makes it easy to add AI smarts to iOS and...
by hooluupog on Tuesday May 08, 2018 @03:52PM
(#17024258)
Google: ARCore MLkit
Apple: ARKit CoreML
Re:Google’s ML Kit makes it easy to add AI smarts to iOS and...
by Klathmon on Tuesday May 08, 2018 @03:57PM
(#17024317)
Apple have been using (name)core and (name)kit for a lot longer.
As an aside, how do you escape a star character on HN without dropping to a code block?
Re:Google’s ML Kit makes it easy to add AI smarts to iOS and...
by colonelxc on Tuesday May 08, 2018 @04:16PM
(#17024553)
https://news.ycombinator.com/formatdoc
You need a space after the star, (* core) which is not like escaping at all...
Re:Google’s ML Kit makes it easy to add AI smarts to iOS and...
by zaksoup on Tuesday May 08, 2018 @06:15PM
(#17025764)
nit: I think the apple naming convention has been (name)kit and core(name).
Re:Google’s ML Kit makes it easy to add AI smarts to iOS and...
by saagarjha on Tuesday May 08, 2018 @07:02PM
(#17026112)
Apple seems to use both, but they've been leaning towards Core* rather than *Core recently. We have CoreAudio, CoreBluetooth, CoreFoundation, CoreGraphics, CoreImage, CoreLocation, CoreText…but there's also WebCore, JavaScriptCore, QuartzCore, and ImageCaptureCore.
Re:Google’s ML Kit makes it easy to add AI smarts to iOS and...
by Klathmon on Tuesday May 08, 2018 @06:24PM
(#17025849)
I am really only familiar with webkit and webcore, so I just assumed most others followed that pattern!
CoreML always sounded wrong to me because of that.