draluy

Your implication that google services are free is untrue. You are paying with your privacy and data. And the price is such that, if I ever made a better mail service than gmail that openly asked to sell and privately use all your data, nobody would subscribe. You are paying by seeing ads. You are paying by being coerced into a certain ecosystem. You are paying by having one company chose what standards are the de facto web standards of tomorrow. And their main business is selling your data. You are paying by losing access to your data if a company feels like it. etc.

I dont get this. If this is true, then he found a more efficient algorithm than binary search. Why are we not using it in CS?

Mastodon?

Just mount the Graphics card vertically using a raiser cable. It more of a PC case problem that a motherboard problem. Also, it allows for better form factors, with spread out components and bigger fans.

This article is so infuriating I had to log in. All this article is underlined by the fact that Alice and Bob should try to get the most out of the negotiation regardless of needs. This is a rightist way of seeing the world, and in my mind childlike. With any level of maturity people should realize pizzas should be divided according to who needs it, whatever the definition of need is.

How about this way of dividing the pie: Alice and Bob describe theirs needs to a third party, and the third party gives each one what is needed. Or if no third party: just describe and justify your needs in an envelope, open both simultaneously, and share the pie.

The logic that "of course, everyone should take as much as they can" is an impasse. It doesnt make anyone truly happy, makes the person with the worse fallback an inferior to the other party during the negotiations, doesnt guarantee fairness, etc. And worst of all: it doesnt allow for human values such as empathy.

This article is an algorithm between programs, not any reasonable way to treat a person, valuing their feeelings and needs.

From what I read it could be the buildup of scar tissue around the magnet. I can't find the source, sry.

I find it very bloated. I spend so much time waiting on the compiler and writing boilerplate code (as opposed to actual features), that I try to avoid it when I can.

I really prefer Vue, because it gets out of my way when declaring services or making modules etc.

Can you elaborate on one? I think I'm part of the not very intelligent crowd that actively dislike angular due to the points raised in the article.

Thanks!

Does anyone know how to solve the tennis-ball formula? All I can muster is that the distance on the beach (b) divided by the speed on the beach (Vb) + the distance on water (w) divided by the speed on water (Vw) should be minimized. So I should find the minimum of b/Vb + w/Vw , but I have no clue as how.

I understand most of your points, but I disagree when it comes to the Optional part of your article. As stated by Brian Goetz here (https://stackoverflow.com/questions/26327957/should-java-8-g...), the intent was not to use optional all the time as you suggest, going as far as to say "Optional allows you to completely remove NPEs from your program. ". No they do not, an optional can be null anyway. As explained by Mr Goetz, they should only be used when designing an API, to explain to the consumer that a result may not be returned: "you probably should never use it for something that returns an array of results, or a list of results; instead return an empty array or list. You should almost never use it as a field of something or a method parameter."

I think we should keep in mind this is a type added for the JDK code foremost, and use it in similar use cases, and not see it as a general replacement for nullable values.