Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
soamv
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
91.
▲
by
soamv
10y ago
I think you're on an older version of the CLI, can you try updating it? https://github.com/fission/fission#install-the-client-cli
92.
▲
by
soamv
10y ago
1. One time operations like that are run at module init time. Here's a trivial example: https://github.com/fission/fission/blob/master/examples/pyth... 2. We don't support Java yet, but w
93.
▲
by
soamv
10y ago
Kubernetes gets you pretty far along the path of not messing with servers (especially if you use GKE). And we think there's other advantages to Functions-as-a-Service on Kubernetes -- it simplifies the dev workflow, improves server ut
94.
▲
by
soamv
10y ago
Yes -- Go and other compiled languages are on the roadmap.
95.
▲
by
soamv
10y ago
So we've started by focusing on improving the whole workflow, which is why we're operating at the source level. But we have occasionally heard the use case for working at the image level, and it has pros and cons, so we're t
96.
▲
by
soamv
10y ago
Agree on the importance of API gateway. Feature-wise, fission router is very simple right now. It's a service based on gorilla/mux. We had to write our own router because of cold-starts -- basically, the router needs to be able
97.
▲
by
soamv
10y ago
Hi there, it would be awesome to have Zappa support Fission, happy to talk more about it! We're working on a detailed comparison with Openwhisk, but basically -- we bet on Kubernetes as a good foundation to build this on, and it seems
98.
▲
by
soamv
10y ago
Yes, this is very much on the roadmap. We're working on better support for compiled languages. Once we have that, adding a language should be a matter of creating a plugin. (You watch this issue if you'd like to stay up to date
99.
▲
by
soamv
10y ago
[fission developer here] About that 100msec overhead -- there's a bunch of optimizations yet to be done, and also we think we can reduce the median at the expense of tail latency; but for now 100msec is good enough performance for a go
100.
▲
by
soamv
10y ago
Hi all, Fission developer here. Happy to answer any questions.
101.
▲
by
soamv
10y ago
The comment you're replying to doesn't say that etcd is insecure; just that access to etcd is equivalent in power to Kubernetes API access. It's hard to have a productive discussion in such a confrontational tone, especially
102.
▲
by
soamv
10y ago
Nice work. Feature request: track CFP dates and let people find conferences with upcoming CFP deadlines. BTW, you have "USA" and "United States" as two countries, might want to combine those.
103.
▲
by
soamv
10y ago
Yeah. This is an important problem with Lambda that doesn't get nearly enough attention.
104.
▲
by
soamv
10y ago
Ok, but is it actually computing the same thing? Are the blurred images from photopea and photoshop identical? The article mentions always doing no more than N*10 steps -- is this an approximation algorithm?
105.
▲
by
soamv
10y ago
From my experience hosting a bunch of user-provided images: 1. Strip all metadata but provide downloads of originals somewhere 2. Keep it simple, just use imagemagick's convert to remove profiles (but don't use imagemagick for fil
106.
▲
Container Orchestration Tools: Compare Kubernetes and Mesos
(platform9.com)
1 points
by
soamv
10y ago
|
0 comments
107.
▲
by
soamv
10y ago
There are financial benefits to being able to very easily overcommit resources (although Lambda is just one way to do that).
108.
▲
by
soamv
10y ago
I run https://glimmer.cc . It pays for its own hosting costs. It's not very profitable but it's steadily growing.
109.
▲
by
soamv
10y ago
Nice! Just tried it out and it seems to work well. Why does dumb-jump-go want me to save my files before jumping?
110.
▲
by
soamv
10y ago
I read the article and the linked blog and I still can't tell what this has over plain Kubernetes deployed on AWS -- what am I missing? > Storage for applications deployed on Supergiant is allocated on high-availability arrays, howe
111.
▲
by
soamv
11y ago
I haven't yet figured out exactly how much to offer, but something like 10GB is what I'm thinking.
112.
▲
Show HN: Glimmer, a Simple Private Ad-free Photo Sharing Service
(glimmer.cc)
3 points
by
soamv
11y ago
|
4 comments
113.
▲
by
soamv
12y ago
This is a great question! I find that the act of explaining the problem itself helps a great deal in figuring out what the pieces are. It's totally okay to just talk to a developer about the problem and start sketching out your ideas,
114.
▲
by
soamv
12y ago
Well, this is about userspace access to nvram, with the nvram mapped as memory. It just so happens that cache management is one of the hard parts of doing that, so that's what these new instructions are for.
115.
▲
by
soamv
12y ago
You started with asking what you can do to help, then went on to discount her experience as an outlier despite her clearly saying it wasn't, and then finished more or less by implying that _she's_ racist. So if you're asking
116.
▲
by
soamv
13y ago
Or, A cuts the pizza down the middle, B chooses a half, A and B cut their halves into thirds and C chooses one third each from A's and B's halves.
117.
▲
Computer Swap on Curiosity Rover
(jpl.nasa.gov)
2 points
by
soamv
14y ago
|
0 comments
118.
▲
by
soamv
15y ago
That's interesting. What is the cost of switching the stack when calling C code? Do you allocate a new stack every time a C function is called from Rust? If you inline a compiled C function, don't you have to do the stack switching for wh
119.
▲
by
soamv
15y ago
Part 1: http://irinawerning.com/back-to-the-fut/back-to-the-future/
120.
▲
by
soamv
15y ago
Can't you just do: p/x *foo@100
More ›