Hacker News new | comments | show | ask | jobs | submit | adregan's comments login

I just set up a free ssl cert via AWS[0] yesterday for serving static assets and securing an API Gateway endpoint (previously was using a free Lets Encrypt[1] cert). So hopefully there will be more ways around certification authorities who charge.

0: http://aws.amazon.com/certificate-manager/

1: https://letsencrypt.org/

Some of these folks are taking plea deals to get out on time served. That time they are serving? It's accrued while they are waiting to go to trial. In a hideously over crowded prison system with overworked public defenders, the right to a speedy trial is a thing of the past. Here is a particularly terrible story of this kind: http://www.newyorker.com/magazine/2014/10/06/before-the-law

Tragically, the young man from the story committed suicide last year: http://www.newyorker.com/news/news-desk/kalief-browder-1993-...


I too was expecting an article on Marinetti and his cohorts and their love of violence, speed, and strange dinner parties.


I like to think that Roland Barthes would have loved to use "The Road Not Taken" in his piece "Death of the Author"[0]. Truly, at a scale that's frankly staggering, agency has been given to the reader—though one could also argue that the clipped version of the poem often remembered is a case of remixing and rewriting and that the agency isn't merely passive interpretation but a very active creative endeavor.

0: http://www.ubu.com/aspen/aspen5and6/threeEssays.html#barthes


Granted, I'm only 30, so take my anecdotal experience as an older person with a grain of salt, but I've found that getting older isn't so hard as everyone seems to get nicer in their 30s. Life's easier when people are nicer.


When I search, all but 3 results are now news stories and blog posts about googling "What happened to the dinosaurs." I don't find those results to be particularly useful either.


Searching for "What happened to the dinosaurs" returns in the answer box the text "Google is Wrong About What Happened to the Dinosaurs", which is a cute instance of the Liar's Paradox: http://en.wikipedia.org/wiki/Liar_paradox


A few of the flux implementations have the concept of "rehydrating" state (serializing and deserializing the stores), which does allow the client side to reuse the data and keeps the component from refetching the data.

A useful pattern I discovered was fetching just what is necessary to render the page on the server. Then pass the state to the window object through a script tag and recover the data on the client side and rehydrate. Any additional data (or potentially slow returning), I fetch client side via `componentDidMount` [0] which isn't called on the server. This way, I can get a loading screen up as quickly as possible with a few elements custom to the user.

I should note that even thought the flux library I was using, flummox [1], works great for this, I can't recommend it as in the month and a half I was working on my project they've decided to quit and recommend a different library, so I'm not sure what to recommend now (the frustration I feel over this quick turnaround is an entirely separate topic, though).

0: https://facebook.github.io/react/docs/component-specs.html#m...

1: http://acdlite.github.io/flummox

2: https://github.com/acdlite/flummox#40-will-likely-be-the-las...


the newly recommended library, redux, is great. Flummox was great too, but redux is better, I recommend giving it a shot if you haven't.

To the original point, you are still sending the data twice, once in rendered html, and once in that state that gets rehydrated.


Depending on the kind of content t you have, that's hardly an issue. I've built a big site like this, and gzip does an extremely good job at filtering out duplicate data. Check the source of http://viva.vlaanderen/


when you view the source of your page, you see that very little of the dehydrated state is used to build your initial markup.

The entire rendered source is 142K. I isolated the actual markup, and it weighs in at 31K.

In other words, your dehydrated state is 4x bigger than your html rendering. And that's not including your 750K main.js file that also gets downloaded.

That's almost 1MB of downloads (not including images and stylesheets) just to "app-ify" your 31K of markup. I tend to agree, it's not a problem. Or perhaps, it's not one of the biggest problems. But it's not "hardly an issue" either.


Is there a good guide out there that lists very plainly:

1) All of the information one should ask for re. equity. 2) What to do with that information.

I don't necessarily need to know all of the in and outs right away, but it would be nice to know a some of the key things that I really ought to know in order to get some kind of handle on it.


I would like this , but one additional question is "when" should you ask? As in, what part of the interviewing process does one ask about outstanding shares, etc..

Should it be after an offer is extended, immediately after the technical part of the interview, etc..?

I would feel awkward asking some of these specifics about financing early in the process.


Its only relevant after an offer is extended. View it as due dilligence...they are giving you equity in exchange for cash/less salary..the burden should be on them to prove its a good or fair deal.


> I would like this , but one additional question is "when" should you ask?

When discussing compensation, I assume. If someone offered you $X dollars per year and Y HappyTimeFunBucks, I'd definitely want to know more about the HappyTimeFunBucks before deciding.


I find this to be one of the better guides. There is a list of questions at the end you should be asking.



Benjamen Walker recently released a 3 part podcast called _Instaserfs_ examining the sharing economy. It's worth a listen: https://toe.prx.org/2015/06/instaserfs-i-of-iii/


While it doesn't add up to a terribly large amount of extra characters, you are missing the function keyword (ie. `handleDoubleTap: function(e)`) in the ES5 example.


Ah, now I think I understand what they were trying to argue—full ES5 versus ES6 where I took it to be ES6 versus ES6-using-class.



Applications are open for YC Summer 2016

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact