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

Thanks!


This sounds like architecture astronautics. Lots of things that sound good in theory, but there's no analysis of how useful they would actually be in practice, what actual tradeoffs there are with current designs, etc. Lots of wishlist features.


Not really. This is more organized misogyny than voluntary celibacy. If you take a look at their forums, they are more concerned with criticism of women and feminism than celibacy.


> This is more organized misogyny than voluntary celibacy.

Voluntarily celibacy and, especially, voluntary complete isolation from women have often been sold by organized groups with justifications that incorporate misogyny, so "organized misogyny" and "voluntary celibacy", while distinct, aren't completely independent.

So, I don't think MGOTW is, even to the extent that it combines these things, particularly novel.


You're right, I don't think that it's particularly novel. Just that it seems the misogyny aspect of "MGOTW" is more important than the celibacy aspect.


It appears that that's the intent of using an obscure acronym like that; people can drop it casually in conversation, and then people search for it, and then someone edits the Wikipedia article to crow about how many people are searching for it.


Wow.


I think he's saying that in this document, "creat" is sometimes spelled with an "e", indicating that the OCR process overcorrected.

  3.5.2 Create
  
  To create a new file, the following call is used.
  
       filep = create(name, mode)


At some point, you have to stop considering any discussion of a movie as spoiler.

The term "spoiler" should be reserved for a reveal that actually spoils the movie; where some crucial element of the movies emotional impact can be taken away by knowing some fact in advance that is held secret through the movie.

The discussion in the first paragraph here pretty much just covers the exposition in the credits, and the material you learn very early on about one of the main characters.

I feel like treating this kind of information as a spoiler will just lead you to endless anxiety until you have seen every possible movie that could be "spoiled" for you this way. Why not just relax, accept that people are going to do some light discussion of movies, and reserve your outrage for actual spoilers of surprising plot points, mysteries solved, puzzles spoiled, and the like?


OP didn't seem outraged to me, just a bit disappointed. Which I understand, because "at some point" is still far away for the new Star Wars movie. I do think that any discussion of a movie is a spoiler. It depends, but from friends I don't even want to know if they liked a movie or not as I know them and their taste so well that I will deduce things which will influence my experience. I want my experience as pristine as possible, which is hard enough without articles mentioning tiny details about plots that they just don't need to mention for the point they are making.


When I say "at some point", I don't mean that that's the timeline for a particular movie. I mean at some point in your life, it is better to let go of the idea of walking into a movie in a completely pristine state with no expectation about what will happen in it.

Otherwise, either you have to cut yourself off from all media and conversation that might possibly reference the movie, or try and convince everyone you might interact with, and everyone who might write anything online, not to discuss the movie. Neither option seems particularly pleasant nor realistic to achieve. I suppose you could also just see every movie you intend to see on the first showing of the opening day.

What you are doing by asking for absolutely no information at all, even the basic exposition and setup of characters at the beginning of the movie, is imposing a large burden on everyone else around you to prevent a very minor inconvenience to yourself. I understand not wanting major spoilers, and that there should be a reasonable time before discussing those points openly without a spoiler warning. But it just seems that the trade-off is fairly poor for not even allowing the most basic discussion.


In that case I guess my trouble with your point of view lies not with the "at some point" phrase but rather with the generalization implied by "any discussion". That argument is almost always used against people who complain about spoilers, and sadly it's often insultingly non-understanding. I'm not saying that all discussion are spoilers. While my personal wish is to not know anything about a movie before seeing it (which I have never regretted afterwards, by the way – the opposite, having advance knowledge, has not hurt the experience always, but it has never ever improved it), I realize that this is hard to achieve and requires me to take care of that, not everyone else. As you mention, that would impose too much of a burden on everyone else.

But that does not mean there is not still a lot of stuff that really should be considered spoilers, and the complaints about these should not be brushed off just because you think I expect you to not mention anything about a movie. I think it's a very valid criticism when the article in question reveals something that even the trailers kept unknown by never showing that person, without any need for it in the context of the article. It's like saying "The Sixth Sense, where he was dead all along, was quite good, I loved the cinematography." a week after that movie was released. While I personally would not have wanted to know about the cinematographical quality either, I realize I can't complain about hearing something like that when reading a review or when I'm not fleeing a discussion of the movie quickly enough. I never would complain about that. But I'm sure I'm not the only one who would be pretty annoyed to read said plot detail in an article about e.g. "The decline of quality in M. Night Shyamalan movies" a week after that movies release.

To sum it up: I agree with your basic point, but I think too often people that are fine with spoilers don't care about the fact that other people have a different level of acceptance and when confronted with that simply resort to saying "Well, it's silly to have this level of acceptance."


>it is better to let go of the idea of walking into a movie in a completely pristine state with no expectation about what will happen in it //

I actually managed this pretty much with the new Star Wars movie - but then on the way in to find the screen was greeted with a massive poster showing lots of info about the movie. I averted my eyes. Then at the entrance there were sales staff touting character drink cups which successfully spoiled a couple of the characters who would feature heavily.

After the movie I watched a BBC program which supposedly reviewed the Star Wars franchise and promised no spoilers. Pretty much the entire plot and many of the scenes could be determined from the content they gave.

The problem I have nowadays is that trailers seem to include the entire plot, all major characters, all the best effects, all the most emotive scenes; ostensibly the entire movie in digest. These to me are very poor trailers.

Generally I agree with your points however, lambda.


I think that _the same weekend it opens_ is not in the span that most would consider "spoiler free". If the movie has been out for a month, maybe.


Take a little time off from checking HN?


But that would eat into my Reddit checking time.


If you need to leave to go to work at 8:00 AM, to get there at 8:30, it's a 5 minute drive from your office to my house, and I need to leave at 9 to get to my job at 9:30, then an on-demand driverless car can take care of both of us. It can also pick up the person who was able to take public transit in but needs to run errands on their lunch break, as well as the second shift worker, and take someone else home for dinner, and get someone else to the airport at 3 AM.

Right now, many people have cars sitting idle for a large portion of the day because they need them for an hour a day, or sometimes an hour every couple of days, or a couple of hours a week. While it's true that there are surges in demand in the normal morning and evening commutes, there is still a lot of excess driving capacity that is needed for trips other than those surges, and so you only have to have enough cars to cover those peaks.

In addition, there may be other people who could take public transit, walk, or bike to work, but don't because there are other things that they need to do at various points that require a car, and so it's more convenient to just always have it available.

So yeah, driverless cars can only get you so far, you're right that the peak demand number is pretty much the minimum number you could have. But if I go an look at my residential street during the day, when commuters are presumably at work, I still see about half of the cars present. Those are all cars that wouldn't be necessary if everyone were riding in self driving cars that could rearrange themselves based on demand. That reduction in number of cars would also reduce the amount of space needed to store all of those cars, which could help bring everything closer together making it more walkable, bikeable, or efficient for public transit, which could further reduce the demand for cars.


> While it's true that there are surges in demand in the normal morning and evening commutes, there is still a lot of excess driving capacity that is needed for trips other than those surges, and so you only have to have enough cars to cover those peaks.

Do we really have excess capacity compared to the peak demand? Put another way, how many people own a car and aren't using it at e.g. 8:50AM? At a complete guess I'd say maybe 5%?

(Also, given zoning and city layout, most houses are a lot more than 5 minutes away from most offices. Even if my commute is 8:20-8:50 and yours is 9:15-9:45, we're probably both heading into the city centre from outside, so the same car probably can't serve us both).


> Do we really have excess capacity compared to the peak demand? Put another way, how many people own a car and aren't using it at e.g. 8:50AM? At a complete guess I'd say maybe 5%?

As I said, when I look out at my residential street at 8:50, I see about half of the cars still parked there, or maybe a third (very rough estimates, I haven't actually counted). Now, I do live in a city with good public transit options, that's also fairly walkable and bikable. But at least where I live, there's a pretty serious oversupply of capacity, just because people do need cars occasionally and the options for not owning a car are not good enough.

In fact, on the next street over, parking goes way up at around this time since I'm near a major subway stop, so a lot of people park here and take the subway the rest of the way in. Rather than just sitting there, going back up and shuttling more people to the subway would be a more efficient use of cars that you could do with self driving cars. The commutes from house to subway station are likely under 30 minutes, and since rush hour generally actually lasts about two hours from 7 AM to 9 AM, you could fit a couple of round trips in that time period.

> (Also, given zoning and city layout, most houses are a lot more than 5 minutes away from most offices. Even if my commute is 8:20-8:50 and yours is 9:15-9:45, we're probably both heading into the city centre from outside, so the same car probably can't serve us both).

This is increasingly untrue. Mixed use developments, companies moving out to the suburbs for cheaper real estate, people moving back in to the city, and so on mean that reverse commutes are increasingly common.


> Even if my commute is 8:20-8:50 and yours is 9:15-9:45, we're probably both heading into the city centre from outside, so the same car probably can't serve us both).

If you are willing to share the ride, you can have the same car serve you and someone else who shares a similar route and is willing to travel 10 minutes early (or late - can be incentivize by a discount).

Self-driving cars can make car-pooling easier - it can be a hyperlocal public transport system. Pick up 4 people who are traveling from/to within a 2-mile radius with each other, and peak traffic will be 25% of what it is now (best case). It's even simpler considering that most people commute the same route everyday.


> If you are willing to share the ride, you can have the same car serve you and someone else who shares a similar route and is willing to travel 10 minutes early (or late - can be incentivize by a discount).

What does the self-driving car change in that case? Wouldn't that be just the same as ordinary carpooling that we can do today?


Right now, I need to manually find someone who is carpooling. If there happens to be someone on my street that I know and is going to roughly the same place, that's fine. However, there are many trips which have overlapping segments that I'd never be able to find without an automated system.

For carpooling with my own car, that's really too much work to try and hunt down someone, figure out how cost sharing is going to work, ensure that our schedules are in sync often enough for it to work out, and so on.

With an automated system, it can just adapt to changing demands. Maybe some days schedules are too far out of sync, so it just sends dedicated cars. Maybe some days there's someone better to pool with.

You can already do this with systems like UberPool, but with self driving cars, you don't have to pay a dedicated driver, so it becomes even cheaper and more convenient.


* More flexibility: currently a driver has to be first in, last out

* ability to add more vehicles on demand

* automation


It is unfortunate, and it is a good question to ask why Rust is attracting so few female contributors.

To assume when asking that question that the project is misogynist is a bit of a stretch, however. It's worth checking the project's policies and behaviors, to make sure it isn't doing anything that provides some kind of bias, but simply starting out by claiming that Rust is "anti-female" goes a bit far.

A few things that I can think of off the top of my head:

Some of the prominent contributions from women don't show up in the list of contributors because they are not directly to the compiler and standard library which are what are tracked in this contributor list, but rather to the broader ecosystem. Julia Evans has written some good blog posts on writing an OS in Rust, that have inspired other people in this space: http://jvns.ca/blog/2014/03/12/the-rust-os-story/. Emily Dunham does some excellent work on Rust infrastructure: http://edunham.net/2015/05/20/open_infrastructure.html There are of course many more that I'm not listing here, but the point is that the Rust community, and even the upstream project, consist of more than just the compiler and standard library, though those contributors are the ones that get credited in a release since that is what is being released.

Rust is still a nascent language; while it is starting to gain traction in the industry, it is not yet broadly adopted, and thus investing a lot of time and energy in joining the project is still a bit of a risk. People who have more social capital and more free time can afford to spend more of that on projects like Rust with a lot of potential but a higher amount of risk. Unfortunately, in our society men tend to have both more social capital, and more free time as domestic labor and child rearing is still seen as primarily women's work.

There are probably a large number of other factors at play. The Rust community that I have seen has been very supportive of women contributing, and has been doing a better job recently of outreach, but there is still probably more that can be done.

Can you provide any suggestions; any place you see the project structure, or contributors, being "anti-female", or any positive action that could be done to increase outreach or increase participation?


What benefit would Docker images have over the existing upstream distribution or distro packaging? The Rust compiler doesn't have any particularly complicated dependencies, either installing the binaries directly from rust-lang.org or installing packages from your distro (if your distro has packages yet) should work fine.

Container images are great for daemons with possibly complicated dependency sets that might have conflicting version requirements with other packages and can benefit from isolation from other packages that containerization gives, but seem like a pretty heavyweight solution for just installing a compiler.


A few reasons:

- It is common for languages to have official Docker images (Java, Ruby, Python, Go, Erlang, Haskell, Julia, etc)

- In August the install process didn't work on my Debian system, eventually got guidance for workarounds from IRC

- Our build farm is docker based, application deployment environment is docker based

- Ensures development environments are identical

- Solves the multiple compiler issue

As much as I use Docker, it'd be tough for me to call it heavyweight. In terms of resource consumption Docker is just a neat wrapper over some functionality that is built in to the kernel, there is no "vm" of any sort, which is a common misconception.


One benefit: one could install latest version of Rust on any distribution. Debian stable for instance usually lags behind (with good reason, but still...). I imagine it is mostly useful for checking out Rust though, not for normal use.


The installer from https://www.rust-lang.org works fine on Debian stable. Right now, you can just use the upstream rustup.sh script for platforms that don't yet have it packaged (like Debian stable), or install from your distro for those that do (or use rustup.sh on those as well if you like).

What I'm not seeing is the value of a Docker image. Rust doesn't have much in the way of runtime dependencies, which is where the value of a container generally comes in. I don't know of a platform where Docker image would work but rustup.sh would not.


I'd attribute it to IMO bad devops habits encouraged by Docker. It's too easy in Docker to depend on someone's unofficial image ("FROM rustxyz" vs. "FROM debian + download deps + install rust"). Having official images would at least reduce the number of people building their infrastructure on unverified/unofficial images.


So you think running some script on my machine is preferable to running a container? If I don't like having Rust around, with containers I can just remove it. With script - yeah, maybe, with some digging for correct parameters and assuming it cleans up after itself properly (which is far from trivial).

Packages are of course preferable if available and up-to-date.


rustup.sh has an --uninstall flag that should remove everything cleanly.


Should. It wouldn't be the first script to have a bug.


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

Search: