Barnyard Protein posted:

i get mad now when i have to use a for loop.

fart simpson posted:

severe stackholm syndrome

fart simpson posted:

Python code:

big_butts = []
for butt in butts:
    if butt.is_bug():
        big_butts.append(butt)

is only more clear than

Python code:

big_butts = butts.filter(is_big)

if you have severe stackholm syndrome, and it's not because it only takes up one line

leper khan posted:

big_butts = [butt for butt in butts where butt.is_big()]

LeftistMuslimObama posted:

we're not allowed to use linq expressions in our c# code and no one can give me a good reason why. it's so annoying.

Bloody posted:

you work for a company that uses mumps.

fart simpson posted:

Python code:

big_butts = []
for butt in butts:
    if butt.is_bug():
        big_butts.append(butt)

is only more clear than

Python code:

big_butts = butts.filter(is_big)

if you have severe stackholm syndrome, and it's not because it only takes up one line

leper khan posted:

big_butts = [butt for butt in butts where butt.is_big()]

HappyHippo posted:

this is a weird example because the second one is clearly better?

fart simpson posted:

that makes it normal and not weird

HappyHippo posted:

but which is more ~pythonic~?

leper khan posted:

big_butts = [butt for butt in butts where butt.is_big()]

fart simpson posted:

list comprehensions are ok when theyre small but they get more confusing more fast. consider

code:

[c.upper() for string in strings for c in string]

vs a language with something like linq methods

code:

strings.flatten().map(lambda c: c.upper())

HappyHippo posted:

but which is more ~pythonic~?

fart simpson posted:

Python code:

big_butts = []
for butt in butts:
    if butt.is_bug():
        big_butts.append(butt)

is only more clear than

Python code:

big_butts = butts.filter(is_big)

if you have severe stackholm syndrome, and it's not because it only takes up one line

FamDav posted:

don't use java hth

Share Bear posted:

canonically bad example http://docs.spring.io/spring-framework/docs/2.5.x/api/org/springframework/aop/framework/AbstractSingletonProxyFactoryBean.html

i still dont get why java and java projects are this way

FamDav posted:

don't use spring hth

Share Bear posted:

canonically bad example http://docs.spring.io/spring-framework/docs/2.5.x/api/org/springframework/aop/framework/AbstractSingletonProxyFactoryBean.html

i still dont get why java and java projects are this way

Shaggar posted:

in spring you have proxies which are interface implementations that are not real implementations, but are instead "proxies" that forward the method calls to the interface on to something that actually handles the implementation. a good example is using CXF soap clients. you specify that a bean is a cxf client and give it the interface and endpoint information and behind the scenes cxf builds a proxy that acts like the interface specified, but behind the scenes sends the requests off to a remote webservice.

one way to generate proxies is using a factory. If implementing your own factory, you would put it into the DI container as a bean.

sometimes the generated proxies are singletons

AbstractSingletonProxyFactoryBean is a base class that handles some of the common tasks related to implementation of a factory bean that generates singleton proxies.

If you don't do actual irl software development this will be confusing because its not your math homework. If you actually do software development then it makes total sense but you probably will never use it ever yourself because its mostly for use by spring and frameworks built upon spring.

fleshweasel posted:

drat there's even a bug in the loop version of the code. just proves the point more.

Soricidus posted:

the filter version of the code meanwhile isn't python at all, which doesn't prove anything except maybe that it's easy to make things look nice when you don't have to care about real syntax

conversely, here's an actual example of the kind of thing i was talking about :

JavaScript code:

butts.filter(butt => butt.isBig()).forEach(butt => butt.insertProbe())

is not, in my opinion, an improvement on

JavaScript code:

for (let butt of butts) {
    if (butt.isBig()) {
        butt.insertProbe()
    }
}

Bloody posted:

your opinion is wrong

Soricidus posted:

you make a compelling argument but i think i'm going to have to stand firm on this issue

Share Bear posted:

only work on brand new projects in languages/frameworks of the week, forever, never stopping to maintain

Soricidus posted:

Shaggar posted:

in spring you have proxies which are interface implementations that are not real implementations, but are instead "proxies" that forward the method calls to the interface on to something that actually handles the implementation. a good example is using CXF soap clients. you specify that a bean is a cxf client and give it the interface and endpoint information and behind the scenes cxf builds a proxy that acts like the interface specified, but behind the scenes sends the requests off to a remote webservice.

Shaggar posted:

i don't like .forEach

gonadic io posted:

yeah but

JavaScript code:

butts.filter(butt => butt.isBig())
     .forEach(butt => butt.insertProbe())

is better than either of those