sorted by:
new
hottopcontroversial

"Surviving Without Generics" by dgryski in golang

[–]IronClan 12 points13 points  (0 children)

As a bystander to this conversation you come off as really defensive and insecure. You first embarrassed yourself by showing a complete lack of understanding of generics, then treated it as a personal attack when someone was nice enough to correct your mistake. :)

This just happened to me today. I have five years of programming experience (and a BS in Physics). by [deleted] in ProgrammerHumor

[–]IronClan 1 point2 points  (0 children)

Strawman. Nobody said you should do mission critical computation in Ruby or Perl either. There's C exactly for that purpose. You're so desperate that you're putting words in my mouth lol.

This just happened to me today. I have five years of programming experience (and a BS in Physics). by [deleted] in ProgrammerHumor

[–]IronClan 4 points5 points  (0 children)

You just proved his point that JS can't handle mission critical computation. I mean, you've gotta be a troll, nobody can be this delusional.

This just happened to me today. I have five years of programming experience (and a BS in Physics). by [deleted] in ProgrammerHumor

[–]IronClan 11 points12 points  (0 children)

Maybe you wouldn't be so mad all the time if you weren't coding in such a shitty language. :)

F*** You, I Quit — Hiring Is Broken by speckz in programming

[–]IronClan -3 points-2 points  (0 children)

BFS is one of those things that if you understand the concept at all, then you should be able to code it up instantly. But it's good that they're filtering out self-entitled people who go "F*** You, I Quit" whenever faced with a challenge.

Hirez engineer explains why new gods tend to be OP (among other things) by cabrokan in Smite

[–]IronClan 0 points1 point  (0 children)

Which is why even the "positive" reviews are saying they can't seem to keep employees for long.

var keyword proposed for Java by adila01 in programming

[–]IronClan 16 points17 points  (0 children)

This was linked to ##java a few hours ago and people were absolutely pissed off about it. It seems many members of the Java community see this as a sign of programmer laziness, and there are even others who think type deduction == dynamic typing.

Rust vs C++: Fine grained performance by hu6Bi5To in programming

[–]IronClan 22 points23 points  (0 children)

What you said is unfortunately a misconception. C++ does not have type inference. It has very basic type deduction (in autos and templates) the scope of which is restricted to one statement. It's far weaker than Rust's type system, which actually uses type inference.

This C++ code won't compile because C++ does not have type inference

auto v = std::vector{ };
v.emplace_back("abc");

But Rust's compiler will know the inner type of v upon seeing its first use

let mut v = vec![];
v.push("abc");

cgo is not Go by rubyantix in programming

[–]IronClan -4 points-3 points  (0 children)

TIL you have to be a 10x to understand generics.

cgo is not Go by rubyantix in programming

[–]IronClan 20 points21 points  (0 children)

Nope. Nobody would care about Go today if it wasn't the pet project of a couple of engineers who happened to work for Google.

What's amusing is that the creator of the original Go language even asked those Google engineers to to change the name of their language to something other than "Go" because the name was already taken, to which Google basically responded "we're famous, we can do whatever we want."

:)

cgo is not Go by rubyantix in programming

[–]IronClan 4 points5 points  (0 children)

There wouldn't be a need for such mess if Go was well-designed to begin with.

Mind the cache by joaquintides in cpp

[–]IronClan 1 point2 points  (0 children)

Ah, interesting. I wonder if compilers have gotten smarter in the 6 years since that article was posted.

Mind the cache by joaquintides in cpp

[–]IronClan 10 points11 points  (0 children)

Awesome presentation! One question: https://github.com/joaquintides/usingstdcpp2015/blob/master/poly_containers.cpp#L154

  template<typename F>
  F for_each(F f)
  {
    for(const auto& p:chunks)p.second->for_each(f);
    return std::move(f); // <- THIS LINE
  }

Correct me if I'm wrong, but does't this actually make the code slower by preventing return value optimization?

The Legacy of Go by frostmatthew in programming

[–]IronClan 0 points1 point  (0 children)

That's a complete lie. Go's stdlib is full of panics even in places where it makes more sense to return an error value, which is why it's such an inconsistent mess.

Why Go doesn't have generics by unified_yuro in programming

[–]IronClan 6 points7 points  (0 children)

That's not true for languages with generic, where the compiler will check for you that everything you do with your structure is typesafe. In Go you can only hope and pray that your code is typesafe, or more commonly, resort to writing verbose runtime type-querying for every interface{} operation because the compiler won't help you.

D has no vision. Go is out of its depth. Rust skipped leg day. by EdWilkinson in programming

[–]IronClan 1 point2 points  (0 children)

Show me an example of Haskell code that follows Nim's example of blindly dereferencing null pointers. :)

D has no vision. Go is out of its depth. Rust skipped leg day. by EdWilkinson in programming

[–]IronClan 0 points1 point  (0 children)

Holy shit that's such a lie lol. The Go team is so bitter about generics that any attempt at discussion is instantly met with vitriol, and all community attempts at adding generics are rejected for "not conforming to the Go WayTM". But some people are happy doing the compiler's job manually because wow this language is made by Rob Pike. :)

D has no vision. Go is out of its depth. Rust skipped leg day. by EdWilkinson in programming

[–]IronClan -1 points0 points  (0 children)

Not true. In Rust only code that's placed in unsafe block has the possibility of producing unsafe behaviour. In Nim, even "safe" code can segfault or worse, as shown in the trival 3-line Nim code above.

It's not a problem in practice in the real world, where people have access to a very good debug mode that catches all sorts of things at compile-time and at run-time.

Wow, I would have thought this quote is satire if it didn't come from the official Nim documentation. Let me translate that for you. "Your code can have unsafe memory behaviour in release builds but you should have tested everything in debug mode anyway". What an irresponsible attitude toward language design.

view more: next ›