Hacker Newsnew | past | comments | ask | show | jobs | submit | udoprog's commentslogin

It is not far fetched given that "big boobs" is interpreted in a societal context which is dominated by male gaze. That is, big boobs is "artsy" and "funny" for a man, since he is the target audience of the joke. Someone at the other end of the joke might take offense. Especially if you experience similar events on a daily basis within your professional environment. Just because something could qualify as art, doesn't mean that you are not allowed to scrutinize it.

I suggest that you employ a bit of empathy instead of drawing assumptions about the persona of the other party.

Putting up twenty links to Wulff & Morgenthaler (epic comics) and using it as an educational/critical source without context only dilutes what you are trying to say, i.e. people should more relaxed.

That being said, being able to figure out how to spell anything sensible using 8 sixteen-digit letters is an accomplishment.


I fail to understand the step where the other end takes offense. It's almost like underpant gnomes: 1. Big boobs in code. 2. ????? 3. Offended people.

What's that stage?

Big boobs are a fact of everyday life. If for some reason their mention casts such strong emotions, perhaps there are deep problems in the workplace culture. Art lets you expose that. But art is not a source of those hypothetical problems, rather than reactions to it are merely indicators.

I don't say people should be more relaxed. People should get better; It usually involves them getting a little worse first. Force them to reflect. Force them to negotiate peace with their sexuality and their environment.


No, the main point is to show how simple client verification actually is. This implementation is one step up on the application stack into a comfort zone which seems to be more acceptable by devs.

I believe in design in depth, and by allowing the most basic of techniques (form submission + cli tool stack) to handle something that is generally perceived as difficult and letting people "get" the manual process, the automation might not seem as daunting.

I did not intend to create a standard, just to provoke more discussion. I would however by gladly surprised if I woke up tomorrow and twitter allowed me to sign in by solving a challenge instead of a password : ).


Not so different in theory. This just displays how little fuzz client certification can be on a higher level which is more easily approachable by web developers.


Side note: Firefox extensions aren't native code, they're written in JS.

EDIT: I do however agree that chrome is more well designed. Firefox has been through a lot of iterations through the years.


While most Firefox extensions are in JS, I believe you can bind to native c++ as well.


Chrome also allows you to access native code in extensions using NPAPI plugins: http://code.google.com/chrome/extensions/npapi.html


This is an epic introduction into virtual machines for the brave C coder. Very neat and clean, thank you.


I haven't perceived that people think C is significantly scary (or evil). There are however many compelling reasons not too choose C in the present RAD/Web/Cloud/Solution Business world.


Indeed, I currently get turned off by most books I pick up, simply because they start out on a too basic general level.

If you however dig a little deeper you can usually find stuff that isn't too tutorialish. Like http://www.c-faq.com/top.html which has been an extremely solid resource for me.


I'm hoping to make this book ramp up faster than LPTHW, since I'm assuming people have either read that book or know one programming language already. However, I'm also a big proponent of practicing the syntax even if you think you're an expert already. It just makes things way easier later on.


Personally, I hope that this book will work for people who don't already know a programming language. C seems like a great first language to learn if only because (if taught well) it exposes a large number of the underlying details of how programs actually run on a system.


Moving from Python to C is a very good move. It allows you to go from programming to inner workings, everyone should have a solid knowledge of C since it give you the tools to identify and correlate aspects of other languages to reality.

I don't understand what "practicing the syntax" means (language barrier?), but I'm not suggesting that I've stopped learning, which I never will.


Different people learn differently. Some people don't like to practice the trivial practice stuff, and prefer to breeze through the beginning, read through new material, and then take on some real project.

Rich Hickey, recently in an interview, said he doesn't do programming exercises - he is not interested in programs which don't make the computer do something useful, interesting, or both.

I, for one, type the trivial examples. Or else, I simply forget how to use them. For example, you have list comprehensions in Python, Racket, F# and if you ask me to do a list comprehension right now without looking up the reference, the only one I will get right is Python. I recently started learning F# and didn't type much code; so the concept is known, but since I didn't practice the syntax, I will have to learn it again.

That's what he means by practicing syntax.


Got it.

I wouldn't however say that the complexities of C is it's syntax (unless you're playing around with macros : ) ). But I guess the concept can be applied broadly, like remembering functions, headers and other language specifics.


how about 'if you are proficient at another language, feel free to skip to chapter x'? and put the generalized stuff at that point


If you really are that proficient, you should be able to figure out what you can skip.


I'm not so sure about that. The devil's in the details - you might think you know something well enough to skip it, but get caught out later.


Sometimes due to language discrepancies, skills don't transfer and there is no easy "feel free to skip to chapter x".

For example, a conversant Python programmer's idea of string, and strings in C are 2 different things. A conversant C programmers idea of looping is different from idiomatic looping in Racket(and other lisps).


actually you are right, it completely doesn't work in that example


It seems like the real solution would be to introduce low level guarantees and memory access (similar to Java) and the option to disable the GIL and C API extensions in CPython (until a new API is introduced?).

Also, give the developers access to some real synchronization primitives, that would be sweet.

I'm not a CPython developer, but the last points of the points on the desired list[0] seems very unfeasible to me. Not even STM solves the "Speed" requirement, but PyPy gives away with native extensions so it's halfway there!

[0] http://wiki.python.org/moin/GlobalInterpreterLock


I voted for displaying comment points, but I do agree that they might create something of an echo chamber where the "highest rated" comment is the one that decided where the topic is going. If this _was_ the case prior to removing comment points another solution is necessary, but more information would be appreciated.


Added "Java Portlet" to specify, thanks for the heads up.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: