soc88

19 ms·

151.
by soc88 15y ago
After people finally figured out that he was leaving (almost no one knew of that) they offered to take over the complete responsibility, what happens? Suddenly he wants to keep the domain, forcing everyone to pull and update their documenta
152.
by soc88 15y ago
That's exactly what I'm trying to say. He is leaving his Lift community to do something new and doesn't intend to do the hosting work anymore. That's completely acceptable. What makes me confused is his determination to prevent anyone else
153.
by soc88 15y ago
I have no idea what your problem is, but feel free to completely ignore what I have written and write down your ramblings instead. The net is big enough for everybody, right?
154.
by soc88 15y ago
I never used his pool. I just think that his behavior is intended to maximize the potential damage to everyone, he is well aware of that and does it on purpose, because someone hurt his feelings. In my opinion there are other, more construc
155.
by soc88 15y ago
Then maybe you should actually read the text. Apart from that, registering multiple common scala-* domains and then making them point to his blog instead of something actually related to the topic is pretty much the definition of domain gra
156.
by soc88 15y ago
So you would expect to be totally within your rights if you would register windows-tools.com/net, ipod-library.com/net and use these sites to damage the reputation of the mentioned product?
157.
by soc88 15y ago
Sorry. I think we should try having a constructive debate again, that was lost a bit it seems.
158.
by soc88 15y ago
The EPFL owns it, especially the logo he is also using. And no, registering is not always a requirement.
159.
by soc88 15y ago
You are still missing it completely.
160.
by soc88 15y ago
No, not really. It was about maintenance work.
161.
by soc88 15y ago
Maybe someone should try to explain to you the concept of a "trademark".
162.
by soc88 15y ago
This comparison is just deeply flawed. Point is, he can do whatever he wants, but his actions are solely designed to make the live of everyone else a bit harder, just for the sake of it.
163.
by soc88 15y ago
As far as I have seen until now the community feels different. >> And maybe I missed it, but I didn't see anywhere he threatened to "use the site for damaging >> the reputation of the Scala community as a whole". > My wa
164.
by soc88 15y ago
While I think he has all rights to feel insulted by an individual, I think holding the whole community responsible for that individual and threatening to use the site for damaging the reputation of the Scala community as a whole is a bit to
165.
by soc88 15y ago
> - There's no way to do array access without null pointer and index checks each and every time. That's not happening anymore for years already.
166.
by soc88 15y ago
I wonder in which part of the world you are living. OSM has in most parts of the world outpaced even the best, commercial map providers...
167.
by soc88 15y ago
The issue the author mentioned has already been solved in a much more easy and efficient way, without trying to use every feature of the type system. Now the question remains: Should a language make almost-impossible and dangerous tasks eas
168.
by soc88 15y ago
4. A simple compiler that sometimes requires a type annotation. > Those are your only options. Reasonable people can disagree over which is preferable. Ah ok. Being right seems to be more important to you than having a honest discussion
169.
by soc88 15y ago
Returning the most precise result types (both collection _and_ element type) is a requirement. If this wouldn't be required, the problem would be much easier.
170.
by soc88 15y ago
I disagree. The problem here is that those claiming “it is easy in language A” haven't even understood the problem. People should first actually understand the problem, only after that a discussion about solutions makes sense.
171.
by soc88 15y ago
This is really, still missing the point. “adding methods” is trivial. The real complexity is when you add method M to collection C and expect that class A which does not have any relationship with C also gets the method. It has been shown t
172.
by soc88 15y ago
I don't see how it solves the problem mentioned.
173.
by soc88 15y ago
Have a look at how stuff like Count is implemented. It basically does instanceOf checks for ICollection to figure out if the underlying type supports a better way to compute the result (instead of iterating trough the whole collection). Thi
174.
by soc88 15y ago
That has nothing to do with the issues mentioned in the original article. In fact, the thing you described is trivial in Scala. implicit def Upcase(s: String) = new { def upcase = s.toUpperCase } "abc".upcase
175.
by soc88 15y ago
Well ... maybe just click the link and read the article? It is pretty clear. Ahh, the famous behavior of Lisp fanatics. Tragic, how it is obvious to everyone – except themselves – why no one wants to use their language. > No, CL is not
176.
by soc88 15y ago
> See the problem? No. Must be because I actually use the language instead of trying to bash it to advertise another language. :-) I'm still excited to see another language solving the problem mentioned in the article. At the moment it
177.
by soc88 15y ago
CL isn't even statically typed. Everything is easy if you don't expect that the language gives you any useful guarantees.
178.
by soc88 15y ago
Maybe you should try to understand the actual issue first, _before_ claiming that "but it is easy in my pet language" stuff ... Additionally, last time I looked Cl wasn't really statically typed. Has that changed recently?
179.
by soc88 15y ago
I still have not found a single comment showing "how easy it is in other languages". Do you have a link?
180.
by soc88 15y ago
Both "more opinionated" languages are considerably slower than Scala, so sometimes it is necessary to fall back to "ugly, imperative" code and those languages make sure you will hate that experience. The difference imho is that Scala doesn'

More ›