Love to see this on the Steam Deck.
94 karma · joined January 29, 2009
Another problem I have with it is civil rights (I believe in them).
21st Century C - Ben Klemens http://www.amazon.com/dp/1449327141/?tag=stackoverfl08-20
You asked about "Modern C" and that caught my eye. Most instructional resources on C focus on facts about C without putting them into perspective as to which C era they belong to. "21st Century C" takes an explicitly modern perspective, is opinionated as to which aspects of C you can postpone or ignore, and provides updates for people (like me) who have mostly been familiar with K&R or C89. I found it a really fun read and would definitely recommend it as #1 for your question about "Modern C".
As to if you should learn C, I am super opinionated but I think C still has a lot of value, even for someone who doesn't describe themselves as "full-stack". The reasons are obvious: the kernel is written in C, libc is written in C, the webserver serving your web application is almost definitely written in C, but if it isn't, the compiler that compiles the language it is written in is almost definitely written in C (hats off to Golang for getting off their C compiler). Despite its flaws, I love C.
As patio11 notes, this would not at all be excessive as a response to the threat model, but even with an aggressive key rotation mandate, this still doesn't make your production infrastructure as secure as your corporate Confluence wiki with SSO. Your employee's private key is still a static credential, and any rotation policy (14 days? 30 days? 90 days?) will leave a significant window for an attacker to use a stolen credential. Additionally, using a single key per employee for all infrastructure access magnifies the attack surface of a stolen credential to everything you operate.
Full disclosure, I'm a co-founder at ScaleFT, a startup focused on solving these sorts of problems. We're releasing a patch to fully mitigate this for our users this morning.
I'm also one of the founders. We all have extensive open source experience, have grown up in open source communities, and love open source. We're not committing to 100% open source yet. We'll be pragmatic.
We all want to open source as much as useful to the community, rather than just a code dump. This will probably look like open sourcing the individual libraries we use to build the client, rather than a single open-but-monolithic client. The client is written mostly in javascript[1] so we'll be publishing modules on NPM when the modules we need don't exist already. I think we'll need to build a Go client library pretty soon also. So, for the purpose of code re-use and learning, we'll be open source.
I'm sure we'll also be sharing the complete source for the purpose of security audits. If this is your concern, the answer is Yes, we'll let customers see the code they're relying on for their infrastructure.
Hope that helps!
rch
Worrying about this a decade or two sooner would've been more timely. The city changed dramatically from the late 90s to early 00s. We had a lull in change during the macroeconomic recession, but now the machine is getting back up to speed.
I've been increasingly sad over the years as my friends who are artists, librarians, dancers, therapists, social workers, statisticians, teachers, writers, musicians, accountants, anything other than software engineers, have been falling away from the Bay because it is just so expensive.
Rapid growth can apparently kill anything. IMO it's likely too late to do anything for San Francisco. There's still time to worry about Oakland though.
We're the product Cloudkick grew into after being acquired. We love to collaborate with peers and make things for people who make things. We want to build the monitoring tools we've always wanted. Come join us and write code every day in Node.js, Java, C, and Lua.
More info: https://uscareers-rackspace.icims.com/jobs/10925/software-de...
People bringing their protests to Oakland is nothing new (like the black bloc protests during Occupy). I've been living in my Oakland neighborhood for about 9 years. On my block, that makes me the newcomer. I don't speak for Oakland and neither do these protestors or whoever contributed that article.
A. Run a pre-existing routing program on it, such as http://wiki.openstreetmap.org/index.php/Rana, or
B. Write your own (which would require knowledge of algorithms such as http://en.wikipedia.org/wiki/A*_search_algorithm)
There are also services where people do these things for you, and for low volume, they might not mind if you programmatically scrape their results. A good example is http://www.batchgeocode.com/
Properly, Rana isn't intended as a package for programmatic access, but it does include code which does what you want:
* http://wiki.openstreetmap.org/wiki/PyrouteLib - Pyroute is probably exactly what you want.
* Rana's routing module: http://wiki.openstreetmap.org/wiki/Rana/Modules#route
I'd love to see a book of this nature concentrated on the Civil War.