The "moderators on StackExchange" shot was good, but I really take offense to the "PyCon 2013" one. The reason stuff went wrong at that conference was because of the actions of one attendee, who specifically did not go through the process the conference organizers set up for dealing with reports of harassment.
Ah, the wonders of low-level assembly programming. I was a teaching assistant for an assembly course this semester at school, and one of the students was running a program in the debugger. (Specifically, Microsoft CodeView running in DOSBox.) F10, F10, F10, until she got to the load instruction that would fill the cx register. Press F10 again, and suddenly, the debugger shows "cx = DEAD."
She freaks out a bit, I freak out a lot. We're both worried that something really bad happened, then I realized that DEAD is actually a number in hex. I look through the data segment, and I see a AD DE in there (yay Intel byte reversal!).
I check through the code a bit, and even though it looks like the data segment is being initialized properly, it's still reading from the Program Segment Prefix. So, I find the Wikipedia article on the PSP and see that address 05h in the PSP has a cross-segment jump to CP/M compatibility code.
But, there's nothing at address DEAD (at least, nothing sensible). So I go searching through the DOSBox code for that string, and I find these lines:
// far call to interrupt 0x21 - faked for bill & ted
// lets hope nobody really uses this address
sSave(sPSP,cpm_entry,RealMake(0xDEAD,0xFFFF));
As it turns out, because DOSBox doesn't implement CP/M compatibility, they simply made it jump to DEAD instead, just to make sure that if anyone tried running a CP/M program they would get the picture. And the assembler just happened to put the variable in the right place that the load pulled the DEAD instead of random nonsense.
I can only imagine the problems that can manifest when you're dealing directly with hardware, and don't have access to commented source code.
> On the one hand, it seems ridiculous (absurd, perhaps) to fire someone over a pronoun -- but to characterize it that way would be a gross oversimplification: it's not the use of the gendered pronoun that's at issue (that's just sloppy), but rather the insistence that pronouns should in fact be gendered. To me, that insistence can only come from one place: that gender—specifically, masculinity—is inextricably linked to software, and that's not an attitude that Joyent tolerates.
They're not opposing the use of the word "he," they're opposing him saying "no, go away, I don't see any reason someone could take offense" when the issue was pointed out instead of "thanks for the patch."
He didn't quote Strunk & White to justify rejecting the patch, nor did he bring up the grammatical argument at all when reverting it. He just said "this is not worth spending time on" and closed the ticket. (And if it was truly not worth spending time on, he wouldn't have contramanded one of his fellow maintainers to revert the patch, then rewrite the repository's history to cover himself.)
I use Symfony at work. I would love to contribute some of the patches and helpers I have written to Symfony, or release them as an independent bundle, but (a) I'm the only programmer on the project so I don't really have time, and (b) my company doesn't really do OSS, so I would need to explain all this to our legal department before I could get authorization to release it.
This looks like a fairly well-designed format. My main concern is that this seems to have suddenly appeared out of nowhere and gone directly to RFC. (Presumably there was an Internet-Draft, but I have never seen anything about this before.)
It would be up to the parser to implement the standard without a vulnerability, but a protocol is a language and a language can be designed to be self-referential, hypocritical, inconstant etc, making a conforming parser impossible. A lot of these so called "living standards" are probably not "evolving" so much as partially classified.
Here's a point that gets forgotten in a lot of discussions of this issue:
> We’re also underlining that our events are for over-18s, maybe even over-21s, by holding them in licensed premises. Most of us know students or even those who are working professionally in our field long before they are “adult.” Should they be excluded?
Depends.
Many conference I attended are professional, expensive and don't offer any alternative resources or attractions for younger participants. There are exceptions like some of the Python conferences and Maker Fairs but I doubt there would be many minors into a SQL DBA or serious embedded electronics event. Plus there is a liability issue to be considered when you mix immature adults with minors and blend in alcohol.
Under-18s can still enter licensed premises. At least here in the UK they can. And they often do, if my local that is more "5-year-old's playground" than "pub" is representative.
That's usually not the case in the US. It depends on the jurisdiction, but bars can oftentimes be fined for underage drinking if a minor is on the premises, even if he/she isn't actually drinking.
Even in situations in which the venues have discretion (eg, nightclubs, comedy clubs), venues often don't allow underage patrons to enter, because they know they're going to make no money off of them, and they're just taking up space that could instead be going to a paying customer.
Interesting, I wasn't aware that this was permitted in the UK.
Here in the US, under-18's often aren't allowed on the premises of a drinking establishment at all, so the OP does raise a point depending on the location of the conference.
Can you draw brightly colored lines on roads for a bus map? I like to mess around analyzing bus routes, but so far I haven't been able to find a computer-based tool for drawing them effectively.
I would probably draw in QuantumGIS and export as shapefile. There are many many ways to draw or otherwise generate spatial data. I think it depends on what you mean by 'effectively'?
Edit: Ok, I just re-thought your comment, and perhaps you mean to 'highlight' the existing road paths if they are also bus-routes. That would be trivial if your roads lines have attribute "bus_route". You can also add the attribute, then in QGIS you can select such paths, edit them and set the attribute as 'true', in TileMill you would then add a style to change color for lines with such attribute. Also, if the streets have names and you have a list of such streets, you can do a CartoCSS selection based on the street names attribute.
This is trivial - assign a value to an attribute for all segments that are part of a bus route, then style accordingly (preferably in a gis, the approach in the op is a cumbersome roundabout way)
Also, I just realized, if the bus routes are not in the OSM, he could use the new iD editor and add the bus routes to OSM under his account, and then export :)
I like the implementation of the "Enum" class, especially the way they allow for enums with variant behavior and "abstract Enums" (something I could have used in Java recently).
But, ever since I found out about algebraic data types from other languages, I keep wanting those. There's not quite a good way to do those in Python. (I've used both "tuple subclass" and "__slots__," but both of those have their own little quirks.)
Yes, for better of worse Python is nowadays fairly conservative in introducing backward-incompatible syntax changes, and pattern matching would probably require quite a bit of new syntax (and benefits a lot from a strong compiler).
