And so, by cleverly digitizing his precious type specimens -- which he fought bitterly to protect from automation -- we've done exactly what he strove to prevent. Are you happy now?
You've obviously never hit one of the many edge-cases in front-end development that are simply not possible (without an incredible amount of hacking effort).
Multi-line vertical text-centering is a great example (try v-centering a paragraph of variable/unknown height). Or the way text wraps around an image differently at varying widths ("can we make it not break like that? I don't like how it flows at X width"). Or dynamically truncating a block of text and adding an ellipsis automatically, at any given size, in a responsive design.
There are a LOT of examples of "blue sky" design that simply cannot be translated easily, if at all, into HTML/CSS. This is why it's so important that designers have fundamental understanding of the technologies they're working with.
I have no degree and I am 0.5 out of 1 full time programmers at a major footwear apparel company. Just keep working, keep reading. Fuck the paper credentials. Never stop learning.
I would like to know why the Indian Sanskrit scholars refused to help NASA. My best guess is that they are wary of the possibilities of AI when expressed in such an efficient language.
I feel the same way. These are certainly funny signs, but they're completely useless and ultimately distracting from the park in which they're placed. I will, by default, sit on a bench (or the grass) unless I am explicitly told not to. I don't need an cutesy sign to tell me I CAN sit.
Sure, these signs are cute, even original. But without any honest purpose beyond being witty, they're frankly not adding value to the public. Yes, I would prefer to see traditional signs executed this way when needed in parks (where a posted sign is actually warranted) but I would ultimately prefer not to see any signs at all.
My only comment is that I don't see much of a real-world use case for it. It strikes me as a one-off or a novelty app that'll be old news as soon as it hits.
Don't take my word for it, though. Hope it gets traction!
JSON is a container for data. It is no less safe than XML, HTML or plaintext. It's your application's architecture and basic security measures that define how "safe" your JSON is. CSRF tokens?
Absolutely not hard, but PG is too busy/lazy to care about making improvements to HN. The people here who argue it's "hacker tradition" to embrace minimalism/build browser extensions yourself to make HN actually modern are only enabling PG's unforgivable laziness.
Honestly PG, "unknown or expired link" should not be a thing anymore. Not to mention how slow this shit gets.
For a community composed of basically the best programmers in the world, HN really sucks. I say this all with pain as I am a HN-lover.
I'm sorry. I disagree that you are "institutionalizing a gap" by not going out of your way to get women because research says they are less likely to apply. There is no "institution" presented by simply opening up public applications and sorting through the responses.
I have respect for the lengths this person went to in order to increase gender representation at her event. However, I disagree fundamentally with that statement.