It's especially misleading because "services" like Amazon RDS and the provisioning systems offered by the big IAAS providers are listed and the self-hosted (+- open source) alternatives don't get mentioned.
One could write a whole essay on the inability of this $4bn company to fix the most basic bugs in their product. I'd love to see evidence of people actually usefully using the features like this that Splunk provides.
I work in the BI / analytics space, with a fair amount of what's called "big data". The security of something like cloud IO is typically not too much of a concern on the kind of projects I work on: more often than not, our clients deploy dedicated analytics databases. Perhaps I'm biased as we tend to work from the outside, but I'd be surprised to find many sysadmins allowing chart IO to connect to the production DB. The ETL process for analytics databases tends to either obscure user data or aggregate it to an impersonal level of detail.
I'm more concerned about the more enterprise-y products aggressively advertising 'enterprise' security features like Active Directory integration, smoothing over their total lack of transparency in vulnerabilities and bugs.
And yet reddit is corporate-owned, being hailed ITT as "the mainstream media", and there's plenty of evidence of senior Reddit moderators showing solidarity for the more criminal subreddits. Defending Reddit's dark side by comparing it to the wild world of message boards and comment sections is disingenuous: Reddit has a pervasive culture of "free speech" at all costs, and this is a consequence of it
Indeed. Nice little sleight of hand where the article reference "mainstream media" and then switches to "mainstream blog media" before citing any examples.
And yet I've met people from Xinjiang and Sichuan who share my feelings about other people and view things through the lens of international solidarity on a personal, human level. What's your point? That the risk of 'white guilt' is a reason not to discard indefensible perspectives like xenophobia and othering?
> Essentially, the financial aid programme is the PyCon
Outreach program - it's the community holding up the
community and making itself accessible at this major
event through these financial grants. It is the very
spirit of the conference; make the information,
knowledge, friendships and connection available to everyone.
Love this. Too often, conferences & groups that are all about 'openness' and freedom don't make allowances like this to actually expand the reach and the appeal. Linux Australia do a good job of this.
Yep, futures can be done easily in Go with a goroutine that sends a single value on a channel, but: 1) you can't dereference the value multiple times in Go, so you have to manage saving it yourself, and 2) there's no syntactic sugar. Pity.
The Arch package maintainers' job mostly boils down to managing the PKGBUILD. If you get comfortable using ABS your experience with Arch will improve dramatically.
It seems weird that large features like dictionary comprehensions and syntax changes like set literals are making it int0 2.7.x, but I'm not complaining - most of my projects are stuck on 2.7 due to deployment environment or library limitations and I'd love to be able to use these features.
The language in the original article had two properties that stood out to me:
* The dialog was entirely unrealistic- to the point that a 'dialogue' was clearly simply the wrong form for what Tomayko wanted to do
* the 'wife' was portrayed alternatively as infantile, naive and purely reactive.
I follow Ryan Tomayko vaguely and I'd be surprised if this was a reflection of his behaviour. From what little I know he seems to have some awareness of and sympathy with struggles that come under "left politics".
But my knowing that doesn't erase the issues with his original post.
My comment on the original posting was thus:
> So Ryan Tomayko's conversions with his wife are akin in tone and style to a language textbook aimed at tweens?
You can't have that coupled with "wife" and simply wave away the problematic implications, not in our culture as of stands today. It's admirable that Tomayko is mature enough to consider challenges like this - instead of just going on the ultra defensive MRA spiel like some Redditor.
A well-engineered UNIX-y "pipeline" is not unlike an impure functional program, yes. Well-behaved processes share no state (i.e. they don't contend over the same files), and messages and data passed over UNIX pipes are immutable, much like data in a functional program.
For example: one system I implemented needs to take a few hundred very large CSV files every day, aggregate and sort them, perform some complex processing on them, and output a result in a very different format to many different output files. It's an extremely complex system, and each component is in Go, performing a specific task, e.g.:
* combining the many source files
* cleaning the source files
* performing some aggregation on the stream
* splitting the stream into many parts that other components can read from in parallel ('named pipes' in unix make this very nice)
* splitting the stream into many output files
etc. Every component is dumb and does one thing, but a single controlling program is responsible for handling command line arguments that describe the overall outcome and setting up the stdin and stdout stream of all of the components to create the final result.
There's a beautiful simplicity to systems implemented like this, and it means you can take advantage of existing tools like grep, awk, sed, sort, cut, etc. to do a lot of the heavy lifting more reliably and quickly than you could probably implement yourself, while still coding the overall system at a reasonably high level of abstraction. Go doesn't lead to this approach directly, but it's very pleasant working with it as a citizen of this wider environment.
> Meanwhile, Go isn't a platform, nor is it trying to be. Its designers (Rob Pike and Ken Thompson) already made the platform, first, a long time ago. It was called Unix.
This is great, and I think many of Go's advocates - including devs at Google - underplay it. I don't understand why, particularly given the pedigree of Pike and Thompson.
My approach to building large systems in Go is based around processing pipelines, and tries to be as UNIX-y as possible. The interface types in the io package particularly fit the everything-is-a-file model, where processes can do one thing well while having their inputs and outputs connected to pipes, files, sockets, named sockets, devices, etc.
In short, building complex systems with Go components has made me a better UNIX programmer, a level that I could never quite reach in C due to all the distractions of memory management and unsafety.
I love seeing the source for such elegant single-purpose projects like this. I'm in the middle of writing my own static site generator for Python; it's a bit more feature-rich, but it's up at something like 800 LOC for the minimum feature-complete implementation. Great to see evidence that I have a long way to go..
Anyone care to give a very cursory run-down on why someone would look at Minix in this day and age instead of one of the BSDs? Particularly since those release notes mention bringing in the NetBSD build system and much of its userspace.
Not to say that I think it's bad to have plenty of unixes floating around - just curious.
Agreed. The way I tend to use the repl in clojure is just to code up a script in vim and then %Eval the whole thing. Editor plugins for Go could compile-and-run, and know stuff like the working directory and the gopath, which could get you a bit closer without having to build a real REPL.