tag:blogger.com,1999:blog-977684764667858073.post2470648344711224589..comments2024-02-09T21:43:15.143+00:00Comments on /bɑs ˈtjɛ̃ no ˈse ʁɑ/ (hadess) | News: Geocluing the desktop, slowlyBastien Nocerahttp://www.blogger.com/profile/14621847888418739807noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-977684764667858073.post-12769109554378092992013-04-04T09:53:49.922+01:002013-04-04T09:53:49.922+01:00Unknown: as one of the original developers of geoc...Unknown: as one of the original developers of geoclue (who hasn't been contributing in a long time though) I totally support this move. With hindsight the geoclue architecture tried too much and did not achieve the final goal of Just Working: we always suspected that that might require having at least one platform/product where you clearly know your data sources and can optimize for them (and then make it degrade nicely): this never really materialized so the code is a lot of abstraction for little benefit...Jussi Kukkonenhttps://www.blogger.com/profile/12464573708791187079noreply@blogger.comtag:blogger.com,1999:blog-977684764667858073.post-7470908390240564072013-04-04T07:56:10.085+01:002013-04-04T07:56:10.085+01:00We're separating it because there's no poi...We're separating it because there's no point in having a small wrapper around web APIs in a daemon.<br /><br />We could either have exposed the API through D-Bus, introducing an unneeded level of indirection, or offered the API through a library, which wouldn't have been usable (or needing to be wrapped) for people that didn't use GObject in their projects.<br /><br />A stand-alone library makes sense in that case.<br /><br />As for moving the GeoIP code to Geoclue, geocode-glib was just a holding place for it (as mentioned in the post), and we don't want application developers to rely on it (for the reasons mentioned in the blogpost).Bastien Nocerahttps://www.blogger.com/profile/14621847888418739807noreply@blogger.comtag:blogger.com,1999:blog-977684764667858073.post-53004528514058724192013-04-04T02:42:40.058+01:002013-04-04T02:42:40.058+01:00I am still a little confused, though. It seems tha...I am still a little confused, though. It seems that Geoclue, in its current form, offers both geocoding, reverse-geocoding, calculating velocity and a few other things (hard to figure out what exactly just from the wiki).<br /><br />In that context it is not clear why we need a separate geocode-glib, and then why do we need to move the GeoIP code from geocode-glib back to geoclue.<br /><br />Not that I am suspicious of your intentions or anything. ;-) Just that it is a bit confusing for the casual reader.Unknownhttps://www.blogger.com/profile/09422865531232183193noreply@blogger.com