jbnicolai

Joined 13 years ago

Karma
113
Submissions
54
Member since
Mar 18
username at jbna.nl
View on Hacker News

Recent submissions

Comment · 3 years ago
That's essentially what axioms are. Wether it's reasonable or not depends on your intuition of both axiom & implications.

This is where the axiom of choice is interesting; many people feel that it seems intuitively reasonable, but the implications are counterintuitive (e.g. banach-tarski)

Comment · 8 years ago
Comment · 8 years ago
Agreed. The problem is the risk of small, relatively hard to spot & nearly impossible to properly debug mistakes.

> A{2,4} -> AA(A|AA)

Comment · 8 years ago
Comment · 10 years ago
Comment · 10 years ago
Thanks! Definitely going to look at these. Can't believe I wasn't aware AWS came with an API gateway service as well.
Comment · 10 years ago
Good question! I didn't include too much context in the top-level question to keep the discussion as broad as possible, and hopefully have advice applicable to others as well, but am more than happy to expand a bit here.

It concerns a large multinational in the transport sector. While we have built up a strong digital department, there's a lot of catching up to do, so the more 'batteries included' any given solution has the better.

On the other hand, it's crucial that we can extend any given tool as there will undoubtedly be unforeseen or non-default scenarios. For example: we'd love to perform some analytics on not just what customers are calling the APIs, but perform more detailed queries based on e.q. request parameters, geoIP, or perhaps even User Agent headers. It is absultely no problem to have to do this ourselves by performing raw queries on the database, and perhaps built our own dashboard around it, but again; if there's something that already covers a lot of these cases that'd be ideal.

The minimum required functionality is that the tool can operate as an authenticating proxy, only passing on requests when the e.g. OAuth2 headers are verified. Other security aspects, such as throttling and rate limiting are a requirement as we're dealing with systems that must be protected from unforeseen load.

Nice to haves are features such as autogenerated documentation pages, where clients can test the APIs from within their browser. On the other hand: rolling this ourselves using Swagger wouldn't be a problem either.

Research so far has included looking at some open source tools, e.g. Kong[1] from Mashable, apigee[2], reading up on Gartner's magic quadrant re. API management, and demos from IBM and CA. Costs of these vendor tools aren't a major concern, lack of modifiability absolutely is. I'm currently leaning towards Kong, but am wondering if others have interesting experiences to share.

[1]: https://getkong.org/ [2]: https://apigee.com/ [3]: https://www.gartner.com/doc/reprints?id=1-2DC669J&ct=150409&...

Comment · 10 years ago
Comment · 10 years ago
Just serialize the state in the hashfragment of the URL ;)
Comment · 11 years ago
In the python example you're running a function, while in the grep example you're launching a program (grep) from your shell.

To make the comparison more fair you'd store the python program and time starting and running both from a shell.

Comment · 11 years ago

    So close to haiku,
    only one more syllable,
    great embarrassment.
Comment · 11 years ago
Comment · 11 years ago
Rather, 'under the hood' it _is_ a lisp (that is, an AST). The powerful feature here is that you visualize (project) the AST into a more concise representation

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton