grundprinzip

To make sure that resources are compliant I would suggest using AWS Config Rules as they allow to specify for example that tags need to be applied. Validation of resources is done in a lambda function which should in theory allow to terminate the resources if they are not compliant.

Containers are just namespaces, mount, user, pin, and network namespaces.

The reason why chroot is not enough is that you want to allow a different pace of using certain dependencies is different applications. In a way its similar to how Mac OS packages applications as they all ship their own prefix root so to say.

Luckily, Trump is going to make America great again and will keep all those manufacturing jobs where owners don't like to pay minimum wage because they can't afford to pass on the raise because nobody wants to buy cheap apparel at this price point.

While I understand why the author is complaining, he should much rather complain to all his potential customers that make a purchase decision based on price instead of ethically supporting american workers.

I'm really waiting to see all those voters spend significantly more on "Made in Great America" apparel to make sure to keep all those jobs...

John McWhorter: Words on the Move: Why English Won't - and Can't - Sit Still (Like, Literally)

It's not a product for storing data and then accessing it via SQL. It's a data analysis tool similar to Tableau.

What I found interesting is that the two high profile projects mentioned in the post written in D are no longer maintained, which is kind of weird.

Totally agree, in the paper they only look at competitive programming contests. Ideally, it would be interesting if the same could be applied to a larger code base with more authors and if it's possible to find a particular author in such a code base.

Anybody knows if there is support for LLVM IR code as well? What would be good alternatives here?

Something that is (typically) left out in these articles about how expensive rent in SF is, is that even for tech folks with rather high income the city becomes too expensive as soon as you have family. It might be ok to pay 2.5k per bedroom when you're single, but when you pay an additional 1.5k per child in daycare perspective changes.

In my opinion, if the trans-bay (e.g. Oakland to San Mateo) and around-the-bay (Berkeley - SJ) public transport would be reasonable in terms of time, things could normalize easier. It could take some pressure of the rent market as more opportunities could be found in other places.

I'm not sure, but the assembly code generated when using __builtin_expect looks almost identical.

I think the biggest challenge is compilation time. With the lack of incremental compilation modifying more complex classes can result in long compilation time. Same is true for modifying templates that are widely used within the code base.

If you look for example at runtime compilation of queries in database systems, compiling can take significant amount of time, at least enough so it doesn't feel instant anymore.

To get incremental compilation, one would need fully dynamic dispatched invocation which would be probably horrible slow.

This said, I'm a strong believer in runtime code generation, just with a reduced scope rather than full c++.

./build/cmake/target/fnordmetric-server --http_port 8080 --storage_backend mysql [ERROR] unknown backend type: mysql

Looks like a tool I need. Unfortunately, it looks like the MySQL backend is more a promise than reality.

Nice work, though I liked the dataref package even more!

I really like your above example. For people coming from Ruby on Rails or Python Django, such a notation makes it simple to understand what the code will do, even without knowing how to implement it.

Thanks

The soundtrack is really awesome and fits perfectly!

I don't know why, I find this post greatly uninformative. Yes, you can have some kind of Vim mode in Emacs (as you can in Sublime) and yes it takes time to remember key-bindings. If you have years of experience in Vim, why would you expect to get used to Emacs keybindings in a short time?

It's like moving to a foreign country and then continue to buy and to eat only your old local food, and go out and talk to only people from your old home. You will miss so much.

I think there is something missing in the discussion of the article: Shared pointers are used for shared ownership, where in the example the author is assuming unique ownership.

In the benchmark this requires the compiler to generate code that makes sure that the object was not changed by issuing an exclusive request for the data plus the additional pointer dereferencing.

To check what is really happening I recommend two things:

1) Look at the generated code and see what the compiler issues. 2) Compare object* vs shared_ptr<object> 3) Compare unique_ptr vs object vs object*

My assumption is that unique_ptr will be faster than shared_ptr and have the same speed as object* and that will be a bit slower than object.

In general, I would say you want to have schema. However, both yaml and json lack this. Still I find this a nice approach.

I have to admit that for a moment I thought: awesome, there is a built-in cache feature now for the llvm compilers and it took me almost a paragraph to recognize that the author was not talking about compilers....

It's only the necessary income to afford the mortgage. The media house price was listed as something like 600k.

For CS I did it almost like that: Typically you write papers in LaTeX which means you need a correct Bibtex entry, and correct means its better be curated by someone else. Since most of the relevant CS publications are in DBLP [1] I wrote a small script that scans missing citation keys in your LaTeX file for actual DBLP keys and automatically builds this into a bibtex file that you can use [2]. If you integrate this command in your regular build cycle for LaTeX using for example latexmk manually maintaining bibtex files is a thing from the past.

[1] http://www.dblp.org/search/

[2] https://github.com/grundprinzip/dblp

"rr currently only supports x86 32-bit processes."

While the idea of a replay debugger is really nice, I don't understand where this limitation comes from. I thought, that since years we practically live in a 64 bit world.

It's not a question to keep my DNA confined, but rather making it random. If somebody wants to track my DNA, yes they can do that - here in Switzerland, far away - but I wont send it to them on a silver plate.

What I don't understand is: People use 1Password etc to generate arbitrarily secure passwords for Facebook but agree on sending their DNA password (even though its 1B chars) on a postcard to a company (with unknown security credentials and intentions) just to know that they are 29% east-european and probably sleep better at night. Sigh...

Actually, this was irony, as all the systems that I have currently deployed run a classical Linux stack and I would have to think a long time to start deploying a .NET / Mono app if it's worth the integration effort.

Easy to deploy as it's written in C# :)

I totally agree that cloud storage for photos is mostly broken but how does this help me with cloud storing the photos of my DSLR, a compact tough-cam, 2 Android phones? Any chance to keep Lightroom for developing the pics or is it a iPhone/iPad only photo backup solution?

You are just sounding like the prototypical PhD / Post Doc that tries to convince everybody that their work is the hardest and if they don't put in the 80h/week humanity will fail.

Every science has it's own merits and problems and we CS people do not only sit on the couch and drink coffee before we hit back on some brogramming and getting the next 10^9$ from Facebook.

Even if not all of the aspects that she wrote about may related to everybodys problems, it's a very good read because it allows to relate to her situation. Being a post-doc in CS myself and having two kids I exactly know how hard it is to juggle everything. In addition, I think that many of the comments here try to interpret the article as a list of advices and treat them as such. But If you read carefully you would have seen that this is especially something she didn't want to.

My key take-away from this post is that: Yes, the system is designed for young, childless PhDs who are willing to put 80hs/weeks into work and robot-like follow the advice of others. But, it does not have to be like that. It's paramount to remember everyday why you are doing this job and why you love research and teaching.