pea

17 ms·

181.
Why data scientists are blocked from creating value(blog.nstack.com)
3 points by pea 9y ago|0 comments
182.
by pea 9y ago
This is really interesting. Firstly, I wonder how fundamental notebooks have becoming to the preparation phase in the last couple of years (to avoid https://cacm.acm.org/system/assets/0001/3683/long-filen
183.
by pea 10y ago
Hey guys, I'm Leo - one of the founders of NStack. We started work on NStack around a year ago, to help data-scientists productionise their models and compose them together with various data sources. We built NStack using a mixture of
184.
by pea 10y ago
BTW this is what we're hacking on at NStack.. we're building an analytics platform which gives you a high-level language which provides an abstraction over infrastructure. The aim is that data teams can productionize code without
185.
by pea 10y ago
NStack | London, UK | Full time | Onsite | Functional Developers / Data Scientists | http://nstack.com NStack lets data analysts to do sophisticated data work in the cloud without a team of engineers. To accomplish this, we
186.
by pea 10y ago
NStack | London, UK | Full time | Onsite | Functional Developers | http://nstack.com We’re a building a platform for composable, data-driven microservices using a mixture of Haskell and Linux systems technology (including contai
187.
by pea 10y ago
NStack | London, UK | Full time | Onsite | Functional Developers | http://nstack.com We’re a building a platform for composable, data-driven microservices using a mixture of Haskell and Linux systems technology (including contai
188.
by pea 10y ago
NStack | London, UK | Full time | Onsite | Functional Developers We’re a building a platform for composable microservices using a mixture of Haskell and Linux systems technology (including containers, systemd, dbus), with some typed DSLs, s
189.
by pea 10y ago
We're a startup in London (shameless plug: www.nstack.com) using Haskell to develop a containerised microservices platform, bringing in lots of low-level Linux coding along with high-level concepts such as typed DSLs. So far it's
190.
by pea 10y ago
NStack | London, UK | Full time | Onsite | Functional Developers We’re a building a "Cloud OS" for composable microservices using a mixture of Haskell and Linux systems technology (including containers, systemd, dbus), with some t
191.
by pea 10y ago
Great article. Another good way we've had this explained is: if someone is in a burning building, you are the option of jumping out of the window.. There may be a 95% chance they will die, but they're in so much pain that they&#x2
192.
by pea 11y ago
Yes, layering is somewhat of a hack to get around the fact that most OS package managers are mutable. IMO nix / guix have a much better approach here.
193.
by pea 11y ago
StackHut | London | Full Time | ONSITE We’re a London-based startup working on a microservices-based “CloudOS” using a mixture of OCaml, Linux containers, and Erlang/Elixir - with some DSLs, systems code, and distributed systems thrown
194.
by pea 11y ago
Haha you're right. I love flock of birds analogy.. and thanks for the mention! We've also been floating 'Software defined infrastructure', 'Software defined compute'. Sounds a bit like something out of a Gartne
195.
StackHut: deploy classes as Docker-based microservices(github.com)
4 points by pea 11y ago|2 comments
196.
Building a PhantomJS Cloud API(blog.stackhut.com)
2 points by pea 11y ago|0 comments
197.
by pea 11y ago
Hey Jake -- thanks for your feedback, that is really helpful. We're going to add some better pricing. How would you like this to work? - per month, flat rate, ups w/ usage - per request - per compute / storage We really like
198.
by pea 11y ago
Great to see Lambda stepping up their serverless game. We're big fans of this approach and are hacking on something similar to this at StackHut[1], but: * Mostly OSS to avoid lock-in * Git integration * Full stack specification (OS, de
199.
Calling Python functions through HTTP, without a server(blog.stackhut.com)
3 points by pea 11y ago|0 comments
200.
Deploying code: it was meant to be so easy(blog.stackhut.com)
3 points by pea 11y ago|0 comments
201.
by pea 11y ago
Lack of git/versioning integration is pretty key and is one of the downsides of requiring deployment from the browser. We're hacking on something that solves this @ https://stackhut.com .
202.
by pea 11y ago
Hi Jake! Sorry you're having issues. I'm presuming you're on Sky in the UK? They are currently blocking HTTPS on various CloudFlare endpoints (such as ours!) We're attempting to get this sorted ASAP. Let me know if this
203.
Show HN: StackHut – Deploy your code without a server(stackhut.com)
6 points by pea 11y ago|1 comments
204.
Show HN: Open Source PDF Compression API(stackhut.com)
5 points by pea 11y ago|0 comments
205.
Show HN: PDF processing API powered by Docker(stackhut.com)
3 points by pea 11y ago|0 comments
206.
Going Serverless with Firebase and StackHut(blog.stackhut.com)
3 points by pea 11y ago|0 comments
207.
by pea 11y ago
Hey all! I'm one of the devs @ StackHut and am here to answer all and any questions/rants/ideas/feedback. Cheers!
208.
Show HN: StackHut – Your code as a cloud API, powered by Docker(blog.stackhut.com)
10 points by pea 11y ago|1 comments
209.
by pea 11y ago
Hey Stephen -- Honestly, it was just what I had more experience using; I always presumed Phantom is more consistent and malleable, albeit sometimes a pain to configure. You are definitely right on the simplicity aspect. We're aiming to
210.
by pea 11y ago
Absolutely, we're more concerned w/ use-cases vs. Docker itself. PhantomJS is a great tool, and we're using it to show off the platform which hosts this sort of stuff in the cloud (with Docker!). Would love to get some more f

More ›