vruiz

15 ms·

91.
by vruiz 9y ago
simplesurance GmbH | Berlin, Germany | Onsite, Full Time https://www.simplesurance-group.com/ We are building one of the world’s leading platforms to make insurance accessible. Since 2012, we are proudly “Made in Berlin”: w
92.
Russ Cox announces plans for Go 2(twitter.com)
4 points by vruiz 9y ago|1 comments
93.
by vruiz 9y ago
simplesurance GmbH | Berlin, Germany | Onsite, Full Time http://www.simplesurance-group.com/ We are building one of the world’s leading platforms to make insurance accessible. Since 2012, we are proudly “Made in Berlin”: we
94.
by vruiz 10y ago
That's how we started back in the day. It works but setting up everything and doing the rebase/commit dance to update can be quite cumbersome when you have more than a couple dependencies. Nothing wrong with it if you are willing
95.
by vruiz 10y ago
The go toolchain doesn’t but many of these vendoring tools do something similar. But you still don’t want to depend on the origin repo being up and have missing/altered repos break your builds.
96.
by vruiz 10y ago
> What's the reason for yet another utility? > Some copy the source code of dependencies into the vendor directory: I don't agree with any of the stated problems there. Unless you are building a library you should commit you
97.
by vruiz 10y ago
It's actually both, and a file system.
98.
XO: Generate Go types and funcs from a database schema(github.com)
5 points by vruiz 10y ago|0 comments
99.
State of PHP-FIG(groups.google.com)
2 points by vruiz 10y ago|0 comments
100.
by vruiz 10y ago
I have similar worries with kafka, that’s why I’ve been working on and off in my own log based message queue for while now [0]. So far is nothing but a humble beginning to something targeting very simple use cases, but AFAIK there aren&#x27
101.
by vruiz 10y ago
For those who like to watch talks, I found one on youtube: https://www.youtube.com/watch?v=QW1OEQxcjZc
102.
Running an Experiment in the IBM Quantum Experience [video](youtube.com)
2 points by vruiz 10y ago|0 comments
103.
by vruiz 10y ago
> There was one fundamental mistake made, however, which is that we shouldn't have used channels. > they make it very hard to prevent message loss. If unbuffered channels are used everywhere, performance plummets unacceptably due
104.
Experimental support for HTTP checks in ping.gg(news.ping.gg)
1 points by vruiz 10y ago|0 comments
105.
Go 1.7 freeze announced(groups.google.com)
91 points by vruiz 10y ago|20 comments
106.
Control, monitor, and instrument your React Native apps from your console(github.com)
2 points by vruiz 10y ago|0 comments
107.
by vruiz 11y ago
> you should expect a few "surprises" if you're running consul.io on Digital Ocean, heartbeats are delayed quite often (depends on datacenters), which makes failure detection hard isn't that true for any CP store in a
108.
Harbor: Enterprise-Class Container Registry Server Based on Docker Distribution(github.com)
1 points by vruiz 11y ago|0 comments
109.
by vruiz 11y ago
I really like GitLab, we use it and they follow the business model I wish GitHub had. But as they become bigger and bigger I have to wonder how much longer until they start antagonizing GitHub with these feature clones, and who should have
110.
New KBO might add more evidence of Planet Nine's existence(theverge.com)
1 points by vruiz 11y ago|0 comments
111.
Public Lecture with Google DeepMind's Demis Hassabis(youtube.com)
3 points by vruiz 11y ago|0 comments
112.
by vruiz 11y ago
Having the capability does not imply having the permissions.
113.
by vruiz 11y ago
I want to agree with him, I'd like to see a future where WebAssembly closes the gap between native apps and the web. For better or worse browsers are the new OSes, and I dream of a future were all vendors come up with the equivalent of
114.
by vruiz 11y ago
Indeed, I remember perfectly well how "die of success" was a thing when sites that became popular could not keep up with the hosting costs.
115.
by vruiz 11y ago
I'd like to believe you, but what kills people is not their age, today it's mostly cancer and heart disease. While I'd hope we'll make progress, I doubt those 2 will be just gone in 30 years.
116.
by vruiz 11y ago
> I'm interested in why LLVM was disqualified. They simply used what they knew best: > If step one had been "learn the GCC or LLVM toolchains well enough to add segmented stacks", I'm not sure we'd have gotten
117.
by vruiz 11y ago
I've seen similar services for higher fees. But opening a US bank account without visiting the US? That I have not seen.
118.
by vruiz 11y ago
This almost seems too good to be true. What's the catch?
119.
by vruiz 11y ago
http://www.blevesearch.com/ It has an very long way ahead to catch up with Lucene, but it's a very promising start.
120.
Vault 0.5 released with keybase.io support(hashicorp.com)
1 points by vruiz 11y ago|0 comments

More ›