|
Sir_Substance posted:I'm curious to hear your guys opinions on the whole "antisocial" debate. Actually using Glass in a social setting is worse. If you're looking at someone, then look at the Glass display, the other person sees you kind of looking at them but not really. The other thing about Glass is that the difficulty in acquiring them (had to write an essay and pay $1500, although now it's effectively just paying $1500) meant that the folks who actually had them were really keen on the idea of wearing them all the time. If the devices were more accesible, and actually had utility, you might find more folks purcashing and using them for specific uses, but not going out in public with them.
|
#
¿
Feb 5, 2014 02:13
|
|
|
|
| # ¿ Apr 27, 2024 19:55 |
|
|
Three Olives posted:Do they expect to swap out several different versions at no cost? Three Olives posted:Do they not really plan on releasing this for such a long time that a wider user base would not expand development in a realistic manner? Those things are entirely on Google to fix. The platform can't move forward until that's done, it doesn't really matter how many folks adopt it.
|
|
#
¿
Feb 5, 2014 04:31
|
|
|
TheReverend posted:At the cost of sounding like a Google apologist, it's clearly labeled GDK preview. They most likely aren't done working with it yet. TheReverend posted:I got into the game late (for glass developers) and never had to deal with the MIRROR API so thank goodness for that but the GDK isn't so bad. I think it doesn't have a lot of documentation because a lot of it is just the normal Android stuff. The GDK isn't terrible, but if you really try to exploit its features in depth, you'll find the sample code only scratches at some of its features and that the GDK-specific API documentation doesn't document quite a number of methods, leading to trial and error to make stuff work, with no assurance it won't break in the next platform update. Perhaps that's all part of the experience given that the GDK is a "sneak preview". But as an engineer, when there's a number of other projects on your plate, you're probably going to invest time in something that doesn't result in a lot of process inefficiency and won't have to be redone next month. That's what's holding the platform back right now. Edit: At least with Android, if there's an ambiguity in the (otherwise generally quite good) documentation, you can actually check the framework source code to see how things are implemented. The Glass layer on-top of Android is proprietary so you can't really do the same there without a reverse engineering effort. That makes getting the documentation right even more important. ExcessBLarg! fucked around with this message at 19:03 on Feb 5, 2014 |
|
#
¿
Feb 5, 2014 18:57
|
|