tiglionabbit

What is the discussion here?

I haven't played Heavy Rain but I really enjoyed Farenheit / Indigo Prophecy. Your choices had a limited effect on the structure of the movie, but the game was making constant nods to what you did, often in clever ways.

Heres an example. In the very first scene you have to flee a crime scene. You could leave the murder weapon where it is, or try to hide it. If you hide it, the game doesn't show you where you hid it. Later on, you play as the cops investigating the crime scene. If you didn't hid the weapon, it's in the same spot, but if you hid it, you'll have to look for it now. Most changes to the movie follow this structure. Demonstrating a higher level of play results in a movie with more and longer scenes, and all those extra scenes make it very clear that your actions caused them to exist in the movie.

Not to mention that it launched with a lot of missing features that existed in Gmail.

XCode also had issues working with large repos. Perhaps they were talking about that?

What you're proposing goes a step beyond multiple repos and into package versioning.

That is one viable workflow: Make a change to the common code and publish it as a new package version while allowing all existing code to continue to use the old package. Then, migrate other projects to the newer version of the dependency one by one.

Allowing multiple versions of the same code to exist in production at once adds complexity. It's a trade-off.

Also, if you're doing this with code that is ultimately webpacked to run in a web browser and you don't pay attention to the full tree of dependencies you're working with, there's a chance you end up loading two versions of the same library into a single web page, increasing the page weight and possibly causing incompatibilities in event handling.

Google prefers to simply have one master version of the entire company at a time.

I've spent a lot of time wondering which solution is the best and I'm still not sure.

Fun fact. I asked Facebook why they built their monorepo on Mercurial instead of Git. They said there were scaling issues in Git that made it unusable for large repos and the Git maintainers would not work with them to fix these issues. However, they were able to work with Mercurial to make it capable of holding their entire company in one repo.

Do you all have any idea what this is talking about? I've never heard of ICO and you're all using it as if it's some familiar and obvious thing with no explanation.

Back when I was interested in Django I'd go to Python meetups and hear people complain about how the Django project would not accept their patches. They told me that third party changes never make it into Django. That "contrib" is a lie, and that it's made almost entirely by core developers.

Ultimately I found Django to be more trouble than it's worth. I only use it if my work forces me to. I find its design to be obtuse and unpleasant in many places.

I vastly prefer Flask's documentation (http://flask.pocoo.org/docs/). It explains everything from a perspective of what your use case would be, and they've gone above and beyond in covering use cases that might otherwise have been deemed outside their scope.

A lot of these things are only common mistakes because of Django's unusual behavior.

> POST to views loses POST data

The middlewares shouldn't be redirecting POSTs then! They could have returned a client error instead.

> Blank object names

They could have provided a fallback of __class__.__name__.

> Integer & NULLS

If the admin interface knows the field is required, why does it even attempt to insert a null value? It could return a validation error.

> Appending to a list in session doesn't work

Django's behavior with ORM relationships has always disappointed me. There's no way to work with them in memory like in SQLAlchemy because they always attempt to sync out changes to the database immediately. As a result you often have to write some very strange code. They could change this.

> Errors about undefined attributes with one-char names

They could have done a type check to see if you passed a string instead of an iterable of strings.

...etc.

To me, the Django project exudes the stubbornness of the developers who maintain it because rather than fixing these problems they've decided to write this page about how it's you, the user, who is wrong.

You can upload videos to facebook though. In fact, that's the only way to get videos to play inline in peoples' timelines.

To be fair, Facebook's notifications are really annoying.

It even works if you just say `margin:auto` on the flex child

Perhaps people don't differentiate between 1-7 and 0-7 and assume that 3.5 is always going to be the midpoint?

You would throw a Nintendo Switch into the trash?

That's so wasteful. Why not give it to a friend? Or to GoodWill?

Have you considered having the courier pick up the item at your workplace?

Throwing it away would make me feel even worse. I wouldn't want it to be wasted. I'd feel better about giving it to a friend.

What he really should have done was get it delivered or picked up at his workplace so he wouldn't have to stay home waiting for the courier.

Why shouldn't your entire application be a widget? Sometimes it's nice to embed one application into another, multiple times. I find your reasoning here short-sighted, since there's often no clear point at which components should bottom out. You can always add another layer.

Angular v1 or v2 though? :P

> Glitches allow travelers to explore the universe together

So it's actually going to have multiplayer? Actually what does this even mean?

You could write down what you're thinking while you're thinking it. I usually use a google doc to organize my thoughts. It frees up active memory to get your thoughts out of your head and onto paper where you can see them and no longer fear forgetting them.

It needs to access your contact book at contacts.google.com.

Neat game. The time trial scores seem a bit strict though. I mean, I can't seem to get 3 stars on the first level of the tutorial even though it's literally just holding down a single button. Am I missing something? :P

I used that version just fine in my projects.

How does this compare to Box2DJS, the automatic conversion of the ActionScript version of Box2D?

http://box2d-js.sourceforge.net/

That's a comma splice. Original comment was more correct than this.

Falcor sort of solves this by allowing you to communicate "references" in the graph. For example, it might inform you that users.52.friends.1 is actually users.45, so the client will cache it at that location instead.

This is less complicated than GraphQL's solution of using the Relay Node interface.

Well, whatever we go with, we have to square it with the fact that fructose is worse than glucose in terms of causing diabetes.

I thought eating fat with sugar was better than eating sugar alone since the fat slowed down the absorption of the sugar, thus dampening the insulin response.

Anything goes at this point. They have no shame.