skysight-inc/HackerNews huggingface dataset:
This is a worthwhile point.

Eating is just as cultural as the food itself. Rice and pork are both staples in Asian and Mexico, but the way the meals are prepared and served are so completely different because of a range of influences.

Why do people in the US eat the way we do? A combination of having a massive number of people living in our country, the ability to produce an enormous amount of food (especially meat), a larger GDP than anywhere else and a culture that's always trying to do things quickly/while on the go.

The culture is complex and the reasons are many, but people not learning to cook while also having specific expectations of what food should be is definitely a large part of the equation here.
I've been thinking about this a lot as someone who recently bought into a condo building.

I think SFR neighborhoods do tend to be better on average, than renter-dominated ones. Alameda (city next to Oakland) is instructive. Walk across the bridge from Oakland to Alameda, it's like you're stepping into a different world: the streets are cleaner, people drive with more civility, it really is noticeably nicer.

Condos are a bit of a wildcard. They can be better in theory but most probably aren't. As someone on my HOA board, I put a lot of time into making sure my condo is a good place to live. (328 units, 1000+ residents). Just yesterday, we invited Monkeybrains over for a chat about getting fiber in the building. We'll do it soon.

I think it's just that the challenges are different. In a SFR neighborhood, you get a lot of very invested people, which is good but also can be bad (NIMBY). Apartments people don't care as much. Condos have "ownership" but also governance problems; they can be the best when run well, but horrible when they aren't, which seems depressingly common
To make sure it does the opposite of anything the JS ecosystem ever did? In that case, I agree.
The sun is radioactive. Sunlight is not radioactive, it's radiation.
Introducing a Powerful Release Engineering Process for Zenko
> It sounds more like a cultural issue, or perhaps such staples are not easily found in most of the USA and/or are marketed as "health foods" and suffer a corresponding price increase?

Culture definitely sounds like a component, I wouldn't be surprised to hear a crass criticism of your rice-and-beans meal as something eaten by "those starving children on TV."

There's also the issue that a lot of folks simply don't know how to cook. The benefit of a lot of those box meals is the hand-holding, instructions included nature. I buy a box, it tells me what I need to buy, and how and how long to cook each component.

I'm a bit embarrassed to admit, but if you handed me a sack of rice and beans I'd have no idea how and for how long to cook it. I simply never learned those skills. In the past several months I've realized how poor my culinary skills are, and have been working to address that deficiency, but for many folks in the US we simply pick the path of least cost and effort.
The Age of Floating Transport
The aircraft case is a good bit different than the car case IME.

In cruise, there's not much to do in an aircraft and minimal oversight by the pilot is easily accomplished. Then, during the arrival (and during the departure), the workload is quite a bit higher, meaning the job is anything but boring and it's easy for the pilot to remain engaged.
>For RTS games, 250 milliseconds of command latency was not even noticed -- between 250 and 500 msec was very playable, and beyond 500 it started to be noticeable.

I wonder if the rise of competitive RTS has changed this guideline. In SC2 people will start to complain if their ping to the server is more than about 130ms, and anything above 150ms starts to become painfully noticeable.

In Brood War being able to play on "LAN Latency" was a always a huge deal---to the point that unauthorized third party ladder systems enabled players to play at "LAN Latency" even when battle.net official didn't support it.
Likewise with Apache Groovy, which has optional typing:

#!/usr/bin/env groovy
// @Grab annotation won't work in scripts
import static groovy.grape.Grape.grab
grab(group: 'org.apache.commons', module: 'commons-csv', version: '1.5')

println "Starting to parse CSV"
Samsung plans to launch smartphone of the future
(Author of the original article here) It was really pretty naive - nobody would plan for an RTS now without planning a series of patches to do the inevitable adjustments. Even for AOK we planned to patch and adjust. The 'general argument' was a MS publisher stance as quoted by Matt Pritchard - to do a patch in those days through the MS system meant a lengthy and expensive full test process, rollout, creation of a patch system, etc - so it was something you planned and budgeted for. The concept of 'day-one-patch' would have been pretty horrific. Patching is now something you integrate, plan for and expect - because we aren't shipping on gold masters to a printing company.
Heating it with Coke?
> If you then look at those outcomes together, you find that in over half of them, we are alone in the universe.

Since we do not really know, anything but P=0.5 should imply incorrect prior estimates. That might be more insightful than whether alien life exists or not.
I know this is about congressional campaigns, but does anyone remember this from 2008? https://www.theguardian.com/global/2008/nov/07/obama-white-h...

I wonder why that never reached the same amount of outcry when Obama won.
Tax policy and zoning is clearly telling people what they can do with their property. Eminent domain is clearly telling people what they can do with their property. The problem is that those who want cheaper housing don't have the votes to win on that issue.

And if building a high rise damages the value of an adjacent property with no compensation, that's a taking, no?
Still USA citizens, not ideal either.
Imagine if in python open('file.txt', 'r') never failed so no one ever bothered to put a try block. To prevent this from happening they purposely have open() fail a couple times.
Yann LeCun’s IJCAI Keynote: We Need a World Model
It depends on the genre and the specific game. RTSs can do it this way and some fighting games do, although some fighting games use a variation that involves predicting player input and rewinding the game state on misprediction in order to reduce perceived latency. FPSs tend to use a totally different model that involves sending only the most recent relevant information to each player and trying to balance server authoritative cheat-prevention with allowing clients a little leeway in order to make the twitchy gameplay feel better. There's a great paper on Tribes' networking model that is still largely relevant for FPSs.
You need to turn off bluetooth on your phone too.
German Manufacturing Behemoth Siemens Forges AI-Enhanced IIoT
I believe wow (and most MMO's) instead take input from each player and run the simulation completely on the server. Although often enemy and NPC positions aren't synchronized exactly between players. There's also much more tolerance for latency in crowded situations - it doesn't really matter if the ~30 other player characters lag behind their actual position in a town by even 5 or 10 seconds, you only need players in your party or who are fighting against you to be low latency.
How to Use Hashtags in YouTube Video Titles and Descriptions for Better Search
What they mean is that if you're doing anything that samples random, don't do it inside of something like a loop whose length is dependent on the local game state that isn't sync'd on the current turn; especially in the graphics engine for doing particle effects or picking random animation frames. Like if you sample random every animation update frame to pick which fire graphic to use on a torch or bonfire (very common), but you suffer graphic slowdown and sample it not enough or too many times, that could vary between clients unintentionally.

Once it comes time to simulate that next turn, if you have something different than other clients because of a missed update or graphics lag, even if object positions and the random seed going to be "fixed" by another turn update, all future interactions with any objects that over- or under-sampled random will be wrong and could create further sync problems.
I wonder why ambulances don't have mobile x-ray systems? I realize the radiation would have to be managed, but it seems like a great application of technology to perform the imaging and send it digitally while eh route.
You must work for Apple :P
If you're building a system from scratch, keep in mind that this way of designing your service may not be flexible enough. You don't want just service level objectives, agreements and indicators, you want customer level.

Your service may end up providing for multiple customers with different requirements. Maybe 1% of your customers will end up using 99% of your resources, creating uncomfortable situations that affect the other 99% of customers. To get away from this you have to start spinning off multiple identical services just for groups of customers, which is really annoying to maintain. You may find you need to add hard resource limits to control customer behavior, which is hard to add after the fact.

Instead, if you design your new system from scratch with customer-specific isolation and service levels, you can run one giant service and still prevent customer-specific load from hampering the rest of the service. You can also just run duplicate services at different levels of availability based on customer requirements, but that's not going to work forever.

As an aside, I'm looking forward to reading ITIL 2019 to see what new processes they've adopted. I think everyone who's getting into SRE stuff should have a solid foundation on the basics of IT Operations management first.
Per the article, Google has over 100 engineers working on Fuchsia. If these are all "senior engineers" that "Google is trying to retain", the cost of keeping them must be at least 50 million per year.

That's a lot of money to pay just for retention of people who are not producing anything of value, consuming many other resources (office space, network, hardware, perks), and deeply committed to a project that supposedly will never benefit their employer.

A rich employer may retain an unproductive employee for a limited amount of time if they expect it to ultimately pay off. It just doesn't make any sense to retain someone indefinitely if they're not going to produce anything of value, and (implicitly) will quit the moment you try to put them on any sort of real-world valuable work. Google is a public company with fiduciary responsibilities to its shareholders and a legally accountable board, it can't just throw tens of millions of dollars away without good reason or explanation.

> You see all these different projects competing against each other (multiple messaging apps are a good example) and you think: why is Google so unfocused?

There are many good reasons to have multiple teams competing against each other, building the same product. Often it will bring a strong drive and pace to all competing projects, as well as cross-pollination, and eventually they often merge to a single deliverable that is better than any of the projects could produce individually.

> what Google basically wants to do is hoard engineers

I'm not sure why all these improbable theories make more sense to you than the plain fact that Android was designed quite a few years ago, has many natural deficiencies, and - like all technologies - will eventually be replaced by a superior successor.

That's exactly what Fuchsia is about. Its existence does not require any elaborate conspiracy theory. On the contrary: given how strategically important the Android market niche is for Google, it would be very surprising if Google was not working on a viable successor. It's as if Sony didn't have a successor for the PS4 in the pipeline, and just expected it to sell forever, with minor patches here and there.
Thanks for your feedback. When we ship a scriptable version Docker seems like a great choice for wrapping it. I'll add an env variable for ya :)

The JVM is somewhat allergy inducing, but I think Graal may solve a lot of these issues. Optic is written in Scala because a) it's a great functional language and b) the JVM is super portable. If we can get Graal working nicely in our builds, binary sizes should drop markably and performance should improve.
I personally love Angular (Not AngularJS) + TypeScript.
If you can get along with how opinionated it is, you will be rewarded with a quick development time and great looking project that is easy as pie to manage.

Vue doesn't seem to be robust enough yet for larger projects, and I personally just don't fancy React's syntax.

If you want to just be able to get from 0 understanding of front-end to making a working demo, you really need basic HTML/CSS/JavaScript. It's like trying to write a book before you learn to read.
This is where it comes from: https://youtu.be/NlCJokZcwJA?t=15m24s

(Starts at 15m 24s)
The problem is that this extra day will allow them to think of/execute their own plan... but I need them to be part of my plan and have the weekends JUST be for rest.
> Part 2 being time.

I really don't think so. All the statistics we have point to poor people having more, often much more, free time than middle class people or rich people.

https://www.statista.com/statistics/191558/average-daily-tim...

https://www.theatlantic.com/business/archive/2016/09/the-fre...

Thirteen year old children can also be taught to cook and prep reliably, as I'm sure you know.

Part 2 is probably more likely a basket of cultural issues. Sampling my middle income and lower friends, almost none of their parents taught them a thing about cooking. (Those that did of the very poor had 13 year olds cooking.)

I have seen a total lack of interest in cooking and a total lack of planning. It takes essentially zero time to soak beans overnight, and no time to simmer them in a pot with olive oil or butter or anything else you have (carrot water/cabbage water/stubs of vegetables if-you-have-any water). Many times a week I make beans and scrambled eggs this way.
Oh my god just freakin kill me already. You can never do this shit right, it’s extremely tedious.
So the lobbyists only have one place to go to buy the laws they want.
You think that's bad? I got my last book in the same package as a 40lb bag of cat litter.
I recently bought a washer and dryer at Best Buy. I was thoroughly impressed with the selection and customer service. They even gave me a deal on the higher tier model after the ones I wanted were on backorder. I think they partner with Pacific Kitchen and Home to do the appliances.

Their remodels have gone a long way in getting me back there, personally. I had otherwise steered clear and was an Amazon/BH junkie.
Right, which is why the press should specify phishing here, and boost awareness for this particular threat, rather than ambiguous 'hacking'.
> Property owners often don't sell their property even when it seems advantageous to do so, both for them and for the economy in general.

I think there is a big difference between property owners who buy a house to live there, retire, hoping it appreciates in value, and people wealthy enough to buy a 2nd or 3rd house, or even a whole block. The later, would have no qualms selling them quickly if another opportunity arose. The first category of people will be a lot more risk averse. That's also one of the reason why the wealthy get wealthier, they don't have to worry about risk, and can easier jump from opportunity to opportunity.
Even more interesting than other sources is the fact that many spinal and similar surgeons reach their lifetime radiation exposure limit in just 10 years of practice. Many (most?) end up with cataracts or other tell tale symptoms of radiation exposure. It's because of all the x-rays needed for minimally invasive surgury.
True, but I think that for bigger applications static typing is better even if you don't get it quite right.
https://en.m.wikipedia.org/wiki/Coke_(fuel)
> Only thing I paid? The taxi ride home. For anything else there was my insurance card.

Oh, so you don't pay for your insurance card? Nice deal! Because I also have public health insurance in Germany, and last time I checked, it cost 14% of my gross salary.
America's Binge-Drinking Problem Is Even Worse Than We Thought
How did you get that zoning map? Does anyone have one for Montreal?
What do you think I'm doing all day at work? Planning my own venture.
It's exactly that.
Just replying about 'balconies' - I //hate// them as sources of noisy neighbors and neighbors that smoke and thus ruin the air around where I live.

I also dislike how MDU exhausts, particularly the laundry exhausts, are not sent out a scrubbed (E.G. water filtration) negative draw system to remove the fine particulates. I have never in my life even seen an MDU with such a setup, let alone filtered air ingress delivered to each unit.
>but you know how much easier this would be for everyone if Google offered an option for users to be paid for volunteering your information to them?

Have you not seen their Opinion Rewards app for Android? They do precisely that.
(Original author here) - here was a really hard-to-find bug - in some instances more than one quantity of fish could be placed in the same location - that meant the game would work fine until someone fished that same fish the second time and the fishing boats would diverge in the different simulations. The world sync check only counted the tile contents so we didn't see it. - There were actually two RNG's in the game, one was synchronized with the same start seed on all machines (basically the same random pool) for combat and whatnot - the other was unsynchronized and used for animation variance, etc -things that weren't gameplay related. Not knowing when to use one of these specifically (e.g. animals facing seems like animation but definitely affected gameplay if they could be hunted) could alter the code path and cause an out-of-sync condition.
> they basically pick deals based on who else is investing.

Another phrase for that is "herd" mentality, which will hopefully result in de-risked "safe" investing, but VC's are supposed to be looking for true breakout possibilities. If LP's wanted safe, they'd buy Treasury notes.
> First, in both of your points someone gets fucked. As far as you're concerned, who cares, so long as it's the right group getting fucked. Perhaps the real discussion is on why you chose to favor one group (new property owners) at the expense of the other (incumbent property owners).

This is a disingenuous characterization of the problem at hand. Its not a question of newcomers getting your single family home from you, its of you selling your home which will likely be redeveloped into higher density housing for a lot more people. And you wouldn't be "fucked": yes you would lose your beautiful single family residence, but more people would be able to afford living in the community in which they are a part of, but can't because of how expensive housing is.

On the contrary, by denying newcomers any housing near their workplace, you are fucking up their quality of life immensely: they cannot build equity (prices too high), are forced to commute long distances or are simply excluded from the community because of artificially high home prices, have to pay much more in taxes for services that you use. That is massively fucking a lot of people.

This isn't rocket science; it happens all the time in all major cities. Low density gets redeveloped because of changing economic and social conditions. Its how cities evolve. Prop 13 is basically stifling the growth and natural evolution of major cities in all of California, but especially SF.
Having multiple competing projects is not unheard of in the business world in general, and in high-achieving technology businesses in particular. Often, those outside the organization are only aware of the winning project, and the others are quietly discontinued, with many / most / all members moving to the winning team.

I know of several other prominent examples, but can't mention by name because I'd be breaking an NDA.

Also, Fuchsia is a successor, not a competing project, strictly speaking. It would be the "gauntlet" scenario if Google was running multiple ongoing projects all competing to "inherit" Android (which quite possible it does...)
Honestly, the worst was DHL. I got so frustrated with them, I contacted Amazon's customer service and offered to pay extra to NOT have DHL deliver my items.

The agent offered her apologies and noted they couldn't offer that (did refund me delivery costs), but would note the preference. Not sure if that "note" actually did anything, however I started getting substantially less DHL deliveries, which was a plus.

These days, most problematic is Amazon's own deliverers. They tend to deliver the same day, but usually late in the day or to the wrong address.

USPS and UPS are the best, with UPS edging in delivery time. I've had two USPS packages marked "Delivered" but show up the next day. FedEx seems to miss delivery times a lot.
I feel 3 days, minimum, makes the most sense. You have a day for personal errands, a day dedicated to family activities, and a day for rest and relaxation. As it is, time is hyper squished on the weekends, at least for me it is.
Even if the surgeon doesn't deal with the insurance company directly, you should at least be able to submit the bill to them yourself?
The point is that if Java had had generics in the beginning, they could (perhaps) have been integrated into the language in a way that obviated those casts entirely.
My personal favorite. !14 !14 !14
...and then you reach your 30's and realize you're wasting your life in work.
Is it something easily negotiable in big tech companies?
Hirst?
> Please elaborate on why we should consider that belief false?

Because the alternative, a “magic words” requirement for invoking the power to declare war, is (1) inconsistent with the way every other Article I power is treated, and (2) was conclusively rejected by the courts while the ink was still practically wet on the ratification of the Constitution, in Bas v. Tingy (1800).

> Plenty of Senators disagree with you.

There are all kinds of false beliefs publicly embraced (and perhaps actually believed, but that's harder to assess) by plenty of Senators, but I don't see any evidence that the particular one I took issue with upthread is one of them.
I think what Raymond Hettinger said is a good starting point: slow down and allow the ecosystem at large to catch up. Make big changes in a slower manner, and if there is no widespread agreement on a PEP for more than a year or two, just drop it.
Four tens is a pretty great schedule. Those two extra hours somewhere in the day when there's usually not anybody working are almost as good for productivity as the other eight. And a day off during the week is worth its weight in gold for getting errands and all the other nagging little things that are a huge drag working the whole week.
> literally

excuse me, but no. Our best-effort guesses might be the best we could literally do. But there is no need to be that literal, or literal at all. As long as the uncertainty range includes 0.5, it's OK, but merely a test of how much we know as a fact as opposed to intuitively. And at that, the equation can surely be blown up further. Why would it be optimal?