wesleytodd

Laughed out loud at this. Thanks :)

And if you live in Michigan, his syrup is used in this Bloom kombucha sold at Meijer.

See my other comment, a friend of mine sells it: https://news.ycombinator.com/item?id=17126881

A few years ago a friend of mine started importing this stuff. He got a sample of a syrup made, and then started selling it. It was a slow start because he was just one guy and had other interests, but then I remember when he told me that Starbucks was starting to make a seasonal cascara drink.

Seeing this just reminded me how often it is that opportunities for little startup's are missed because the founder was unable to commit fully at the time.

Plug for him, here is where he was selling it: http://www.inspiredcoffee.com/

Web applications as we write them today are largely centralized systems with centralized ownership of data and small groups of people owning the lion's share of the traffic/data/user attention etc.

Beaker and dat are built on the same base protocols as the traditional web (tcp/udp), but also add higher level protocols for changing the centralized power dynamic I mentioned above. The key, IMO, is that there is a good story for users around transitioning from the centralized web into the decentralized web because of the shared foundation.

I see the confusion. When I say "foundation" I mean how we build applications, not the underlying protocols. Maybe I should have said "foundation of web application design", or something like that.

Yes, the data is owned by you and signed for ownership attribution. AFAIK there is no "remove my data from the network", as it is a public network.

You should also check out Beaker Browser. It is a browser built around the dat protocol. Really great community and even has a few decentralized social networks already.

https://beakerbrowser.com/

IMHO it is the best bet for actually changing the foundation of the internet back to a distributed model.

Just stop now and give your money to Beaker Browser

https://beakerbrowser.com/

Thanks for the good work on GitLab, I tell everyone I can how great of an experience it was to use it at my last company. The CI integration was GREAT, the ui is pretty nice and the maintenance overhead was minimal.

I completely agree with your assessment.

I watch a fair bit of pro play, and also play enough to bounce between low diamond and high platinum on NA. It is almost always my macro that wins or looses games.

Most people at my level wouldn't even have consistent enough play to be able to notice the difference between well and poorly micro'd games. But if they miss an upgrade, or build the wrong comp, or worse, don't expand, that is the win/loose for 98% of games below masters.

Which all around sucks for me, because my micro is on point :)

Funny enough, after I posted this as a joke I realized this is exactly the kind of thing an AI would be incredibly good at finding. It makes it all that much more impressive seeing Buyn do it.

But can your AI learn to drop mules so it can capture some escaping ultras?

Better link: https://clips.twitch.tv/BusyDrabFennelRedCoat

Better link (non amp version): https://www.bloomberg.com/view/articles/2018-03-16/decline-i...

Re-writing dependency source files with another dependency is a much worse idea than vetting your dependencies before you add them to your project IMHO

Agreed, but the tools (nsp) are there to make it simple to know. Devs who are not going to update/patch are not the target here, so making big claims like this does not strongly add to the conversation IMO.

Also, this is nothing new on the web, the amount of wordpress sites with known voulns is probably MUCH higher.

NOTE: I am NOT saying we have had no security voulns. Just that the snyk and nsp disclosures on packages do not mean that those applications are vulnerable.

We run nsp on our production services in CI before merge. The number of false positives I have tracked down is infinitely higher than the number of vouln's found. I literally mean this, we have never seen one disclosure which resulted in a viable attack on our production services.

For example, recently a bunch of ReDOS voulns were reported in popular libraries. None of which were in code paths hit by our configurations.

So needless to say, I think this is a sensationalist headline.

This has nothing to do with Go and a lot to do with choosing the right tool for the job. Maybe Go is the best tool for you in this job, but a given js framework can serve someone else just as well if it is in their expertise area. Don't confuse your expertise with language/ecosystem pros and cons.

I just recently learned you can hide retweets from your timeline for an individual user. I don't think you can turn off the likes, but that would be a good addition.

I feel more focused while standing. I am also the type of person who needs at least a little action going on in the background to really get in the zone (like at a coffee shop).

I have been standing primarily now for over a year and even converted my home gaming computer desk to a standing desk. Yep I stand while pc gaming...lol.

It really helps me feel better, back issues aside, because I feel like I am moving more. Even just the switching feet position.

The only advice I have is to get a good padded mat. I started without one and it was painful on my feet and legs.

If you are interested in a series of fantasy novels with a similar order/chaos mythology, I recommend the Saga of Recluce.

https://en.wikipedia.org/wiki/The_Saga_of_Recluce

I have been reading the ["The Vorkosigan Saga"](https://en.wikipedia.org/wiki/Vorkosigan_Saga) and one of the consistent themes is the "Uterine Replicator". Sounds very much like what this could become in the future.

Not only is this book series great and very entertaining, I think it tackles some technology and social ideas that others in the genre do not.

I do not understand the amount of negative feedback on this. It seems logical to me to move the underlying open source components to a separate org from the proprietary stuff. Why the hate?

Updated :)

I think the subjectivity of this kind of data ruins any value in statistical/scientific analysis.

For example, my beer taste developed while I lived in Michigan. The craft scene is more spread out there, but there is a ton of high quality IPAs, Stouts and Porters being brewed in the metro Detroit area.

Now I live in Austin, and the beer here is crap in those categories, but stronger in the Pilsners and Pale Ales. When people down here rate breweries, it is usually much more focused on those categories, thus putting Austin at #13, even though it is trash compared to a Dark Horse, or a Dragonmead, in the "harder to do right" categories. It's just that they don't know any better.

EDIT: But aside from that the presentation was nice, and well executed

EDIT 2: "Pale Ales"

As much as I agree with the performance side here, I believe the usability for devs is an important factor. Let the users who really need that last bit of perf opt-in, and let everyone else just go along in blissful ignorance. And I am honestly alright if "opt-in" means use preact or some other project.

Think about the reasons jQuery and WordPress were popular, despite performance issues, they JUST WORKED for people. React is the jQuery of vdom projects, don't try to make it the something it is not.

Well thanks then! I know social media sucks for this kind of stuff. And I am sorry for my contribution to that. And know we really all do appreciate it, we are just passionate and opinionated people.

Personally I am more concerned about keeping my team building cool features than updating react. This has led to us having two distinctly non-interoperable code bases, one with react 0.12 and one with react 14-15. This makes me worried that now we will have a third with react >15.

I think we can all agree that many of the ideas, while not new, were revolutionary to front-end web developers. And that is what I love about working in this stack. But other than these ideas, the projects themselves are just stumbling along trying to catch up with some perceived "modern" way of coding, and it is the dev teams and projects that suffer.

I agree, I am really concerned about this change. But unfortunatly I do not think my feedback via twitter was well taken: https://twitter.com/wesleytodd/status/850550711804989440

EDIT: I should add, that I didn't want to say that I completely disagree with the change to remvoe this api entirely on twitter to the maintainers. I am sure they get enough crap from people.

Yeah that is what they were talking about when I was following the project. Once that is done in patchwork, I might try using it again.