HNHacker News
TopNewBestAskShowJobs

figglesonrails

171 karma · joined January 12, 2012

submissionscomments
figglesonrails··on We were wrong
All I can say is... +1

This is exactly what I was thinking, but unable to verbalize it so well.

figglesonrails··on We were wrong
This advice leads to sexual assault? Come on. Yeah, in the strictest sense, you do not have a legal right to her bubble of space and she can charge you for sexual assault for leaning in for a kiss.

OR, she can be a normal, non-litigious person and reject you. She can say "no", turn her head, take a step back, etc. and you know what, she won't be worse for the wear, mentally or physically. I promise!

I mean, at that rate, a girl could indicate that she wants you to rub her off, but charge you for sexual assault because Simon Didn't Say Touch My Breasts. Good god, please let this never happen to anyone.

Please, stop spreading advice that any and all action must be done with full and explicit consent. American society doesn't value that. Watch romance movies sometime. This is what girls grow up with. This is how many girls wish to be treated. They know how to operate in those scenarios. They understand the roles of each and have predefined expectations long before you meet them. They want their lives to play out like the most romantic scenes from their favorite movies. They want spontaneous adventure. They want unexpected trips and kisses in the rain. They want to stare in your eyes and for you to lean in. Defy these norms at your own risk.

I mean, fundamentally, what you are saying is just that: go against cultural norms because it's better for the girl that way. Says who? You? Her? "Society"? Feminists? Movies? I, for one, do not buy this line of thinking.

In the beginning, I expect relationships with people who aren't too sure about each other might well be represented by a series of try { } catch { } and throw CourtshipAdvanceNotAcceptedExceptions. Fine, this is par for the course. This is quite a bit different from throwing a lawsuit.

The people you should worry about are the ones who after rejection occurs, grab their victim and proceed to force their actions anyways.

figglesonrails··on NOW HEAR THIS: NAVY ABANDONS ALL CAPS
It's fascinating to me that we have psychological effects of seeing all caps. Compare to a language like Arabic which doesn't have the concept of upper/lowercase letters. I wonder what linguistic effects they have that are specific to their language...
figglesonrails··on Apple Rejects App That Tracks U.S. Drone Strikes
+1 for stolen debit card. Aside from fraud liability agreements, in the absence of them, it creates an upper bound on the damage that can be dealt.
figglesonrails··on Apple Rejects App That Tracks U.S. Drone Strikes
Credit cards are a short-term loan which doesn't require approval for every stupid minutiae. Ever signed a loan? Takes a bit of setup. Imagine doing that while paying for fast food. Pain in the ass. Take it for what it was meant to be: a loan system. Saying "credit cards exist is a problem" is like saying the concept of loaning money is bad, which I will handily point you to for-profit startups and non-profits that all either make or use loans to bring about positive change.
figglesonrails··on John Carmack discusses the art and science of software engineering
This is Java code. If you test for a null reference AND THEN dereference it, you get a NullPointerException. The check was supposed to be "!= null".

This check is obviously erroneous, and found via SCA. I was saying "if I had a dollar for every time I found this [via SCA] I'd have a lot of money."

figglesonrails··on John Carmack discusses the art and science of software engineering
If I had a dollar for every time I saw this...

if(obj == null && obj.isValid())

I'd have approximately 960 dollars per project.

figglesonrails··on John Carmack discusses the art and science of software engineering
Actually, I think one of his strongest points is about making mistakes -- everyone does them and everyone makes the most amateur of them. If you haven't tried running SCA on your code, try it sometime. I've got a ridiculous ego, but when you get hundreds of warnings on your code, you realize just how imperfect you can be and how impossible it is to be cognizant of all things at all times. This is why teams are almost always better, and I'd prefer to review and be reviewed by someone else -- I'm my own biggest blind spot.
figglesonrails··on Gunsmith Uses 3D Printer To Make A Rifle
And for those who say "bah hard to get illegal guns", replace the word "guns" with "drugs" and tell me how hard those are to get.
figglesonrails··on Gunsmith Uses 3D Printer To Make A Rifle
What part of "HOMICIDAL MANIAC" do you not understand? Do you think he'll only kill the family and anyone else who gets in his way ONLY if he has a gun? I don't think this is how homicidal maniacs work.
figglesonrails··on After the age of scarcity
Meh. If I can print a spatula or buy one for $1 at Wal-Mart, I could care less. Printing will work for some stuff, but consider a) materials used to print still aren't any more plentiful just because you can shape them and b) expensive, hetereogenous, multipart things can't be printed, e.g. a complete car (engine, chairs, windshield, seatbelts, etc.) 3D printing looks like it makes cheap items cheaper. So, what, we put a few businesses out and free up some of China's workforce?
figglesonrails··on After the age of scarcity
Yep, and time and time again has shown people pay for sooner. I really think people who assume "scarcity" is the only factor in economic models aren't seeing the whole picture. Exclusivity of group membership (I have a t-shirt, jacket, etc. with this awesome logo I can advertise my social status/beliefs), being "first" in a social group, and just plain impatience or apathy contribute greatly. If everyone was purely rational, I'm pretty sure we'll all use refillable water bottles, personal water filters, and buy food in bulk. Assuming the motivations behind every actor in the economy are purely rational is utterly naive.
figglesonrails··on The security hole in sudo
Since the context is "C" not "C compilers", then I'd say C could have a less dangerous switch statement by requiring break/continue to indicate this. Agreed. Why people don't document/annotate for static analysis intentional fallthroughs is beyond me. OK, so we can eliminate one type of bug if we make that change (assuming we fixed all legacy code) -- what about the other legitimate uses of potentially suspect constructs?

Compiler writers can do whatever the heck they want, and if dumping ALL THE WARNINGS was the priority, you'd need three lines of command line switches to turn off the "noise" warnings. Clearly, the a bunch of people see it as "noise" or don't care about writing clean code. That's more systemic of programmers.

figglesonrails··on The security hole in sudo
Truthfully, C does what you tell it to do. As it turns out, most people don't want it to do what they tell it to do, they want it to do what is in their head. Those warnings are "did you really mean what you just told me to do?". For some people, the answer is "no, what, wait!" -- those are what they are for. Not that the behavior is insane, just "less common". I don't think people fully grasp the idea that C does what you tell it to do when they first start using it.

If you told C "make me a sandwich", it'd give a warning about not having enough mustard to cover your entire body and an error about not have a large enough bun type to fit you in.

figglesonrails··on The security hole in sudo
Most projects don't need C, I'll agree. But I have a hard time seeing how a language that is on a 1:1 to 1:5 statement-to-machine-instruction language will be displaced by a language that is safer while being at least as efficient and at least as expressive. If you say "but I don't need a 1:1 to 1:5 ratio..." THEN YOU'RE DOING IT WRONG.

C isn't broken. Gah. Why does everyone have such a hard time understanding that? The language does //exactly what you tell it to do//. If that's overrun a buffer, then that's what you get. If it is fallthrough a switch statement, that's what you get. If it is typecast a block of memory that is too small to hold the structure, then that's what you get. In short, for many programs, that means doing stupid things at some time. For many programs, edge cases aren't considered at all. Blame C? It let me?

For every single one of the "warts" of C, there is also a usecase. This is why it will not be "fixed" and why it isn't "flawed". To remove them is to remove a useful function that could otherwise cause more machine code to be needed. THIS IS THE KEY. Minimizing machine code (overhead).

If you aren't good at managing these edge cases, don't need native code, don't need interop with other code, can take a performance hit, or don't want to use automated tools to help you, then don't use C for large programs.

Take it for what it is: a low level, mostly portable, mask over assembly. Stop complaining about C, start complaining about programmers.

figglesonrails··on Richard Stallman Collapses At Barcelona Conference
Legally, minors are considered "incompetent", the idea being that they wouldn't know if something would be harmful to them in the long run. Additionally, the level of wisdom/intelligence is just too different -- children are extremely easy to manipulate compared to adults, especially since adults are almost unanimously regarded as "authority figures", doubly so if a family member. Voluntary means little if you can't reason at the level of an adult. I don't think we can honestly say that a 7 - 10 year old child has the same reasoning and experience to make good choices.
figglesonrails··on Richard Stallman Collapses At Barcelona Conference
He's not advocating...

The question (which is unethical to research) is "does voluntary pedophilia harm children?"

In all honestly, the answer is "probably most of the time". Right now, we can't say with absolute certainty that the answer is "probably most of the time". However, the cost of finding out the answer is via a controlled experiment too great, and given the ethics of science today, it definitely shouldn't be researched. We have a lot of reason to believe that children aren't mature enough to handle the consequences, and there are very common negative consequences associated with pedophilia that have been noted for decades. This evidence strongly points to the idea that it is bad, but it isn't proof any more than an apple falling is proof of gravity (it's a case for, but not a proof of). Our society saying "it's bad" isn't proof either.

What Stallman is writing is that he is skeptical of the claim that it is bad. That is a belief, and as already mentioned, testing it would be incredibly unethical. That doesn't make you a bad person for saying that without proof, you refuse to accept a claim.

While what he says may seem heretical, to burn him as a heretic is wrong. Until he says "we should test this" or "I support this group and/or changes of current laws", he hasn't suggested anything that would endanger/harm anyone. The proper response isn't "HERETIC", it is facts that we do know that suggest that this belief is likely (even if not proven in a formal study to be) wrong. For example, bed wetting, PTSD, sexual repression, hypersexualized behavior, extreme depression are symptoms experienced later in life. I don't know what the voluntary/involuntary ratio is, but this suggests that there are serious psychological consequences. Experts in the field would know more. The point being that in an open society, we discuss and counter, not silence and shut down.

Many people believe P = NP despite the years of no solution and a general consensus that researching a polynomial time algorithm is a waste of time. We don't have a proof that P =/= NP, so we can't counter, so we can't counter those who believe it, even if we regard their beliefs to be misinformed or likely to be wrong.

figglesonrails··on Why should I have written ZeroMQ in C, not C++
Yes, it does, for the same reason that C++ code that is compiled with a C compiler can be called C.
figglesonrails··on Why should I have written ZeroMQ in C, not C++
"Though we probably learned this is not the way to use them, I have seen numerous real-world examples where this was the case."

Ah, Java code at my workplace.

   catch(Exception e) {}
figglesonrails··on Why should I have written ZeroMQ in C, not C++
Exceptions indicate //exceptional conditions//, i.e. conditions other than the intended state transitions of the program. They aren't a guard against crashing, they are a mechanism for formalizing error states in the program.

Memory corruption? Appropriate response: fail. Logic error? Appropriate response: fail. Exception? Appropriate response? Decide if program can continue, respond.

I'd say the bigger issue is less of "exceptions" so much as "states". Adding any kind of error handling increases the number of state conditions that your program may be in, and that complexity is obscenely hard to manage. I don't think C or C++ or Java or Erlang or any other language will free you from the burden of proper software engineering.

figglesonrails··on If You Have A Smartphone, Anyone Can Now Track Your Every Move
If privacy is gone, then email me my shoe size, favorite pizza, and a picture of my fish. (hint: I don't have a fish)
figglesonrails··on Why I Am Creating TCombinator
Well, if we're going to be technical, you don't alter sexuality (mindset) with surgery, you alter sexual organs. And that wasn't so much a change in sexuality as a change in ability to reproduce. :X Also, "surgery in a nature" seems like a bit hard a precedent for.
figglesonrails··on Why I Am Creating TCombinator
This isn't really addressing the issue of "Is this a good idea to create TCombinator?", it's just a personal statement. Agreeing or disagreeing with this still makes it OT.
figglesonrails··on Why I Am Creating TCombinator
Yeah, going to have to agree here. Right now, you seem focused on accentuating the differences between "us" and "them" in an area where it doesn't matter at all. You should be pushing towards an ideal world where things like LGBT pride parades aren't necessary because the differences are inconsequential.

EDIT: It isn't to say there is exists no discrimination, but if you're running an e-business, the question of sexuality or gender identity does not come into play whatsoever, nor should it ever. I'm not sure how someone would be able to find out either of these to even discriminate against you unless you took the time to specifically advertise them. How you choose to invest the money you make as a business person (e.g. help other transfolk) is purely a personal concern.

figglesonrails··on Bye Bye SVN, Hello Git
I use SVN at home and in a 9-5. It's works fine.

1) Fast enough? I have tried git. It's pretty cool, but the difference between 5 seconds and 1 second is minimal at best to me. I don't think I've found myself dying for a faster SCM, though I usually make maybe 1 - 5 commits per day. Git on Win32 is meh compared to git on Linux, so that doesn't really convince me any further either. Git is also a PITA to compile on !Linux using !gcc, because heaven forbid we write using ANSI/ISO C.

2) Yes? I can do renames, but strictly speaking it is not an atomic "rename" operation. I don't particularly care about rename history, and I'm not really sure why others do, but I guess if I tried I could make up a use-case for it. Still, it wouldn't be a selling feature for me, that's for sure.

It seems strange to me that you take the time to tell us that "git is better", like we're comparing O(n) to O(log(n)) algorithms. Different workflows, projects, and organization structures have different needs. It seems hopelessly naive to simply assume everyone's needs are best fit by git, and git alone.

How about this: I want to tell, given two revision numbers in the mainline branch, which came first? In SVN, it's pretty simple. In git? Well, first open a terminal...then ...argh. As release manager, it's kind of annoying. Simple use case: is 2aa8aca05357004d4418807c06f53d81517bc629 before or after e8d0555ce401b6acb0f225aa0263e9b72136347d? Did e8d0555ce401b6acb0f225aa0263e9b72136347d make it into the build given that 5b5c73ceaa442bafff08b4470aad3ff276be94e3 was the final commit before the cut-off?

I might waste 5 seconds opening a terminal window or tab, 30 seconds finding, copying, and pasting the revision numbers, then a second or two determining the answer. This, to me, is not a productive use of my time when revision numbers simply tell me what I need to know. All of that magical time git just saved me might have just been absorbed or gone into time debt.

figglesonrails··on The byte order fallacy
This isn't surprising. If the set the AC bit on x86, then it will disallow unaligned accesses and you'll be operating in an environment more similar to RISC machines. In order to allow such a thing to succeed, GCC can't produce a 32-bit read from char* address since the alignment is only guaranteed to be 1 (i.e. no alignment) and this would trigger SIGBUS. Thus, in order to get a 32-bit read, you must deref a 32-bit variable, not 4x 8-bit ones. This makes even more sense on RISC systems where this "optimization" would be a tragic bug you'd want to work around in your compiler. See my post with the x86 assembly output confirming your general results.
figglesonrails··on The byte order fallacy
===============

#include <stdint.h>

uint32_t load_uint32_be(uint8_t* p) { return (p[0] << 24) | (p[1] << 16) | (p[2] << 8) | p[3]; }

uint32_t load_uint32_le(uint8_t* p) { return (p[3] << 24) | (p[2] << 16) | (p[1] << 8) | p[0]; }

===============

gcc -O3 -fomit-frame-pointer -S bo.c

===============

load_uint32_be: movl 4(%esp), %edx

        movzbl  (%edx), %eax

        movzbl  1(%edx), %ecx

        sall    $24, %eax

        sall    $16, %ecx

        orl     %ecx, %eax

        movzbl  3(%edx), %ecx

        movzbl  2(%edx), %edx

        orl     %ecx, %eax

        sall    $8, %edx

        orl     %edx, %eax

        ret
load_uint32_le: movl 4(%esp), %edx

        movzbl  3(%edx), %eax

        movzbl  2(%edx), %ecx

        sall    $24, %eax

        sall    $16, %ecx

        orl     %ecx, %eax

        movzbl  (%edx), %ecx

        movzbl  1(%edx), %edx

        orl     %ecx, %eax

        sall    $8, %edx

        orl     %edx, %eax

        ret
GCC doesn't merge the 4 byte-level reads into one 32-bit read. Thus, it does cause some performance penalty. The true impact is probably quite low, but it does exist on x86.

It is true however, that GCC will take a series of bit ops and produce a 'bswap' instruction on x86, but that requires a full 32-bit word to start with.

figglesonrails··on The x86 PlayStation 4 could signal a sea-change in the console industry
The graphics API is more important for what? Gameplay? AI? Load times? Physics? Or did you mean rendering triangles, because indeed graphics APIs are very important for that.

I think it is extremely naive to assume that the CPU's underlying architecture and microarchitecture are utterly mundane details abstracted by the C++ compiler, ESPECIALLY in the case of consoles. Consoles are underpowered by today's standards, and making today's game run on them requires a deft maximization of both the GPU and CPU, not a mindset like "well C++ will take care of the CPU stuff". In case you hadn't figured it out, common C/C++ stuff from Havoc Physics to little old memcpy() and strcmp() are all hand-optimized for their platforms -- sometimes multiple implementations that make use of various ISA extensions. Try stepping through them in a debugger sometime.

figglesonrails··on The x86 PlayStation 4 could signal a sea-change in the console industry
Surely, /surely/ this is the least of their concerns. Since when did we get so sloppy as to assume byte ordering in files? When was the last time your PNG loader failed on x86 because the file has big-endian fields?
figglesonrails··on The Go Programming Language, or: Why all C-like languages except one suck.
I guess you never worked on boost.
← PreviousPage 3 of 4Next →