soc88

7 ms·

1.
by soc88 14y ago
> People coming from other programming languages that are extremely talented in that language PHP wouldn't be this worse if this was what would actually be happening, because these people would assess the situation and take away the con
2.
by soc88 14y ago
> $foo will grow stronger than ever. -- Democratic People's Republic of Korea Yeah, sure.
3.
by soc88 14y ago
> there are many self-described experts in PHP I think this is the real problem of PHP. It attracts people too stupid to realize that their own level of knowledge should make them avoid teaching others. As soon as someone points out an
4.
by soc88 14y ago
Everybody should have basic programming skills, just like math, writing, etc. That doesn't mean we have to be happy with the shitty way things are currently done.
5.
by soc88 14y ago
Smoking isn't just a profession, it's an everyday skill that everyone should learn, regardless of how badly. A cigarette is a great enabler for this - and I endorse this direction completely. -- Your friendly tobacco associa
6.
by soc88 14y ago
The question is why they don't move on to a working language, knowing that the PHP team will _never_ fix all these bugs. It is like those people who keep penny-stocks they bought years ago for a lot of money, trying not to realize that thei
7.
by soc88 14y ago
> The core of the PHP community is filled with a lot of really talented and smart developers doing some really amazing things. Like those, who failed for years to actually consult the results of the test suite before shipping a new rele
8.
by soc88 14y ago
Yes, the daemon. The actual interpreter is still thrown away every few requests, because it is leaking memory like hell.
9.
by soc88 14y ago
I hate this apologist bullshit. Yes, we know that there are a lot of PHP sites on the net, we aren't retarded. If PHP wouldn't be such a wide-spread problem, people wouldn't have to spend so much time fighting against it. One positive thing
10.
by soc88 14y ago
Weren't there quite some different templating choices (including Groovy) available from the beginning? Independently from that, the compilation times will automatically improve when they update a) their SBT version and b) their Scala versio
11.
by soc88 14y ago
It's funny how that "functional" name calling appears so convenient if it fits the own argumentation. (Not considering that Scala is foremost an object-oriented language.) Groovy is trying to play catch-up with Java currently (typing-wise)
12.
by soc88 14y ago
Ouch.
13.
by soc88 14y ago
You mean the dormant one from 2004 which was never finished? http://jcp.org/en/jsr/detail?id=241 Or the "Groovy specification" which is almost completely empty? http://groovy.codehaus.org/jsr/spec/
14.
by soc88 14y ago
This is my impression, too. I think Groovy's "static" features are a reaction to a lot of developers realizing that "statically typed" doesn't necessarily mean that the language has to be as cumbersome and verbose as Java. Imho, there is ju
15.
by soc88 14y ago
As far as I know they still lack even a language spec.
16.
by soc88 14y ago
That's exactly the issue I'm talking about: you can't “enforce” the static type, so different methods get called depending on whether you pass List foo = MyList(...) or MyList foo = MyList(...), which is acceptable for static methods, but a
17.
by soc88 14y ago
Just wanted to say thank you for this great list!
18.
by soc88 14y ago
Could you please tell me in which alternative reality you live in? :-)
19.
by soc88 14y ago
> Functional programming style tends to generate lots and lots of objects which die very young. Well, there is a lot of Scala code out there doing exactly that. HotSpot has no problems with short-lived objects in pretty much all its gar
20.
by soc88 14y ago
> I may also be missing the point but what prevents you from putting a count method on an enumerable with a default implementation which does the same? Isn't that exactly what we're talking about? The huge difference between C#'s extens
21.
by soc88 14y ago
Works without problems in Scala. Maybe Clojure isn't using the available resources efficiently enough?
22.
by soc88 14y ago
> The original vision behind OOP wasn't at odds with functional programming. This! Imho, Scala shows very well that OOP and FP can be unified without much problems, if enough care is taken.
23.
by soc88 14y ago
You're missing the point. The problem is that as an author you have to implement an interface which is probably completely unrelated to what your class is doing, otherwise you get punished by bad performance. Scala solves this problem nicel
24.
by soc88 14y ago
Seeing how Java tries to play catch up currently, this reads down-right bizarre. :-)
25.
by soc88 14y ago
“Patching up” would suggest that they actually improved the situation. If you had read the diff you would realize they did not.
26.
by soc88 14y ago
Lots of companies missing there. I hope this stuff gets updated when the new site is up.
27.
by soc88 14y ago
This also amazes me too. The US has neither a working, efficient health care nor education system, but blames others for "socialism"?
28.
by soc88 14y ago
I thought the mods alone do that pretty well already?
29.
by soc88 14y ago
So what? It isn't better in the US, it's just more acceptable to you.
30.
by soc88 14y ago
Isn't this exactly what the article said? > I escaped from poverty because I am significantly above the average intelligence level and I managed to make the right decision at the right time. LOL. Dunning-Kruger comes to mind.

More ›