Live data from Hacker News

Viewing profile — southpolesteve

southpolesteve

HN member
Joined
Tue, Oct 19, 2010, 7:11 PM UTC
HN karma
801
Public activity
158 items

About southpolesteve

No profile information was provided.

Recent public activity

  1. comment
    Comment #40179917

    I worked on this project in college and went to the South Pole in 2009. Happy to see it is still making discoveries!

  2. story
  3. story
  4. comment
    Comment #23596811

    Please do!

  5. comment
    Comment #21665497

    Azure Cosmos DB does. There is a good video about it: https://www.youtube.com/watch?v=kYX6UrY_ooA

  6. comment
    Comment #17519505

    I worked on this project in college and went down to the south pole after graduation to help install some of the detectors. Neat to see the results! ~10 years later.

  7. comment
    Comment #17379245

    Yes. bustle.com, romper.com, and elitedaily.com are all 100% serverless and do 80+ million unique visitors per month. GraphQL+AWS Lambda

  8. comment
    Comment #17304792

    More specifically React https://developer.microsoft.com/en-us/fabric

  9. comment
    Comment #15735543

    I also find `this` is terrible for linting. Most tools won't be able to figure you what you attached to `this` at runtime. It's a grab bag object ripe for bugs.

  10. story
  11. comment
    Comment #15491132

    Very straightforward. We send text, they send back categories. We then map those to IAB categories in our own code

  12. comment
    Comment #15491124

    The mapping is custom. Not something they have out of the box.

  13. comment
    Comment #15475130

    I see this comment a lot. The issues are the same with any REST API. Often they have been solved many times by the community or are baked into whatever backend framework you happen…

  14. comment
    Comment #15448503

    Yes. We use the Natural Language Understanding service at www.bustle.com for doing categorization of content. It maps decently to IAB categories: https://www.iab.com/guidelines/iab…

  15. comment
    Comment #15337858

    Martin Fowler's serverless post was written by Mike Roberts. It is just hosted on Martin's blog.

  16. comment
    Comment #14237207

    The place you linked in Philly is a few blocks from my house. I've been a handful of times. Much more of a restaurant. I think it is a good example of a place trying to do too many…

  17. comment
    Comment #14206927

    We haven't seen any issues. Most of our latency critical functions are called a lot. We do get significant spikes in traffic but our CDN does handle some of that load.

  18. comment
    Comment #14144202

    API Gateway needs less config since they released the proxy style integration. In Lambda's case this means you can just return a JSON object like: { "statusCode": 200, headers: {},…

  19. comment
    Comment #14143987

    If you go to www.bustle.com or www.romper.com you get a JS app server side rendered by AWS Lambda and delivered through API Gateway (CDN in front of that). We do 50+ million unique…

  20. comment
    Comment #14103208

    In graphQL they are called mutations http://graphql.org/graphql-js/mutations-and-input-types/

  21. comment
    Comment #14103201

    You are definitely not wrong. In our case the benefits have far outweighed the harshness from the bleeding edge. But for sure we have had to do a thing or two that I would rather n…

  22. comment
    Comment #14102164

    Reading the article, I come to the opposite conclusion. Of course I need GraphQL! I want these problems solved out of the box. I want to build on the shoulders of smart people who …

  23. comment
    Comment #13000183

    Mostly it is not a big problem for us. Our functions that need to be fast have very high traffic. Our other functions don't need to be that fast. We also have a CDN in front of mos…

  24. comment
    Comment #13000112

    We use Lambda and API gateway for all production[1] requests. HTML, Server side rendered JS, API calls. All through lambda. There are some rough edges. We wrote our own framework/d…

  25. comment