A missing piece of information is that trehalose is a rather new additive. It was very expensive to manufacture until about 20 years ago when a new cheaper process to make it was found. And voilà, because it appears safe and is somewhat useful, it starts showing up in all sorts of products without any labeling indication. And the fallout is just now being noticed. One of the commenters used the phrase "food science" ... hah! We're the guinea pigs!
Not missing. In paragraphs 5 and 6, the article explains how, just before c. diff infections started to get more common, a new method for producing it that dropped the price by over 99% was developed.
> With tinkering, syrup scientists at Japan’s Hayashibara chemistry company finally figured out a novel enzymatic method to make it on the cheap from starch. The method brought costs down to just $3 per kilogram. By 2000—just before the rise of C. diff.—the company got approval from the US Food and Drug Administration to use it as an additive in food. Approval for use in Europe came the following year. Manufacturers started pouring trehalose into a variety of foods, from pasta to ground beef to ice creams.
We really are the guinea pigs. The supplement and sports nutrition industry can essentially mix whatever sounds good for marketing and throw it over the wall.
Grade level schools, adopted in the USA in the middle of the 19th century, essentially dumb down those who are a bit more advanced at an early age. It takes a few grades to destroy the good work of parents preparing their preschoolers, but the playing field has pretty much been leveled by 3rd grade. :(
The Swift support on Linux is the bare minimum required to say "Swift supports Linux". I seriously doubt that Swift will ever be any more "portable" than Objective-C. That is, Swift, like Objective-C, is portable in theory, but nobody uses it for anything except to write programs for Apple's iOS/macOS platform.
No you are not the only programmer who thinks that languages are going in the wrong direction. For example, the lambda operator of Java 8. All it does is hide the (very useful) name of the method being called. I'm forever having to look up the definition of some arcane single method interface to ascertain the method name so I can have a clue as to what the -> operator is doing/calling. :(
Wait what? In context of the typical usage of lambda expressions, the method name does not matter at all. I mean, what difference does it make to you that if it's a Runnable the method is called run(), if it's a Consumer the method is called accept(), and if it's a Function the method is called apply()?
OTOH the usual, pre-Java-8 way of allocating anonymous subclasses when you mean to pass a function is at best obscuring the meaning of your code...
Hah, I agree with your resentment about the recent wave of "serverless" :)
By now redis has been replaced with native IPFS pubsub, which is provided by both go-ipfs and js-ipfs. The only remaining server-ish is some means of bootstrapping, i.e. entering the network.
I'm not sure how up-to-date the readme is, but the demo (orbit.libp2p.io) is out-of-date and still uses redis pubsub. I pinged @haadcode, who can go more into detail.
Are you familiar with IPFS pubsub? Would you be able to link some information about the implementation/usage?
I'm quite surprised to hear what you said. I've been following multiple Github Issues on IPFS pubsub, and none of them (that i followed) announced success/etc. I thought it was still in the planning phase.
There is some prototype work done in master already (if you build go-ipfs from source).
$ ipfs pubsub --help
USAGE
ipfs pubsub - An experimental publish-subscribe system on ipfs.
SYNOPSIS
ipfs pubsub
DESCRIPTION
ipfs pubsub allows you to publish messages to a given topic, and also to
subscribe to new messages on a given topic.
This is an experimental feature. It is not intended in its current state
to be used in a production environment.
To use, the daemon must be run with '--enable-pubsub-experiment'.
SUBCOMMANDS
ipfs pubsub ls - List subscribed topics by name.
ipfs pubsub peers - List all peers we are currently pubsubbing with.
ipfs pubsub pub <topic> <data>... - Publish a message to a given pubsub topic.
ipfs pubsub sub <topic> - Subscribe to messages on a given topic.
Use 'ipfs pubsub <subcmd> --help' for more information about each command.
Wow, thank you! Very interesting! Quite odd that none of my follows mentioned this going live, must be an issue of too many github issues.
Time to dig into this a bit!
edit: For anyone else perplexed and surprised by me, seems `floodsub` is their moniker for the new tech, and it was (in part) merged in here: https://github.com/ipfs/go-ipfs/pull/3202
This is really, really cool! Also, if this implementation is robust and performant, this is huge for IPFS.
Yes we haven't been very vocal about it yet because it's not yet part of a go-ipfs release -- it'll be in the next release, go-ipfs v0.4.5.
Note on the name: floodsub is one specific implementation of pubsub. There are many ways to do pubsub, and we chose to go with a naive and simple flooding implementation for now. In the future there will be more, and you'll be able to use different implementations simultaneously.
Because IPFS only does distributed storage. It has no processing power or logic to handle data transformations.
Now, one avenue to handle that is js-ipfs. In order to update things like IPNS records, you need the private key of the node you're trying to change. Interestingly enough, and machine with the pub/priv key can submit an IPNS change.
So effectively, you could have a shared repo like Usenet, where everyone has the pub/priv key and pushes updates via js-ipfs. Although, I could imagine easily how that could get super-heavy.
_________________________
Another idea I had, was to build something akin to AWS lambda, except using Tor Hidden Services, and Erlang. It would be effectively a private computation cloud. The reason for the HS is so each machine, regardless of their location, could always talk with each other, using Erlang's built--in networking support. (I am using non-standard applications of Tor Hidden Services - read more what I'm doing here: https://hackaday.io/project/12985-multisite-homeofficehacker... )
That's very cool! Have you looked at OnionCat? I've managed a global LizardFS cluster on a PeerVPN network, overlayed on OnionCat IPv6. Latency is too high for erasure coding or XOR goals, but chunk-replication mode works reliably.
redis was mainly used to get pubsub for the first iteration (demonstrated in June), now (demonstrated in September) orbit uses IPFS pubsub (available in the go-ipfs implementation) for a complete distributed web application.
The headline is false. Far down in the article, find this nuggest:
"The profit landscape is less sunny. Operating income for Walmart’s United States stores was down 6 percent in the most recent quarter, reflecting higher labor costs and other new investments."
And while employee headcount from 2008 is mentioned, there is no mention of the number of employees who have been let go to allow for paying high wages to the remaining workers.
This article is yet another example of how the NY Times is a well-disguised propaganda arm of the Democratic Party.
Sales and operating income are two different metrics. The headline is not false, it just doesn't say what you want it to say.
Paragraph 10:
"The results are promising. By early 2016, the proportion of stores hitting their targeted customer-service ratings had rebounded to 75 percent. Sales are rising again."
Maybe the person you reply to was confused by the original title in HN, which was "Walmart generated higher sales, profits by paying workers more, better training" (that's not the NYT's fault, tough).
