skysight-inc/HackerNews huggingface dataset:
Not my workaround:

http://spectrum.ieee.org/aerospace/space-flight/titan-callin...

http://descanso.jpl.nasa.gov/seminars/abstracts/viewgraphs/H...

This was an extremely serious bug in NASA/ESA's Cassini-Huygens probe, in the S-band link between Huygens (landing on Saturn's moon Titan) and Cassini (acting as radio relay).

It was a timing bug. There'd be a very high relative velocity between Cassini and Huygens, creating a significant (~2e-5) Doppler shift in the link. This shifted the frequency of the 2 GHz carrier (by 38 kHz). Likewise, it shifted the symbol rate of the 16 kbps bit stream (by 0.3 bps). The second effect was overlooked. On the demodulating end (Cassini), the bit-synchronizer expected the nominal bit rate, not the Doppler-shifted bit rate. Since its bandwidth was narrower than the 0.3 bps Doppler shift, it was unable to recognize frame syncs; this was proven in experiments post-launch. The parameter that set the bitrate was stored in non-modifiable firmware.

As it was when launched, Huygens would be unable to return any instrument data. For some context, this was the only probe that's ever visited Titan, at a cost of about $400 million.

The workaround

[spoiler]

The workaround was a major change in the orbit trajectory of Cassini (a $3 billion probe). Details aside, it set up an orbit geometry with this feature: at the time Huygens was descending in Titan's atmosphere, Cassini would be flying at a ~90° angle to their separation. The relative velocity was still 20,000 kph, but tangential velocity doesn't contribute to Doppler shift.
Do yourself the favor, buy the lard and leave the pasta for the people who believe the broken gov't recommendations.
> The intention of the big.LITTLE architecture is to let processes be migrated seamlessly between the small and big core and let the unused core be turned off to save power.

On the other hand flushing specific cache lines is a rather special feature. If the code uses such obscure low-level features (much more than the "typical" application) such as the invariant that the size of a cache-line stays constant over the execution (which most applications really don't care about) one can at least expect from the developer to pass this information to the scheduler so that the scheduler can take that this invariant will indeed be satisfied.
> I tried their web version and was left dissatisfied. Lacked reporting

It's a shame that there is still no official reporting (9 months since the release already!).

However, if you absolutely need it, there's a browser extension called Toolkit for YNAB: https://github.com/toolkit-for-ynab/toolkit-for-ynab. Besides reports it adds some more essential features like search.
It's too bad nobody pumped the brakes after it was a little successful, and said "Okay guys, let's stop dicking around and do this right now, before we have to deal with it for the next 30 years". Alas...
I find articles like this pretty frustrating. There's tons of companies in Silicon Valley that are trying to do audacious things that people's mothers never did for them. They don't get much press coverage and that's fine, media outlets are businesses too so they need to write about companies that their readership wants to read about. But the fact that they then turn around and complain about the fact that all the companies on their radar are the same is outrageous. They're all the same because there's this huge selection bias applied by the fact that they only cover companies they think their average reader can understand. Which isn't a very wide variety.
Haha awesome. I once was fooled by the sun, too.
I noticed an unusual high power consumption of several KWh in my logs. They always appeared at the same time, almost up to the same minute.

So it turns out there is a very small time slot where the sun can reach through a window into the hallway. That was enough to offset the light sensor that I attached to the power meter inside the closet. The threshold was set too tight.

Think about the possible sources that influence this 'bug':
- the month
- the time of day
- the weather / state of the clouds
- open/close state of the bathroom door
- reflectivity of the hallway (objects, doors open/closed)
Whoosh! </self>

Yeah, I managed to miss that.
DevOps Metrics That Matter: Anders Wallgren’s Interview on DZone’s Podcast
Insane. That page loads in 111 network requests totaling about 40MB.
That's what I was thinking as well: it'd be really cool if they did some sort of automatic exposure bracketing and combined the best areas of each version since every one of their sample photos generally looks overexposed, especially compared to what Apple's built-in HDR mode would do.
Good point. And actually, Delphi matches many of those bullet points. Expensive, though. (The promo of the free Delphi 10.1 Berlin Starter version just got over on Aug 9. First time in a a while, maybe, since Turbo Delphi Explorer.)
Agreed on the uncanny valley comment. It's interesting to me that very uniform "smile and look at the camera" is the desired outcome of pictures for so many. This page seems to work on the unspoken assumption that the perfect smile in front of some other thing is the ideal picture. I definitely prefer pictures of people doing something other than staring at a lens with a rehearsed smile. It seems that this and so much other camera algorithmic work is aimed at idealizing that posed picture style.
I have heard this as well, it suggests the single most impactful thing someone could build today would be a tool to generate game art cost effectively and quickly.
Not according to this article, apparently.
The Three Most Important Words? 'I Don't Know'
I can agree entirely with this. I used to drink Snapple iced teas like they were water. After cutting back on sugar, I can't stomach the stuff now. I like sweetness: I'll add a splash of lemonade to unsweetened iced tea. But the presweetened stuff is 10x sweeter than my palate tolerates now.
Also, while JavaScript has been a hacky language, ES2015 and ES2016 have really upped the game:

* Classes

* Modules

* Block-scoped variables

* Multi-line strings

* Default parameters

* Template Literals

* Arrow functions

* Promises

* Async/await

And JavaScript keeps eating the world:

"In three months from today, 98% of all Walmart.com traffic will be serviced via Node APIs and displayed with React.js according to Alex Grigoryan, Director of Software Engineering at WalMart Labs. Three months after that, SamsClub.com, Walmart’s second biggest property, will be 100% javascript based. Even their iOS and Android experiences will eventually be done in React Native, a javascript technology that’s made to replace native Java/Objective C coding."
-- https://medium.com/presence-product-group/javascript-and-nod...
I used to think your idea could be a solution but is too slow and also there is an "infinite" input of new corrupt politicians. Doing some numbers will render that trying to vote them out every 4 years doesn't sound like a win. Since we need defence against self-corruption, the source of all evil, the only I can think of is the Non-Aggression Principle and enforce respect for private property https://en.wikipedia.org/wiki/Non-aggression_principle
It's hard to evaluate in terms of a percentage. Is that 99.9% of hours it's fine and the other 0.1% it will plow into something? That means that it will have an accident, possibly a serious one, one every 1,000 hrs. Which is probably about once a year for a lot of people.
The idea seems to be fighting a specific kind of corruption. Congressmen have an office budget and many use invalid or suspicious receipts to justify expenses. The idea is to use bots to analyze and red flag suspicious receipts and then use evidence as proof in justice.
you sir are my hero.
You can give few neat basic commands of basic git usage but many people just nope out after git add -A . and never learn how to actually use it. It's god awful to actually realize that your peers are not capable or willing to do more.
My impression is that this is very similar to the official camera app on Windows, if not a direct port. I would not be surprised if at least some code was shared. Maybe?
It's probably related to their hyperlapse tech, which shared a few people - at least Johannes Kopf and Richard Szeliski. https://blogs.microsoft.com/next/2014/08/11/hyperlapse-siggr...
Part of it is that the bulk of Americans don't travel outside the country. Many don't travel outside their own state.

Americans tend to live near other like-minded people and are afraid of those with other views - both in our own country and outside.

Facebook pushes this filter bubble which we gobble up. It's not an accident, and it has a scientific basis. It's also better for advertisers.

Regarding sex and violence and censorship - I agree it's a little odd. The only thing I can think of is that there are more laws and regulations regarding sexual photos than violent photos. Also, our media also has a history of pushing violent stories. If it bleeds it leads.
Go has most of the machinery of objects, but not the encapsulation. There are no private fields in structs.
I worked on health record software. An elusive bug in the custom SQL Server crypto plugin led to very occasional corrupted entries, which was very bad.

The guy who wrote the crypto plugin had of course quit and nobody knew how it worked.

Fine-combing the C++, I found an off-by-one error that would cause the predicted failures: after rebooting SQL Server, the first entry would get encrypted with a zero key. (Hooray, we could now also fix all the corrupted data.)

For various reasons it would have been difficult to ship new DLLs to the affected customers. Only a handful used this particular crypto and it would be much easier to patch the existing binary DLLs on their servers.

Well... looking at the machine code, I found that the troublesome off-by-one operations were actually in the printable ASCII range... so I just taught my friend in tech support to do a particular obscure search and replace in Notepad++, something like changing ",}" into ",~" in the binary DLL... and then hot-reload it with an SQL Server command... worked perfectly.
Looks like a much lower frame-rate too, like Pix is choosing a specific number of "like" frames and dropping the rest in the name of stabilizing the comp.
Samsung printers are awful, and their customer service is non-existent. They'll have a lot of synergy with HP ;)
What does this have to do with the article? Her criticism is very specific and is about something very recent.
The Pix images just look mostly like the contrast was reduced and all the dark pixels were made brighter. That's not improving the images in my mind, it's just throwing away color depth and subtlety.
Would you feel the same way if two of your neighbors were having a dispute in court about one neighbor's kid trespassing on the other neighbor's property, and the judge decided to order you to pay $2000 because the kid is running through your yard to do it?
> MLton has absolutely no problems inlining functions, even higher-order functions, at compile time

Of course, but how does it know which functions to inline? If you inline everything, then you will blow through your cache.

> What if it's a virtual method call that's known to be overridden in several places? You can't inline it, even if it's in the middle of a hot loop.

That's not true--a JIT could optimistically replace with a concrete realization.

> Runtime information is always anecdotal, specific to one particular run of a program, so...

That's a benefit. No matter what AOT compiled code you have, it is possible to speed up execution if you know what code paths you will take.

> ... for every “optimization” a JIT can perform, there will always exist a program for which the “optimization” will have to be rolled back after it has already been performed, because it turned out to be unsound.

Yes, but so what? As long as it improves performance in the average case, and the worst case is bounded, then that is a net win. You can equally well write deliberately obfuscated code that an AOT compiler has trouble with.

> Language implementations must work correctly whether you write idiomatic or unidiomatic code.

Implementation is correct. Only reflection is slow. If you don't want that, don't write reflection.
One of my favorite talks. I try to watch it once a month.
I think it's a good topic for HN. Even those focused on programming can appreciate the topic of translation between computer languages, which is something that is non-trivial but likely much, much easier than translating between human languages.

This is something I wish we'd been taught in high school, or even college. For the most part, the idea that translation can be highly subjective seems glossed over:

> It goes without saying that translation is an impossible task, fraught with pitfalls, and that the result can never be more than an approximation.
Downloaded it myself and tried it, and the difference is noticeable. I have to say, the result was better than what the default iOS camera app took. The Live Image is hit or miss (it really depends on what you are capturing), but it works.
For (possibly) smaller scale I wrote a self-service SSH CA: https://github.com/nsheridan/cashier
Binary confusion: kilobytes and kibibytes (2005)
Steel-cut oats. Add water and salt, microwave on medium for 12 minutes. Doesn't get any easier, or cheaper.
It's a common sentiment: https://www.herecomestheairplane.co/
I didn't say "high in fibre", I said plenty of fibre. Difference.
Touché though I didn't say it was a bad example. It's a great example, in an adjacent sense, the autobahn is an excellent expressway system.
Keep in mind that this is the VC that said that they should be able to take back the stock of employees that quit. (obviously that doesn't compare to the horrors of Columbus)
I think commonly, processed doesn't mean so much "flour you didnt grind at home", but more "these meats have been ground and mixed with spices and cured" or "they made the speghetti sauce at the factory" or "artificial flavorings and lots of added sugar!".

Not all processing is bad, per se: Factories can make red sauce pretty darn healthy if they want. But what usually happens is that the sauces are filled with a good deal of fat, salt, and sugar along with other things you'd never actually put in food at home (not all of which are bad, but some are misleading - food coloring, for example). They do this because... well, they researched this and found there are 'bonus taste points' if they have the right combination of flavors and feels.

And there is a lot of politics and lobbying to keep the labels more confusing and to use special ingredient names so people don't really know what is in it. Sometimes even when you are trying to avoid something, it is really difficult to figure it all out.

And really, what would probably be needed is some sort of push for healthier processed foods without the weird ingredients. Some things will probably always be bad in excess - cured meats, for example, but we can do better with the others.
I remember this was exactly how a readability service (readability or instapaper or something similar, can't recall now) was attacked. The service allowed you to fetch internal urls and presented them formatted on your phone. A mixture of file:// and internal web urls allowed complete takeover.
The difference is that Scala is a vastly better, designed language. It's not something like Typescript which tries to salvage JavaScript without being able to fix the worst parts.

Scala also has much better, more mature tooling and IDE support.

The build system is also amazing, not the mess cobbled together in JavaScript that is changing every second week.

In addition to that you have stable, existing and mature libraries which work on multiple platforms, achieving _real_ cross platform support. (Not this "if you make JavaScript run outside of the browser..." nonsense.)

Plus, the quality of libraries is so much higher because they aren't written by JS kids with a maximum attention span of 5 minutes.
> It should be clear that changing the [behavior] of the interpreter, even in subtle ways, puts a burden onto anyone hoping to maintain parity in their own runtime, yes?

No, that's not clear. Any changes to the language specification put a burden on the maintainers of interpreters/compilers. Any extra changes to the CPython interpreter do not. You argued that behavior of CPython becomes its own spec, beyond that of Python itself, but this does not seem to be the case. There are a bunch of optimizations that CPython does, like caching small ints, that programmers do not tend to rely on and do not form a sort of shadow-spec for other interpreters.

You might say that dict keys staying in insertion order is more useful than the other CPython idiosyncrasies and therefore will become a shadow-spec, unlike the others. That's possible, but let's consider the risk.

Pythonistas have done just fine without this behavior for a while. There's OrderedDict, but it was added in 2008, relatively late. If there had been lots of demand/usage, I'd have expected it to be added earlier. PEP 372 [0] indicates that use in a metaclass was one of the big motivations, which was only enabled the year before.

When a new Pythonista considers this issue, they are likely to search the internet for discussion and will find commentary on OrderedDict. I expect most will use OrderedDict when appropriate.

The riskiest group would be folks porting code from PHP and Ruby, or other languages that have a core mapping type that keeps insertion order according to the language spec. They'd just expect a Python dict to behave the same way and won't bother to read about it. To evaluate the impact of this change, we should ask how much porting from PHP/Ruby/etc. do we expect to occur, how likely is it that dict implementation will drop insertion ordering in the future, and how much benefit does this implementation provide.

Based on the explanation of the memory and compute savings, this new dict implementation sounds like a good idea.

Also, Ruby made the change in 2009 to the language spec. I'm not an expert Rubyist, but AFAICT it hasn't caused any problems for their community.

[0] https://www.python.org/dev/peps/pep-0372/
> But then you would never be able to take advantage of the power/performance tradeoff that big.LITTLE gives you

Rather: Only applications that don't depend on the invariant that the size of a cache line will stay constant over the execution time will take advantage of this. I can imagine ways how one could increase the advantage, but I don't want to go too much into technical details here.
That 'hit' is equivalent to reducing the carrying capacity of the planet by ~5 billion humans or using 50% of the ice free land mass for agriculture to support them.
The funny thing about all your links is this:

That most people who lost weight most often times gained it back - yet you somehow think gastric surgery is the cure all when you have to make lifelong changes to your diet and lifestyles and be even more diligent in doing so?

The weight loss for gastric patients levels off after 18-24 months, far shorter than the 5 year mark you use to measure success. I'm not sure how you rate one a success in half the time, and total failure for others since they don't meet your magical 5 year mark.

The problem is, you can't legislate freewill - you have to make a choice to be healthy. Is it easy? Nope, but it can be done.

My grandmother was overweight, had high blood pressure and other ailments. She was able to reverse her Type 2 diabetes through diet and staying active by walking 5 miles a day, hiking and other low impact activities. I had a hockey buddy who was on several different medications for high blood pressure, pre-diabetes and other ailments. Within two and half years, he was off the meds and back on the ice through a combination of intense cardio workouts (P90x, Insanity, etc), weight training, and Brazillian Ju Jitsu - which he had always been into. My best friend was depressed and put on a ton of weight, and became borderline suicidal. He was put on meds and continued to put on weight. Over the course of three years he made various (permanent) changes to his diet and to his life. He started with power lifting, then went to mountain biking, then cycling, then adventure racing, then to mountain climbing. Last year I saw him and he was pushing 40; he was still ripped and finally loving life.

You can't make a switch in 6 months and hope for a five year guaranteed return. Shit doesn't happen like that - it just doesn't. You can't go on a diet for two months and hope that 15 pounds you lost will stay off for five years unless you make permanent changes which is really hard for a lot of people. Finding time and energy to start something new is not how humans function. We constantly look for the shortcut. The shortcut to happiness, the shortcut to getting rich, the shortcut to learning some new programming language. Nobody wants to put in the time to get their shit straight, they just want it to be fixed in some nonsensical time frame.

Everybody I know that went through some serious health problems and got straighten out did not do so in any short amount of time - it took years of dedication, getting up at the crack of dawn, struggling and putting the hard work to get there. No diet can do that for you. The payoff is you get 8-10 years back of your life. You can breathe after you walk up a flight of stairs, you can reduce your cholesterol levels and have a healthy heart and lungs. You can get off your medications, or reduce them from what you're taking now. The upside to being healthy so vastly outweighs the downside and here you are saying - there is no hope, you should give up. How does that even sound to someone who's facing an uphill battle?

Unreal.
This is the key takeaway:

> While VC dollars are a significant source of capital for facilitating new business creation, the total capital deployed is remarkably small.

And oddly it gets a disproportional amount of media coverage:

http://avc.com/2016/08/understanding-vcs/

http://www.forbes.com/midas/
I agree with the general point, and I believe it's well-established, that aid can have second-order and higher order effects that are counter-productive. On the other hand, in this case it's merely FUD and an argument for inaction; we would need specific information about Moolenaar's charity. I'm not going to stand still and do nothing just in case.

Second-order effects also can make donations to the Free Software Conservancy counter-productive.

As an aside, I wonder if the Free Software Conservancy would want to be seen telling people not to donate to Ugandan AIDS victims and to redirect the money to themselves. My guess is they would not like to see their name here.

> emotional appeal

Life and death has appeal beyond 'mere' emotion. It's more important than free software, and I say that as an avid fan of, and occasional donor and contributor to FOSS projects.

EDIT: A rewording or two
Wasn't trying to lead you, I was just wondering if there could be another reasonable conclusion. Your answer seems to be confirming my suspicions.
Advanced Behaviours Design Pattern in Automated Testing Part 2
Sorry if the previous response was overly terse, but it seemed easiest to point out what you were doing with your own words. Namely, demonstrating the behavior you're decrying.

Also, how is showing you sentences from different parts of your post being unable to process more than one sentence at a time? If you just wanted to match snark with snark, then fair enough, but as a refutation, it's a bit lacking. Rather, you seem to be making a veiled appeal to authority via having a readership / cult of personality based around you.
I was doing that for years on gas stations, just picked the blue ones. Now that I am more sugar aware, I look at the labels a lot. I was also shocked to see some ridiculous amount of sugar in that what used to be my favourite drink.
I don't understand. Why would NK impeding the deliveries make the US look bad?