If you need public data from multiple cryptocurrency exchanges but don't want to deal with weird differences in exchange APIs, Blocktap[1] is a free GraphQL API (that I assisted in developing). We also open sourced our web socket data collection tool CCXWS[2]. It's a single, consistent Javascript API for most major exchanges.
Yeah, I guess less so now, but before C# was open sourced the only viable option was Windows servers and people usually used SQL Server with it. So in that case many people chose to lock themselves into that vendor and stack. So in my mind Lambda as a back end is no worse than that in terms of vendor lock-in. I suppose that Amazon will be able to provide support for many years given how much of the internet currently runs off of them.
Hi, I'm currently seeking work around the NYC area, currently based in Brooklyn. I've previously done a lot of Javascript, PHP, Ruby, and mobile iOS (Xamarin) work. Very interested in new technologies and solving problems.
Hey this looks cool. I see it's a beta, but some ideas that would be really useful to me and maybe others. MapBox (particularly the desktop version) can create custom stylesheets and do high quality image exports. I like those features if I don't plan to leave the map on the web (e.g. print, email). It would be good also to view the square area covered inside a polygon and be able to edit one once it's placed.
Hi! Would a PDF export be good for your print / email case?
About square area, do you mean to calculate the area in square kilometres and display it for polygons?
You should be able to edit a polygon once it's placed, just click the "move" icon in the top right corner of the sidebar.
1) Yeah, definitely. I suppose one could screenshot, but having a little more fine-tuning as far as dimensions, image size, etc is far more useful.
2) For sure, much like the border distance.
3) Ah, I didn't see the edit icon. Very cool.
Man, I've never had a problem with a broken iPhone screen. I worked for months on a pretty large construction site breaking up concrete while dropping my phone fairly regularly and it's still aces.
Obviously a stronger screen would be great, but a case does wonders if you want a functioning phone for now.
Well yeah, 3 lines of front end CSS. But there's a bit more back end logic that goes into it. But I do like the concept of relatively small yet profitable changes.
What's your definition of "picking up" a language?
A) Writing a "Hello, World"?
B) being able to fix a simple bug in a program?
C) Writing a small program that solves some domain problem
D) Writing a program that solves a "real world" problem, making use of the programming languages' strengths and conforming to standards (something that other people would let you commit into a repository unchallenged :) )
I'm certain A) takes only a few hours, and B) can be done in a day.
As Norvig says, you can do C) if you write in the new language like you would in a language you already know (not much of a problem if we're talking C# vs Java).
This roughly corresponds to my experience with Erlang; keeping in mind that "D" in Erlang relies heavily on its OTP ecosystem, which is fairly complex and different from most other languages.
Ignoring OTP, my ability to use the language proper was pretty much complete within a week, owing to its simplicity and my prior background in functional languages.
This is in contrast to C, which I have been using for around 15 years now, yet am still learning nuances of the language. (Things like: which integer operations are undefined on negative numbers; how integer promotion works with shift operators; how "restrict" interacts with scope.)
C is almost a fractal of nuance that does take years of experience to comprehend; Erlang has no nuance. (The closest thing to nuance I can think of is the relationship between integers and floats; and even then the takeaway is "it just works; don't worry about it". The only language in which I've seen the number hierarchy handled more cleanly is Racket.)
Erlang has a few syntactic conventions that will probably seem familiar only if you've used Prolog. But, like any other language syntax, you learn it pretty quickly and within itself it starts to makes sense.
This was actually the biggest syntactic stumbling block for me, but because I know Prolog. It's definitely not Prolog semantically, and differs syntactically as well (e.g. clauses are separated by "." in Prolog but ";" in Erlang); to this day I sometimes find myself writing Prolog in Erlang.
[1] https://www.blocktap.io/
[2] https://github.com/altangent/ccxws