theunraveler

Ghouls.

Another case of technical debt resulting in therapy?

$50m to fix? Seems a little ridiculous…

1

> First off, this is completely false. With symfony2 the action needs to return a Response object. This annotation isn't required and the team I work with, we rarely use this.

Correct. But if you want use the form where you just return an array of variables to use inside your template, and have Symfony smartly located the template for you, you have to use an annotation. See http://stackoverflow.com/questions/12922827/symfony-2-php-te... for an example.

> and you state the same with with Doctrine2 which you point out there are other ways to do it.

Yes, there are other BETTER ways to do it. Making comment-based annotations available as one of the ways pretty much guarantees that people will use it, and that seems like a bad idea to me. Just remove them so no one is able to choose the bad practice.

> All your points for "DX Regressions" are completely wrong.

Uhh, OK? How about comment folding in text editors? Would you, as a developer, be happy if you encountered some code that made heavy use of annotations for critical application logic? I wouldn't--this is what I mean by DX.

> What do I gain to hope by using var_dump() on an annotation?

The same thing you gain by var_dump()ing any variable--an understand of what's happening under the hood.

Why is PHP OO a horrible idea?

I added an update to the article. I wasn't aware of the RFC to make annotations a language feature when I wrote the article. The article is specifically referring to annotations implemented as code comments.

Sorry for the confusion, and thanks for your comment.

At least you would know if your array contains a syntax error. With an annotation, you would have no way of knowing that aside from what the annotation parser spits out.

I am not opposed to change--in fact, I welcome it, especially with regard to PHP. Rather, I'm criticizing the use of annotations based on the argument that it is bad application design.

I don't understand how. It's a static property because it applies to all object of the class, not an individual object (i.e. an individual object shouldn't be able to change it).

And how is making the property public a bad idea? The configuration system that parses it will need to read the property, no? And a method like getUsername() should be reserved for actually getting the value of that field, not its config.

> I'll take the first one because I have other shit I need to do.

Uhh, what's so hard about making an array?

Not necessarily. Several Symfony components rely on doctrine/common simply for parsing annotations, even if you are not using Doctrine for anything else.

Wow, I didn't know about those RFCs to make annotations a part of the language. Thanks for posting.

OK, fair enough. The marketing copy and a description of "features" is still forthcoming (not my strong suit).

The idea is that you have a set of chores that need to be split up evenly. The typical use case is a household. The app will take all of the chores you define for a group and split them up evenly and randomly among the members of the group.

A new app I've been working on for groups to evenly divide chores. Good for households, shared workspaces, teams with regularly-occurring tasks, etc.

Check it out and let me know what you think!

Wow, this is wonderful! There are so few iTunes alternatives for Mac. Are you planning on open sourcing this? I would love to help develop it.

Good idea. I did one of these a while back. https://github.com/theunraveler/SequoiaApp

That all depends on what illusions you have about how the market works. I would claim that a single app developer is still subject market concerns. Oftentimes developers are hired by bigger companies to do work, and in that case there is a typical "boss/worker" relationship, wherein they retain the right to fire you for any reason, or no reason whatsoever.

In short, what I would like to see is NOT a "professional association" (like Chamber of Commerce) that advances the interests of business, but rather a union that protects the rights of working people. The union would, ideally, ally itself with other organizations of working people to not just fight for our slice of the pie, but for every worker's slice.

That's why unions are for workers, not employers :-)

I really disagree with this.

1. Lost wages are one of the reason unions maintain a "strike fund" or start collection pools.

2. An injury to one is an injury to all. A company pulling some funny business that costs developer A $1000 could very well do the same thing to developer B. It is, then, worth developer B's temporary loss of income to defend his/her interests in the long term. ALL workers lose when SOME workers decide to trade temporary gain for long-term power.

I think this would be really useful. With those companies perpetually encroaching on our privacy and the freedom of the internet, such leverage would be really good to have.

Just a few quick notes on unions in general:

1. Even though union membership and participation is covered under the NLRA, companies break the law all the time. Organizers are fired and retaliated against for union activity all the time. The fact is that the labor board (the government body that arbitrates labor disputes) is too weak and the penalties for breaking labor laws for companies too lax that it is often work the small amount of hassle for a company to break a union illegally. This has been shown in many, many union recognition struggles. Because of this, a unions power is not through the laws that "protect" it, but in the ability of its member to take action and force the company to meet demands, financially and socially.

2. Assuming the first point, we must have a discussion to determine where exactly our power can be exerted. Your idea of the "kill switch" is right on; essentially, if a company stiffs a developer, the internet as we all know it could shut down temporarily.

3. There are really bad ass unions out there that are in to organizing groups of workers that other unions deem "unorganizable". Developers, I would think, are one such group, considering our geographic and occupational spread. One such union is the IWW (iww.org). I'm a member, and would really strongly encourage affiliating with them.

4. Actually, I think solidarity with the Foxconn workers in China might be a good first campaign.

So, yeah, I really love this idea and am willing to do the work to make it happen. IRC, anyone?