HN user

anothergoogler

162 karma
Posts2
Comments348
View on HN

Yes, I know. That doesn't make an assertion about the "pitfalls" of `self` less muddy. It's literally a variable. It's a code smell too, but that's another conversation. Are we calling out variables in JS now? Maybe we should just hold ourselves to bootcamp standards, copy and paste StackOverflow or something like that. Programming is hard, etc.

[dead] 8 years ago

You sincerely believe that tax revenue would be lost to waste and graft with no benefit to the poor? Higher taxes sting me as much as the next USAer, but I think you're being obtuse.

Instead of a well-designed data store, OOP projects tend to look like a huge spaghetti graph of objects pointing at each other and methods taking long argument lists.

Uh, what? FP projects are the ones with crazy argument lists, has OP even heard of the Law of Demeter? Does FP magically prohibit a huge spaghetti graph of functions and ad-hoc types pointing at each other?

The main point is: just because my software operates in a domain with concepts of eg. Customers and Orders, doesn't mean there is any Customer class, with methods associated with it.

What an observation, it's all a bucket of bits so why name anything? Rub your hands together, mutter an incantation and voila, software without all that obnoxious structure!

[dead] 8 years ago

And to think, one year ago we had the fad of Bitcoin Christmas gifts. I know some intelligent people in tech who bought into BTC and ETH around then. Sub-$1k BTC by year's end is a real possibility.

Disagree, most employers are so desperate for somebody who can show up every day and throw some code together that they will make all kinds of excuses for the candidate. Plus most interviewers know jack and are easily impressed. That said, everybody has their own understanding of "entry level." I think the market is great for entry-level/junior developers, and glutted for true senior developers. Most companies have no need for somebody's 10+ years of real experience so the ceiling is quite low, and you are "senior" after a few years.

The lede is buried at the end of the article:

Much of the data on ocean temperatures currently relies on the Argo array — robotic devices that float at different depths, surfacing roughly every 10 days to transmit readings to satellites. There are about 3,800 such pieces of equipment in waters around the globe that provide the publicly available information...

By comparison, Resplandy and Keeling calculated heat based on the amount of oxygen and carbon dioxide rising off the ocean. Filling round glass flasks with air from research stations in the Canadian Arctic, Tasmania and La Jolla, San Diego, researchers analyzed the samples to determine the aggregate temperature of the ocean.

On what grounds is three samples of a novel measurement preferable to a few thousand direct temperature measurements? I mean in terms of reliability, not ability to generate clicks.

The privacy loss of one account being popped is likely far greater than the privacy loss of thousands of users' browsing patterns being correlated.

That's quite the hand-wave. How do you even measure privacy loss? And given that browsing history is not in your inbox, why are you so confident that one compromised email account is a bigger deal?

I think you're confused about network programming in general. In a post like this, the assumption is that the concurrency is happening over a single network interface. It doesn't matter really. The most conspicuous limiting factor on a POSIX-compliant system is the number of available file descriptors. When you listen() on an address and accept() a connection, the networking stack allocates a file descriptor for that connection. Then you can handle more connections.

http://pubs.opengroup.org/onlinepubs/9699919799/functions/ac...

http://pubs.opengroup.org/onlinepubs/9699919799/functions/li...

Beej's guide is a popular intro, but I'd bet any text on network programming covers sockets.

https://beej.us/guide/bgnet/