josefdlange

Peewee [1] is my tool of choice because of its convenience and flexibility combined. I can create pretty complex queries using its Query API, but also execute arbitrary queries when I know I need something a little more nonstandard. Plus the maintainer (Charles Leifer) is an awesome dude who has always been really helpful to his users.

[1] Peewee: https://github.com/coleifer/peewee

Well, the first port I find of GCD for linux, libdispatch, hasn't been updated since October, but it looks plausible for use. ANSI C doesn't employ the same kind of code block mentality that Objective-C offers, so the interface is probably a little different.

https://github.com/nickhutchinson/libdispatch

I stand corrected -- there has been some movement. The desktop app is largely unchanged (visually) over the last few years, which I suppose isn't necessarily a negative aspect. Feels a little outdated but still works just as well, I can attest to that after downloading and launching it just now.

The Hit List [1] was my go-to when I was in school. Really painless information ingestion, and convenient means of displaying data.

Unfortunately it is not well-maintained in terms of updates... hoping it will see some love eventually...

[1] http://www.karelia.com/products/the-hit-list/mac.html

Largely inspired from Zach Holman's "boom" and with some inspection of the implementation details of Ben Tappin's Python port thereof ("bam"), I whipped this up a couple years ago and have found it useful from time to time as a good way to keep track of tasks without breaking context of command-line work.

Pack this up and get it on PyPI! Nice simple little script but quite inconvenient to get onto a system, especially if one prefers using package managers.

Gah. I would love having this.

The first time I read this headline I thought it said "Nazi Australia" which would be weirder.

Some cool stuff here, though I think a demonstration video or fancy animation would be nice. Like someone else has mentioned, it's a little intimidating to give full access just to see how it works -- you might convert more customers if they can see how it works and some common use cases before they need to commit the time to trying an integration.

Excellent.

If you want your employees to stay, and to contribute their ideas to you instead of running off to your competitors or starting their own companies, it's so so so much better to just treat your employees better than the bind them legally.

I love the thought of being able to use Python on the client side of the web. We need more commonplace asynchronous paradigms, however.

I do like how this project makes sure to point out that the DOM interface is intended for consumption by any language and on any platform -- maybe one day we'll have browsers that come with several languages' runtimes baked in, or perhaps that can leverage the runtimes for languages already installed on the local machine.

This website does the worst job explaining what it's even here for. I have to spend ten minutes reading obfuscated to text to understand that the font shows different glyphs when I type a "dangerous" word? Why do this in a font? Why don't you build a spellcheck dictionary and misuse that technology instead of this one that's in front of me all day?

This is one of those times where you are literally allowed, even encouraged, to think of only yourself.

You have cancer. You can't avoid that. It sucks. It's one of the worst hands to be dealt. Get treatment. Get the best damn treatment. If you don't already do so, start taking care of your body 100%. If you do, bump it to 110%.

Cancer is not easy. It is a vicious plague that wants nothing less than to overtake your body for its own growth. It's ugly.

But you can beat it.

Take the time and effort you need to fight this, and use what you have left doing what you love to do, which if you're anything like me, it's the work that you'll be starting very soon.

It'll be exhausting. When you get into chemo, and maybe into marrow transplants and stem cell procedures, you won't often have much energy--both physically and mentally--to contribute, so do it now.

Sorry if this is blunt, but I don't want to give off the impression that everything is going to be fine and everything is going to be normal. Shit is going to hit the fan.

But you can do this.

You're fucking dammit_lump; you can do this.

I think you and many people are overcomplicating this subtopic into the legal context of receiving C&D, etc letters.

Their service is their software. They have control over it. If they wish to impose technical limitations to how it may be accessed and by whom, that is entirely their prerogative. Nothing in the law can tell a company or a user otherwise, short of subpoenas for customer data or some such like that.

I think the larger legal issues come from the fact that circumventing these technical limitations can lead to to degradation of value and security for a company's customers due to derivative products created via this unauthorized client -- much like what has happened with SnapChat and third-party services retaining snaps. If systematic unauthorized access to a system could serve to diminish the value and trustworthiness of a company and its brand, you're damn right they will legally pursue those enabling it.

When you are cooking, and your recipe calls for transferring a pan from the stove to the oven for finishing, do not forget that the handle to said pan will indeed get very hot while in the oven, and you should wear oven mitts when retrieving said pan.

Source: I am very skilled at burning the palms of my hands.

I can feel the RSI already. I was excited that this might have been a weird hybrid between a mouse and a trackpad where the tracking surface goes on your fingertip, and everything becomes a trackpad.

This.

Making potentially baseless claims and not explaining their impact beyond "they're bad!" is the kind of rhetoric a middle schooler uses before he or she learns to write proper persuasive prose.

While I agree that data should be as freely available as possible--so long as the person to whom the data belongs approves--I really can't get on board with this histrionic garbage.

Make an assertion. Back it up with evidence. Explain the consequences.

Damn, I'm a felon because of my old microwave!?

If anyone is interested in the biography of the Manhattan Project in general, including much of the goings-on at Los Alamos, I really must recommend Rhodes' "The Making of the Atomic Bomb" (http://www.amazon.com/The-Making-Atomic-Bomb-Anniversary/dp/...)

It's an excellent read, cover-to-cover. One of the few assigned books I read with excitement while in undergrad.

It took me about five minutes to realize how dumb I was and that this was literally Vanilla JS.

What's throwing me off -- and I'm sure it's something trivial I'm not seeing -- is how we add the functions to the routes dictionary. When is the decorator's code actually executed? Is that done at import time? My assumption is that its code is executed when its counterpart is called, though clearly that mustn't be the case.

Given my understanding from the article, there's a hole: how does serving route "/" know to call that function if (given my assumptions) the @app.route("/") decoration is not executed until the function it decorates is called?

When connecting to your web page via HTTPS it attempts to load JQuery via HTTP and FireFox cowers in fear of XSS attempts. Don't do that.