sarnowski

14 ms·

91.
by sarnowski 12y ago
> its like clojure core.async only more powerful. Can you explain why its more powerful than core.async?
92.
by sarnowski 12y ago
http://harmful.cat-v.org/software/dynamic-linking/ ..comes to my mind. Shared libraries and their advantages are at least.. controversal.
93.
by sarnowski 12y ago
Since we (Zalando) are heavy PostgreSQL users, we also had the need for monitoring and part of the result we came up with is http://zalando.github.io/PGObserver/ and https://github.com/zalando/pg_v
94.
by sarnowski 12y ago
>> ... `setq` though (a feature not present in Clojure... I am not familiar with elisp but from first google result it reads that the equivalent is alter! / swap!.
95.
by sarnowski 12y ago
At some point most applications have to have some state. Most clojure projects are nice functional libraries that work without state but somewhere are one or to refs (or atoms). A good example is Datomic where Rich Hickey said, it only has
96.
by sarnowski 12y ago
Someone mentioned the JVM interop of Clojure is it's main selling point. While its definitly awesome to have that great integration (I'm a heavy interop user), for me, the main strength is having persistent data structures at its
97.
by sarnowski 12y ago
IIRC stackless python implemented microthreads and channels before go existed - thats the whole point of stackless python - so whats the benefit here on top of that? http://www.stackless.com/wiki/Tasklets http:/&
98.
Canvas Fingerprinting(securehomes.esat.kuleuven.be)
3 points by sarnowski 12y ago|0 comments
99.
Inside Snowden's Germany File(spiegel.de)
17 points by sarnowski 12y ago|0 comments
100.
Bpmn.io releases first preview of JavaScript bpmn library(bpmn.io)
1 points by sarnowski 12y ago|0 comments
101.
by sarnowski 13y ago
Because now your command isn't /path/ independant. The original assumed you downloaded the patch to your current directory and you can just copy&paste this command. Your example requires me to modify your line making this
102.
by sarnowski 13y ago
I suggest looking at LinuxFromScratch[0], especially II.5. It's hard to do a "real" cross-platform compiler because your target system might not only be a different architecture but also has different libraries on the system
103.
Microsoft Lync gathers data just like NSA(m.networkworld.com)
1 points by sarnowski 13y ago|0 comments
104.
by sarnowski 13y ago
Agree. I keep telling that container may provide some benefits but its really not security (especially docker which uses LXC which is still not complete und as you said uses a shared kernel - one plus point is Ubuntu's combination with
105.
by sarnowski 13y ago
For the end user this means: different command line parameters for commands; more consistent userland; consistent documentation; less drivers; slightly less applications
106.
by sarnowski 13y ago
This is true for me too as long as I don't use OpenBSD. The cause is that GNU/Linux manpages are horrible. They are mostly outdated and not in sync with the versions that are actually installed. As soon as you log in to your newly
107.
by sarnowski 13y ago
The "change-port" discussion for SSH is so boring :-/ OpenSSH is I guess the most secure daemon on all your servers. People should more think about to change the HTTP(S) ports of their non-public facing sites and other daemon
108.
by sarnowski 13y ago
Do you have a link for this statistic? Since I don't know of a local root privilege escalation since several years in OpenBSD, this is a quite high mark. Edit: this is not a os-or-vm problem. You will have local problems and now, in ad
109.
by sarnowski 13y ago
> Docker (and LXC) seems like a huge step backwards for security. Sry but link says it all. No further comment from me: http://marc.info/?l=openbsd-misc&m=119318909016582&w=2
110.
It's done: camunda BPM 7.0.0-Final released(camundabpm.blogspot.de)
1 points by sarnowski 13y ago|0 comments
111.
NSA spied on UN, breaking active agreements(spiegel.de)
70 points by sarnowski 13y ago|20 comments
112.
by sarnowski 13y ago
FreeBSD jails already provided those containers for over 10 years. Even chroot is some kind of container. http://en.m.wikipedia.org/wiki/Operating_system-level_virtua...
113.
by sarnowski 13y ago
Refreshing to know that even settled projects have those same problems at their core. Depending on upstream developers is always a big risk you have to calculate well. Was always a pain and only gets bigger in our agile *aaS world.
114.
by sarnowski 13y ago
You have to have your main() in package "main" and all your files in one directory have to be in the same package. So when you want a main() and your logic in a "real" package, your have to seperate them.
115.
by sarnowski 13y ago
Please see my comment to your parent. Additional hint: you should also care about dropping/controlling your user's groups, see https://github.com/sarnowski/mitigation/blob/master/mitigati...
116.
by sarnowski 13y ago
WARNING: I implemented a tiny library for that in go a while ago. Go under Linux is not safe! Linux is not posix compliant and only sets the IDs for the current thread. Go almost always spawned more threads before initializing your code whi
117.
by sarnowski 13y ago
In fact, since go does not have explicit constructors, it encourages the factory pattern all over the place. You'll find static factories everywhere in the go library. http://golang.org/doc/effective_go.html#compos
118.
Camunda BPM 7.0.0-alpha6 released(camundabpm.blogspot.de)
1 points by sarnowski 13y ago|0 comments
119.
by sarnowski 13y ago
The perception of OpenBSD's usage was always low. OpenBSD was always about network infrastructure and simple, super solid servers. It's never something you write blog posts about because of fancy bleeding edge setups. The chance is high tha
120.
by sarnowski 13y ago
This. OpenBSD clean and simple design makes it a breeze to maintain. It's documentation always tells you the whole truth and for most tasks, its so intuitive that you almost always already know where to do your stuff.

More ›