Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jbert
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
91.
▲
by
jbert
13y ago
Thanks very much for that. In terms of comparing the two approaches, I can see that if you are granting different creds based on a user auth, an STS is useful to grant temporary creds limited to a subset. I'll need to look up the detai
92.
▲
by
jbert
13y ago
So - there has to be some trust to the client, unless the resource is public (or locked down with end-user creds). In this case, some kind of creds need to go into the app, right? So the best practise is simply to make those some creds whic
93.
▲
by
jbert
13y ago
Would it work to have a different response to collision, namely to apply a reverse of your last step? (A full reverse or partial). There might still be corner cases, but it would seem to resolve the described issue, since irrespective of wh
94.
▲
by
jbert
13y ago
There's presumably no more energy being dispersed than with manual brakes. The current brakes will heat less (due to energy in the ERS). If the ERS is full, you either switch over to dumping the heat into the brakes (no ERS, switching
95.
▲
by
jbert
13y ago
Still not sure how that helps. In both cases, we have creds embedded in the app which can be used (and only used) for access to the AWS resource. In one case directly (via an IAM limited account), in another via a token they can request. In
96.
▲
by
jbert
13y ago
I'm being dumb. I can see that it is preferable to embed credentials for a restricted IAM acct, not your root/master AWS account. But how does using a TVM improve the situation? Surely you still need to embed creds which allow the
97.
▲
by
jbert
13y ago
> but if there are no normal returns involved, nothing on the stack will ever be deallocated, and your program is effectively just one giant memory leak. This is true, but there is the glorious exception which is "Cheney on the MTA&
98.
▲
Cheney on the MTA – never return
(pipeline.com)
2 points
by
jbert
13y ago
|
0 comments
99.
▲
by
jbert
13y ago
I think the main difference is the way the language and runtime collaborate to schedule multiple events. Note the use of the 'select...case' in the example code. These slides go into some more examples: http://talks.gol
100.
▲
by
jbert
13y ago
I wasn't quite getting that code when I first read it. Now I can see it allows you do "discard" all the pending reads from the input channel (and avoid writing to a possibly-closed 'out' channel), but wouldn't
101.
▲
by
jbert
13y ago
You can buy a DVD set which has the original versions (no CGI, Han shoots first etc) on the bonus disks. http://starwars.wikia.com/wiki/Original_unaltered_trilogy_%2... IIUC, only the 2008 release set has them. But you
102.
▲
by
jbert
13y ago
I'm not arguing the point that generics are unuseful. But imho the method should not be named for the compiler-type of it's return value (unless it's a type converter like int2string or similar). It should be named for the
103.
▲
by
jbert
13y ago
Design is different to the nitty gritty but I'd say not necessarily easier or harder. Just as no battle plan survives engagement, no design survives the realities of implementation. This is what makes waterfall hard and agile.attractiv
104.
▲
by
jbert
13y ago
Move up the value chain. If you can turn a design into code, learn to turn a spec into a design. If you can turn a spec into a design, learn how to understand a problem and produce a spec to solve it. If you can understand a problem, learn
105.
▲
by
jbert
13y ago
PRNGs (pseudo-random-number-generators) take in a small amount of randonmness (a seed) and produce a long stream of numbers from that. Anyone using the same PRNG can look at the output of yours and try to put their PRNG in the same state. I
106.
▲
by
jbert
13y ago
> The problem with Perl, IMO, is that there are too many clever ideas Perl's learning curve is shallow (easy to pick up) but long (the language is big). One explicit design goal from perl which isn't talked about much is &quo
107.
▲
by
jbert
13y ago
I like to use a syntax error if I'm implemented in the middle of a number of related changes. As long as I follow basic hygiene of running/compiling the code before committing, I'll be reminded of where I was. I typically use
108.
▲
by
jbert
13y ago
Duodecimal counting still persists in some places in inches-per-foot and in the UK until 1971 in the "pounds, shillings and pence" old-money system. (12 pence to a shilling and 20 shillings to a pound). It's interesting to me
109.
▲
by
jbert
13y ago
I think the thing which is defeating my intuition here is the continuity issue. "If a periodic function is continuous and nonconstant, then it has a least period, and all other periods are positive integer multiples of the least period
110.
▲
by
jbert
13y ago
I continually find this particular point useful and enlightening. (Joel's whole corpus of stuff is worth a read. At the risk of causing a hacker news "joel storm" of submissions, check out the pricing/segmentation piece:
111.
▲
by
jbert
13y ago
Such escapements can be made a feature: http://en.wikipedia.org/wiki/Corpus_Clock
112.
▲
by
jbert
13y ago
Apache has a nice system where all allocations come out of pools. http://apr.apache.org/docs/apr/2.0/group__apr__pools.html You can then create a new pool to handle a single http request, then discard the who
113.
▲
by
jbert
13y ago
Perl seems to pass nearly all the tests (including uppercasing baffle): $ perl -E 'use utf8; binmode STDOUT, ":utf8"; say uc("baffle");' BAFFLE The only failure I can see is that it treats "no<combi
114.
▲
by
jbert
13y ago
My guess/intuition was that walking backwards might defeat any memory pre-caching at various layers (CPU, OS). I wrote this quick-and-dirty code [ http://codepad.org/d9ilykxA ] to try and test the effect. To me, it'
115.
▲
by
jbert
13y ago
It's interesting that the population seems to be very critical of any food-health articles, presumably from over-saturation of poor science reporting. (Best example of this I know of - http://kill-or-cure.herokuapp.com/
116.
▲
by
jbert
13y ago
Dumb question: What breaks with the following approach? 1) set last_write_wins=true (so all updates, always apply, as described in the article) 2) avoid the "partition/rejoin may cause old values to stomp on new" issue by hav
117.
▲
by
jbert
13y ago
I think it's unfair to lump the faster-than-light-neutrino experiment in as bad science. They pretty much said "this is really odd, please suggest your explanations".
118.
▲
by
jbert
13y ago
I see it as they had removed the "continued mutual goodwill" from the equation, and were offering nothing additionally. (If my current employer asks me to sign something without any additional incentive, I'm not going to say
119.
▲
by
jbert
13y ago
It looks like the underlying feature which enables reverse debugging, Process Recording, could do what you describe: https://sourceware.org/gdb/wiki/ProcessRecord the data may only be in-process, if so it would ne
120.
▲
by
jbert
13y ago
Could do, but why tie to time? What you actually trying to minimise is time spent queueing. So record when people arrive and apply a discount/surcharge depending on how long they queued (or just based on the number of people ahead of t
More ›