thwd

When I think about the generics discussion in the Go community (and even though I am personally for them), this is the kind of exponential complexity that I wouldn't want to see in any implementation thereof.

> place cells

Suiting, given that your username means "place" in German :)

Shame how such a cool project as node.js can drown in political fingerpointing. The only measurement that counts (in my opinion) is cold hard code contributions.

They should know that not all cars break down two times a month on average and that black smoke is definitively not a feature.

Argumentum ad populum; people just don't know better. Also, I doubt it's really hundreds of millions (of people, as opposed to installs).

Just like peer review is a necessary step for a study to be taken seriously, replication studies should be regarded as the direct next step. There needs to be incentive to reproduce the experiment.

On the other hand, #3 might in this case be exactly that: Small companies creating accurate & precise modeling techniques using only a limited amount of data, while giants continue to rely on the sheer and blunt volume of it.

Hochdeutsch is, in my experience, relative. Swiss people call the language of Germany Hochdeutsch, regardless of region. The southern Germans I've met seem to collectively agree that they do not speak Hochdeutsch and that Hochdeutsch is what is spoken in Hannover. I don't know many people from northern Germany, but I recall an instance of someone mentioning Hamburg as being the Hochdeutsch standard in their ears.

On my Google onsite (in Zürich as well), one of the interviewers told me that if he gave me a 4.0, he'd have to argue on my behalf if the hiring committee wasn't sure of hiring me.

Very cool! One thing I noticed is that if you lock all colors except one and press 'generate' repeatedly, each call produces a different color. Why is that?

There's a joke: Mathematics is just applied Philosophy.

It bears some truth :)

To master a lot of the most "hard core" programming concepts, dive into parsers and compilers. It will give you a perspective and generality that will permeate the rest of your career. It gives you arguably the most high-level perspective on all things related to programming and the paradigms therein.

@rspeer used sarcasm, implying everything you said in your two posts and more.

I understand what you mean and agree. But then, you don't need to compile JS into Dart. Rather, JS into DartVM byte code.

Dart can compile to JS, so that edge is covered. Dart bytecode is arguably an easier target for other language compilers than, say, assembly. The DartVM's byte code is fully specified, there is some adoption, it's openly accessible, and there's a bold, production-ready reference implementation. For wasm, only half of that is true.

Thank you for answering the question seriously. All the down-votes were giving me the impression that the answer was "you don't". It's good to hear/read that the Java community is moving on from those practices.

I'm genuinely curious: what is considered light-weight in the land of IAbstractFactoryCreatorBeanSingletonProviderDecorator? I.e. how do you consolidate OOP abstraction practices and conciseness, performance and usability?

> So, have any of you ever been in the same situation and do you have any advice on how should I overcome this?

I haven't, but a good friend had a very similar experience. He worked in telco, stayed at the same company for almost 20 years and then wanted to move on.

The problem wasn't him, it was the company he worked for. They had (still have) a reputation for being bad on the technical side, using age old technology and an even older management style, never updating anything to contemporary standards. Sub-par products.

Potential employers didn't want him because they were afraid he was representative of his old companies' culture. Half his resume was just the different positions he filled at that one company.

The solution he eventually found was to dissociate himself from the company as much as possible on paper. He also picked up 2 modern technologies that he had never used and mentioned them in the applications, as a form of showing he was ready to learn new stuff. It worked.

This sentence stood out to me:

> Now that this gag order has been lifted, Cloudflare is able to publish a more accurate transparency report to its customers and constituents.

A _more_ accurate report, not necessarily a completely accurate report. May or may not imply that there are other gag orders still in force for the period. I wouldn't be surprised.

as C does: with a \00 end marker.

Agreed, but the payload from the article doesn't seem to have suffered from astral radiation. Rather, random attempts at quote-escaping by someone who doesn't understand what they're doing. Also notice the "nan" value -- JSON has no concept of NaN.

I think they mean that if you realize you're talking to a non-techie then you should make an effort to use simple words. Your TCP hex opcode knowledge does not impress someone who doesn't know what hex or TCP is. Figuring that they must be looking for an answer along the lines of "SYN/ACK" is a skill as well. A people skill.

Yes, there are.

Difference is radar/lidar both emit the radiation they use to see themselves. It's hard to illuminate a car's outside completely from within the car.

Don't know about the American thing but what I do know is that while in Europe they teach us to turn our heads and bodies when driving, the modern world caught up with blindspotless mirrors and teach you to use them. It's much safer as people tended to turn their hands together with their bodies, effectively steering a car to the left when looking out the left window.

To illustrate my point: If I implemented some network program which converses with a remote server in multiple steps in an language with exceptions and something fails I might get a stack trace and the message:

"Syntax error, expected token HTTP_METHOD but got 'B'"

In Go, with proper error handling I'd get a message like:

"Couldn't do flubber transfer: Unable to negotiate protocol: Sent supported protocols but remote responded with HTTP 400 "Bad Request": Missing required field 'version' in protocol definition"

As "error" is an interface, this message is only the tip of the iceberg: the error object itself may contain the address of the remote server, the protocol definitions that were sent, the response body that we got and any other relevant contextual payload.

This is all due to the error being treated in-context as opposed to just bubbling up.

True, you can discard errors on purpose by assigning them to "_", which is an explicit way of saying "I do not care about this error happening". If you do that and get a panic down the line, you already know where to start debugging. That's much better than having an exception bubble up from deeeeep inside your code with some context-less cryptic message or number, isn't it?

How does Go completely ignore run-time errors? For all I know it forces you to deal with them by treating them as values instead of exceptions.

That's just clever wording.

> We won’t post or share your WhatsApp number with others, including _ON_ Facebook.

Is just saying that your number won't be visible to your facebook peeps. Which does not mean that Facebook (the company) won't get access to it.

A slice is a view over a continguous array. deleting an index in a continguous array is inherently O(n). Go doesn't obscure this. The pain of writing it out reflects the complexity of the operation.

Compiling a Go program is really quick and painless! Nothing like a similar C/C++ project.