frowaway001

13 ms·

61.
by frowaway001 12y ago
I hate Hadoop with a passion, but this reads like written by people even more clueless than Hadoop developers. > Contrast this with Pachyderm MapReduce (PMR) in which a job is an HTTP server inside a Docker container (a microservice). Yo
62.
by frowaway001 12y ago
> for anyone who wants to write isomorphic code without a lot of pain in compilers, is limited by browser adoption Are you confused? "isomorphic" doesn't mean what you think it means ...
63.
by frowaway001 12y ago
No, not really.
64.
by frowaway001 12y ago
Error highlighting is usually instantaneous.
65.
by frowaway001 12y ago
The important thing is that it doesn't grow proportionally. Adding a second line to your "Hello World" doesn't give you 7000LOC, just like using jQuery in two places instead of one doesn't automatically double jQuer
66.
by frowaway001 12y ago
Yes, both Scala and Play are great.
67.
by frowaway001 12y ago
Did you even understand that the whole point of the article was about not bringing up Monads? Jesus.
68.
by frowaway001 12y ago
This is nonsense.
69.
by frowaway001 12y ago
> AFAIK LINQ pretty much is a library since its just extension methods No, that's flat-out wrong. LINQ's main feature is turning code into data: Put code in, get an expression tree out.
70.
by frowaway001 12y ago
There is pretty much no reason to use <> except "that's what C++ did, because they didn't have any other symbols to spare". If done correctly, (e. g. [] for types, () for values, and >/< for binary compa
71.
by frowaway001 12y ago
There is pretty much no reason to use <> except "that's what C++ did, because they didn't have any other symbols to spare". If done correctly, (e. g. [] for types, () for values, and >/< for binary compa
72.
by frowaway001 12y ago
There is pretty much no reason to use <> except "that's what C++ did, because they didn't have any other symbols to spare". If done correctly, (e. g. [] for types, () for values, and >/< for binary compa
73.
by frowaway001 12y ago
So how are you writing Go if you neither use arrays/slices, maps, channels, etc.?
74.
by frowaway001 12y ago
>"Go's authors clearly have some trouble understanding the mathematical foundations of type systems" Well, yeah. Is there anything wrong with that?
75.
by frowaway001 12y ago
I think that's a bit different. Scala – just like Java – allows you to write inefficient code. The Android's GC is pretty poor, so things you might have gotten away with when programming on the JVM in Java or Scala might require a
76.
by frowaway001 12y ago
There are no performance implications for Scala apps.
77.
by frowaway001 12y ago
Says the Golang dude. Pot. Kettle. Black.
78.
by frowaway001 12y ago
I think it is reasonable to demand that companies have some responsibility for people who spend roughly 40 hours a week at their place following their orders. Companies are not "forced to keep surplus employees", it's a reaso
79.
by frowaway001 12y ago
You can just disallow the compilation of anything where null appears, as well as plenty of other style issues. The language gives you plenty of tools to enforce the appropriate coding style for a given project.
80.
by frowaway001 12y ago
Why am I supposed to do that? A) I'm using a working language already. B) Read the comments on the mailing list regarding third party proposals/implementations from the Go authors. In short: Complete waste of time.
81.
by frowaway001 12y ago
Yes, and Go apologists would also know at least one solution if wouldn't keep pretending that they can't keep reading the post until the very _first_ comment on the same page.
82.
by frowaway001 12y ago
I used to play with a small plastic hammer when I was in kindergarden thirty years ago! I will be very irritated if people laugh at me for trying to build my new house with this hammer now.
83.
by frowaway001 12y ago
Scala is pretty nice. Concerning the JVM startup time: It's usually in the range of milliseconds for your use-case. What gave the JVM a bad name regarding startup time are large JavaEE application servers which had dependencies to hund
84.
by frowaway001 12y ago
Yes. It's neither an operator nor are you overloading anything. The whole point is that everything is just a bog-standard method and infix notation is a orthogonal notion, separate from a method's name.
85.
by frowaway001 12y ago
No. Scala has neither operator overloading nor any kind of rampant form of it.
86.
by frowaway001 12y ago
Which is kind of funny, because they are still playing catch-up with Scala. (That's perfectly fine on its own, but doing the usual Scala-bashing at the same time as copying most of the language varbatim doesn't make the Kotlin tea
87.
by frowaway001 12y ago
Did you even read the article you linked to?
88.
by frowaway001 12y ago
If that's the standard Rust is aiming for, than I'm very sad about it.
89.
by frowaway001 12y ago
Also, the whole cargo thing is a disaster. One namespace for all libraries? This will work out great. Totally. Not.
90.
by frowaway001 12y ago
No, certainly not.

More ›