Hacker Newsnew | past | comments | ask | show | jobs | submit | wlindner's commentslogin


I prefer https://github.com/alex3165/react-mapbox-gl over this library. It seems better maintained and documented.


I think it's way better than the Uber library. We tried both and ended up going with this version and it was much more flexible for our needs.


That's a good library but I had a hard time getting it to work with server side rendering. Ended up having do to a dynamic import with Next.js 3 beta just to get the page to work. This problem affects most mapping libs, not sure if Uber's is any different.


Uber's library was the reason i moved to alex3165's version. Every update came with a day of debugging. Hopefully the new version is any better.


How does Nativescript compare to Appcelerator Titanium or React Native? I know React Native hasn't been released, but they described their approach at the recent React Conf and was curious if it's similar.


I don't know about React native, but I used Titanium for a while and this looks very similar. The biggest conceptual difference from what I can see is that Nativescript allows you to make calls to any native API method. With Titanium you can only call those native APIs that have been wrapped.

With Titanium, I suppose you could say that the cross-platform wrapper API and the product are one in the same. Nativescript promotes their abstracted cross-platform API as a kinda optional add-on to the platform.

That's just my thoughts after looking at it for 5 minutes.


I just took a look at Titanium and holy moley their documentation was overwhelming. I haven't used a "native" hybrid app framework yet (only have experience with ionic), but NativeScript looks a bit more accessible to me than Titanium does.


I say the documentation is pretty ok once you get familiar with how the API is laid out. And for everything else they have the developer QA section, which is like a self-hosted stack-overflow.

I've been building a couple of simple apps on it the last few months, and it has been a pleasure.

I should be clear here -- I've been using Titanium, not Alloy.


A self hosted QA is pretty awesome. I think another thing that threw me off was how every section I clicked opened up a tab.

I'm still new to the hybrid app world and have only used ionic. I want to eventually try one of these "native" frameworks though.


I agree, Titanium classic is really great to work with once you get up and running. I tried Alloy but quickly realized it slows things down and makes it harder to develop.

So, lesson for me was use titanium classic and NOT Alloy.

Also, I would advise building your own small framework with views (things like title bars etc). Just makes it so much easier to make it look and work exactly how you want on iOS and Android.


They lost me with the switch to Alloy.


Exactly, I started on Alloy and quickly found that there was too much magic in going from templates to js code.

Once I took a step back to Titanium it all felt a lot more sane. Yes it is a little more verbose, but at least I can follow the data flow in code.

Appcelerator is going through some changes as of this week[1] which I hope will improve the documentation and ecosystem around the product.

[1] - http://techcrunch.com/2015/03/04/appcelerator-slashes-staff/


Also, their by far best evangelist, Kevin Whinnery, left for Twilio a year or two ago.


Titanium's Hyperloop/Ti.next tackles this problem, too bad the timeframe for release seems to always be 6 months from whenever you happen to check.


Not everyone is a fan of react.js, this is a nice alternative for people who want to use vanilla js.


Or Cordova/Ionic/PhoneGap?


Those are rendered with a webview. Nativescript is rendered with native components.


How do "native" hybrid apps such as, react native, titanium, etc. access the native components of the phone?

I have been developing a side project using ionic and have had a fairly positive experience so far, but from what I understand ionic/phonegap apps are just wrapped web browsers is that right?


It's pretty much identical at a high level: there is a proxy layer that is much like a message passing system. A component (web view, JS engine, etc.) says, "Take a photo with the camera" and the proxy layer calls the native code needed to take the photo with the camera.

The actual camera data is just abstract data, it doesn't care if it was generated from a JS call or from a native call.

PhoneGap and Cordova are, at the core, just a standard proxy layer and plugin API. The other "pure JS" solutions have their own custom layers.


That's pretty cool, thanks for the insight!


Sure! Full Disclosure: I run frontend engineering for Zoomdata. Zoomdata is powering the backend, it's a server that connects to big data sources. In this case, Cloudera Impala, but we also connect to plenty of other big data stores like Elastic Search, Solr, etc. Zoomdata queries those big data stores, then streams the results over a websocket to visualizations. We have a web interface for analyzing your data in standard charts, but we also allow for total customization of visualizations (like for building this dashboard). Those visualizations can be embedded using iframes, or a more advanced approach using a javascript library. I used our javascript library to embed these visualizations into my own web based dashboard.

You can find out more at our website: http://www.zoomdata.com/

And we're hiring experienced JS devs in the bay area!


Any plans for a REST api? Would be useful to query for updates since a timestamp parameter.


WhatsApp uses Foursquare too (https://developer.foursquare.com/showcase/) so, I guess that will use Facebook Places as well.


It definitely serves Facebook's location directory of Places the most.


After Facebook acquired Instagram they were really clear that they wanted them to stay independent. I wonder how "independently" they made this decision to switch to Facebook Places instead of Foursquare. Instagram ads are most likely just Facebook's new ad platform. Facebook just removed their Camera app from the app store (http://www.pcmag.com/article2/0,2817,2457866,00.asp) because Instagram IS their Camera app.


I can't think of any recent acquisitions where the same type of lies weren't uttered.

"We're so happy to be joining Billion Corp. We feel that they will let us stay independent and stick to our goals. We will continue to provide the same awesome experience you all came to know and love before we sold out."

"We're so happy to be acquiring talent instead of finding it. We will totally not, not make their project theirs instead of ours, depending on our lawyers, and our shareholders. Frankly, we're just glad we didn't have to actually spend time building a good product and hiring people like these folks, since they would've never joined us in the first place."


> "After Facebook acquired Instagram they were really clear that they wanted them to stay independent."

Snort. Giggle. Boy have I heard that one before. Everyone says that about every acquisition that isn't an acquihire. Hell, a lot of the time they even mean it.

I have yet to see a single acquisition that promised independence and autonomy actually maintain it for an extended period of time (say, multiple years).


Tbh, if it was done outside the US/Canada, I'd say it could have been an independent decision. As others have said, outside of NA, all I hear is people complaining about the quality of Foursquare's data. ;)

That said...is anyone who actually thought about it really that surprised?

They are almost always being deceptive when they make claims of "independence", "nothing will change", etc. The truth is, most companies choose to maximize shareholder value/profits over other ethical constraints because C-level compensation is chained to the shareholder's interests as best as can be managed in most companies.

It would have been nice if Facebook was more like Buffer [e.g. Transparent, Honest], but does anyone ever really seeing a company like Buffer growing to even 5% of Facebook's current Market Cap [150 Billion]?

Deception works at scale. Politics have proved that quite well, unfortunately.


I don't see this as a sign of lack of independence or evidence of lying. There are very good reasons for anyone to use Facebook places even if the US data is momentarily inferior. These sentiments strike me as unwarranted "gotcha" attempts that have little value.


It's certainly a tough line. You can say you want to be independent, but if one service charges $$$$ and another charges $0, it's hard to pick the pricey one.


Bingo.


Yeah, that was an important feature for onboarding new users. I wish people didn't have to log in, but Instagram (understandably) has API limits that require logging in once you have a lot of activity.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: