tkellogg

Yes! I'm the author and this is the next feature I was planning on adding, I was even planning on naming it `dura status`. First I need to get better logging (to a JSON file), and then expose it via `dura status`. It occurs to me that having all that data could tell me a lot about how I work, so it could unlock some very interesting usages of dura.

Would you mind creating a Github issue? The project could benefit from more discussion around this.

LOL — author here — I definitely didn't intend it that way, but it does kind of jive with "Git's" other meaning. I should have known that all 4-letter words are an insult in some language.

I had originally named it "duralumin" after a magical metal in [a novel that I'm reading](https://www.amazon.com/Well-Ascension-Mistborn-Book/dp/07653...). I shortened it to "dura" after realizing that I can't even remember the name, so there's no chance anyone else will. Plus is has that "durable" vibe to it, which seemed appropriate.

Reminder: There are real-time allocators available, they just tend to not be used because the average case is worse.

* http://repository-of-projects.googlecode.com/svn/trunk/docum... * http://www.ijera.com/papers/Vol2_issue3/GR2311511156.pdf

How long until this hits Homebrew?

For the life of me I can't find anywhere that says "extensibility" is a goal of MQTT. The main goals are clearly stated to be "simplicity" and "lightweight". Extensibility is the enemy of both. A lot of Clemens' points are based on the concept that MQTT is supposed to be extensible. When you realize that's not even a goal, most of his concerns become moot. He says "I'm not trying to create another AMQP" but if you think about what he's actually saying, it's quite the opposite.

It's neat (if not alarming) to see security metrics visualized like this. Nice work!

Honestly, I'm glad its only a DSL. It means I can still use the programming language that I love but get the benefits of some obscure special purpose language.

Yes, I had a similar experience. I was asked to review a book that was terribly written. The language problems were so bad that I had a hard time reviewing the content. That said, even the content didn't deserve to be put in writing. Definitely not worth even $1.

A lot of these seem to be Microsoft technologies like C# or SQL server. Is that because the owner is more familiar with the MS stack? Or do MS devs have more to complain about?

I find it interesting how the concept of countries and nationalities seems to becoming less important. Now (as opposed to a hundred years ago) we communicate with people in foreign countries on a daily basis - even countries whose governments have hostile relationships with.

This is definitely a CYA (cover your ass) maneuver designed to mitigate the political hit these companies are taking. At the same time, these companies are acting like countries. They've formed an alliance and they're attempting to make a treaty with the governments that they happen to fall into. It will be interesting to watch the societal change as the importance of countries and nationalities decreases over the next hundred years.

4 hours of lifting a week? That's a lot of time. I know myself well enough that I won't make goals/commitments that I know I won't keep, like this. I have some simple weights in my living space that are hard to ignore. I typically lift for <5 min/day; when I go to the gym I keep it under 20 min to lower the cognitive commitment. It works for me - I can bench press 250 lbs. You really don't need to spend hours at the gym to stay in shape.

I completely agree. While asm.js has its problems, its moving in the right direction. Honestly, it seems like this wouldn't be too hard to add a backend target for asm.js, if its implemented well.

This definitely highlights how broken the software licensing system is. The US military is notorious for placing money and budgets as a rather low priority. The biggest hurdle for most groups isn't obtaining money, it's going through the bureaucratic processes. Likely, the priracy was committed to avoid the painful bureaucracy. If the company simply made it easier to obtain a lawful copy of the software they would probably be recovering a lot more than $60M - and without lawyers.

2x is a pretty serious regression. I'm really not sure how that could be overlooked. doesn't rails do performance tests as part of their regression suite?

Just make sure to buy 3 or 4, they probably switch busses every now and then.

2lemetry is running an MQTT broker - MQTT is a standard protocol designed by OASIS for these sorts of low-power, low-bandwidth scenarios. It's a pub/sub system and you'll probably get away with a few messages per minute. I think the 2G hardware might be the limiting factor here.

Because constitutional protection and human rights are greater causes than the few bucks you lost. Lavabit didn't have to shut down, they could have handed over your private emails, but they didn't. I'd say they've more than earned what you paid.

You won't necessarily find yourself happier - it's a choice. If you go right back and make the same mistakes at a new job, you'll hate that one too.

I got fired a few months ago and it was the best thing that could have happened to me. Until then, I'd changed jobs every so often because I never liked where I worked. But when I got fired, I thought long and hard about what I needed in a job. Only after acting on some well thought-out conclusions did I find an excellent job that's absolutely a perfect fit for me. I probably wouldn't have thought that hard about my next step if I wasn't fired.

So while that comment is true for me, I can't imagine that it's always true. If I was a dumbass and took a job exactly like the previous one, I'd hate that one too. I might not get fired - I might quit before they fired me. Honestly it doesn't matter which happens first. If you don't put in the introspection to find a place that fits you and vice versa, you'll hate it in no time.

Figure out what you need, figure out what you can do well, and find a job that matches that.

Use rethinkdb instead. Its not perfect but it mainly hits the same niche but does it right.

This isn't impressive. [MQTT][1] is a much better protocol, and an open standard. It's a pub/sub that runs over TCP with variants that run over UDP & TLS. There's only a 2+ byte overhead, so it's very light. It's ideal for mobile devices because it has a QoS system built-in, so the developer doesn't have to think through the problem of missing messages where cell service is sub-optimal. MQTT is even resource-based, so it fits well with REST. I wish more people would start using MQTT instead of these crazy hacks like REST Hooks.

[1]: http://mqtt.org/

If you think sales & marketing are a zero sum gimmick, you must not have encountered middle management. The fact that we pay these baby sitters so much money compounds our "need" for them.

There probably is merit to the warning, but the word "scapegoat" may be wrong. It means that your blaming the nation's problems on them. I haven't yet seen Putin blaming gays for economic hardships or crime. Misuse of overly strong words discredits the article.

I don't think its as simple as "ending it with a phone call". Billion dollar programs don't ever get killed that easy.

It says

    `Option<~T>` is now represented as a nullable pointer.

Does that mean they introduced more prevalent nulls into the language? that seems like a shockingly bad choice

That one's got to be $30, at least! Probably a red...

While we're talking about "smart cd" tools, I should mention my Windows PowerShell tool.

https://github.com/tkellogg/Jump-Location

My favorite part - they use type providers to work with xaml code. They're moving IDE features closer to the compiler.

It creates barriers to use patents offensively. I'd guess that relatively few offensive patent litigations are initiated by the company that created them. Of those, very few of the inventors would agree to offensive usage. The only way that I can see to convince inventors to use patents offensively would be if they got a significant cut from the litigation proceeds. This cuts down on the appeal of an offensive litigation.

So no, it's not perfect. It uses incentives to control abuses. Even though it's not perfect, I still like it's simplicity.

No, the company still owns the patent. However, the company now has responsibilities back to the inventor. So while the inventor still doesn't own the patent, they do have some control over it's ability to be used for evil.

Actually, the VS project file format is standard. Mono supports both Visual Studio formats (.sln, .csproj, *.fsproj, etc) as well as Makefiles