Tinker and Alliance are looking pretty shaky in the long term - Tinker just dropped out of a tournament and Alliance was unable to play games of theirs earlier today. It looks right now like they'll soon see major changes, disband, or become one team. Alliance also sponsors a League of Legends team and a few other teams in other scenes though.
I find it rather crazy that "cockpit", an almost brand new project has its entire backend written in C. Not your typical backend language by any means...
Having spend the last week or so working with client certificates, they could be so much more if browsers implemented a proper interface for managing them, or at least a much more intuitive one than they do at the moment. They work spectacularly for building closed APIs where you control both sides, however. They're just a bit tricky for the end user most of the time
The fun thing about Bitcoin is the immense latency in moving money (USD) between exchanges, which has at minimum 4 days of transit. This makes just about anything involving multiple exchanges or high frequency (especially arbitrage trading) absolutely impossible to do without a service such as bitinstant, which is currently MIA
Now I'm just a little bit disappointed I didn't buy any when I first heard of them... But this feels like the same bubble Bitcoin has had twice before - it spikes then plummets, but it plummets to a point higher than the last drop
It would appear that the title may be cut off, as "error message requests" seems like it would be followed by another word - as in, what is it requesting?
Could you use Docker as a backend on Linux? I feel like it would eliminate a lot of the size overhead, and be significantly easier to ship (a single static binary)
If there's any confusion, that's absolutely what I plan on doing - but I firmly believe that if it's kept simple/lightweight that it's more than doable. The GUI portions slightly worry me, but they're not happening until much later down the line
For me, at this moment, it's simply not a feasible goal to learn the ins and outs of a kernel in any reasonable amount of time. And Kirk doesn't just exist as a blog post, I've done a relatively large amount of work on it, but am just now starting to write about it by request of a friend.
Absolutely agree with you. I struggled with wording this for the longest time - and when I talk about OS development, I'm referring much more to the userland development - package managers, core utilities, shells, init systems, and the like, than I'm referring to kernels. Sorry for the confusion.
Arch is my distro of choice at the moment - but even it simply teaches how to copy/paste to make things work, never explaining what is happening when you run a command, or how it manages to do that.
Well, I'm much more interested in the state of the Userland, not the Kernel itself. And since Linux is the de-facto FOSS Kernel, it makes sense to base it around that, instead of trying to port the various compilers/tools that I've used to Minix. It's just easier to do on Linux, but I've tried using the FreeBSD Kernel, as well as XNU - both ended pretty horribly, so I'm sticking with Linux for the time being.
Thanks! There's no problem with them not being configurable enough, the problem is with understanding how they work behind the scenes. The best way, IMHO, to address this, is by starting from nothing, and building it from the ground up - not just compiling things, but writing basic replacements for things like bash, init, etc. Along the way, this gives me room to try new ideas out on a much lower level - rather than just trying to hack them into Ubuntu/another distro.
My biggest problem with iOS 7 is Apple's loss of their attention to detail - several of the animations are broken (multitasking gestures on an iPad especially), and the newer typography turns out to be inconsistent throughout. It was incredibly impressive last night, but the more I use it, the more I dislike it.
I have a AT&T-mvno Straight Talk plan here in the US that costs 45$/month for unlimited data/talk/text - it's vastly cheaper to just purchase the phones outright. Too bad straight talk quit selling AT&T compatible SIM cards a few months ago.
But now they're in control of a hardware vendor - one in a position to allow them to close off WP8 to other OEMs, and potentially a future version of Windows.
3 walled gardens is a very, very bad thing. Couple this with what Google's doing with the new Play Services and Motorola and with what Apple's been doing the entire time, and we could be in for a world of hurt when there are no "open" platforms (as in, for OEMs to build for).
And now Microsoft has a hardware division. I can easily see most hardware vendors being ousted by the trio of Google/MS/Apple - all of whom now either make or have been making their own hardware to go along with their software. And so the walled garden grows...