This! Any graphical history for git that doesn't let you show all branches at once is trash. (Like the one in Visual Studio) The interactive rebase editor in Git Graph is very nice too.
I also love how smoothly you can jump between git CLI and GUI in VS Code.
I'll have to look at how to compare arbitrary commits in Git Lens and whether it is in the free version. That's the one thing I still rely upon TortoiseGit for
You have no donate link... if you're gonna be on big sites like HN, you might as well have a donation link so that hopefully you break even on App Engine.
Yes, it does. If it is 'hardcoded', then the intelligence lies in whatever 'hardcoded' it, not in the entity following the 'hardcoding'. Genetic algorithms have a certain amount of intelligence, although slow and clumsy. The fact that the world's biggest genetic algorithm* can program a spider to build an elegant solution does not mean the spider itself is intelligent.
* If you treat the algorithm for spiders and beetles as the same... I strongly suspect that a significant portion of the algorithm is actually implemented within the genes. For example, control genes massively amplify the effect of small genetic changes, allowing creatures using them to evolve faster than those without.
Actually, whether admitting it is dumb or not depends a lot on whether you're dealing with an objective or subjective situation, and the odds * costs of being caught at wrong answers.
For an example of a subjective situation, in a poker game it can be useful to pretend to know you will win in cases where it is unknown, or even in cases where you know you have a weak hand. The other player's subjective impression of what you know is more important than its actual accuracy.
On the other hand, computer programmers and engineers usually are dealing with objective circumstances where not admitting you don't know results in things breaking and delays finding out the objectively true answer.
A common failing is to not recognize which of the two types of situations you are in, and just assume you should treat it like the one you are most used to. Hence engineering types may be ignored because they don't sound confident in their answers, and political types forget that that rules or legislation cannot override the laws of physics.
That's because the traditional economic definition of "rational" is an incomplete model of real world sanity that only works in incomplete models of the real world.
In the real world, you have to deal with the uncertain risk that the offer will be unfulfilled due to external factors, which always increases in time relative to present. You, the entity offering you the choice, or the entire environment both exist in, may not still exist in 60 months.
If the same offer is made 60 months from now, you should make a different choice, because the risk of non-existence between time of choice and time of reward has changed.
If the amount of hyperbolic discounting is genetically determined, then is likely that we are still adjusting to the massive drop in risk of death over the past several centuries.
It would be nice if you could tell if there is any local activity before signing up. I'm not giving a random web site my Facebook or email when most likely no one else local is signed up anyway.
I have to disagree there - there are other approaches to market-based funding of the creation of cultural communications that are not advertising based. For a very successful current example, see Kickstarter.
A very quick approximation seems to indicate it still isn't feasible. I saved 2 32x32 JPEGs using Gimp at quality 30. One is a cutout of a face from a photo, the other is random noise generated using the filter in Gimp. The resulting JPEG files were 427 bytes for the face, and 525 for completely random.
Now, I have no idea how much of that is the header. So, to help guess that, I saved a solid white 32px image with the same settings, and it was 164 bytes.
I wonder if this would be explorable for some much tinier subset of the space of images. Like maybe 32 x 32 greyscale JPEG images with some limit on compressed size that keeps it to interesting images.
I'm specifically suggesting JPEG because it is a compression method based on human perception, so if we focus only on easily JPEG compressed images, we should eliminate a lot of the image that look like snow on a TV, and restrict more to images that look vaguely like something.
Unfortunately, I don't remember enough details of how JPEG compression works to make a reasonable guess how many possible JPEGs this is, and whether we are getting into numbers small enough to be feasible.
The reason that is not available is that the universe of options for beginning programming has exploded since the old boot into BASIC days, and there is no longer agreement on the easiest way to begin programming.
As for the same set-up on every single Mac/PC, it's already there, it is just slightly harder to get to than you want. It's called a web browser, and there are numerous URLs you can go to that let you program right in the browser.
The online version of "Eloquent JavaScript: A Modern Introduction to Programming" by Marijn Haverbeke has an integrated JavaScript console at the bottom to follow along. http://eloquentjavascript.net/chapter1.html
If anything, the problem is that there are too many answers, targeted at too many starting levels, so it is hard to Google for any likely phrases and get to the answer easily.Searching for "begin programming" seems to give better beginner answers, whereas "learn to program" tends to give more college-level answers.
I see no reason why a kid who is interested in how to do it, and grew up in the modern era around web browsers and search engines and such, would have any trouble finding something quickly.
I'm amused that you think it is possible to rewrite the whole thing without entering super brain mode. In my experience, generally the only way to reproduce such legacy reports is by reverse engineering how they currently work. (which will require super brain mode based on the above described current complexity) One would think someone in the business would know what the report is supposed to do, but I frequently encounter cases where no one does, they just want the report to work the way the old one did, whatever the heck that was.
I know of no solution not involving time travel to solve that for legacy reports and systems. Obviously going forward one can worry about documentation, etc. but with legacy stuff it is already too late to implement those rules.
One thing I don't like is nothing on Buxfer's site tells you they are dead - I was considering signing up as a new customer, but suspicious due to the lack of blog activity and the questions if they are dead on GetSatisfaction.
They looked like a really decent web 2.0 style personal finance manager, with some really slick features. Way nicer than Mint.
I think gojomo has a really good idea here. However, there is no reason to bias it against Google's ad network. We need an advanced search option to find non-ad supported sites, that behind the scenes attempts to filter out every known ad network.
The use case wouldn't be an all the time thing, it would be when you are searching and get results that are overly polluted with ad-based content. Having the option to filter to non-ad based content lets you focus on those sites that have a motivation other than page views for providing content. I imagine this would include both sites actually selling products and non-profit sites like Wikipedia and open source.
This is a common misconception caused by quoting mean life expectancy at birth, when the distribution is highly asymmetrical. High infant death rates cause low life expectancy at birth, but the life expectancy if you live to age 5 can be massively longer.
A 5 year old ancient Roman was expected to live to 48. About 35% of the ancient Roman population was over 30 years old. The highest listed age is 76, which is the life expectancy of a 70 year old, an age that about 1 in 50 ancient Romans achieved. http://www.utexas.edu/depts/classics/documents/Life.html
http://www.ngbasic.com/ - Has more of the classic BASIC feel, opening a window that looks like ye olde BASIC interpreter, but requires two clicks before you can find it.
http://www.quitebasic.com/ - Also starts at the interpreter, but with a more complicated example program.
1) How hard would it to write a JavaScript/HTML port of it? I don't see why anyone in the modern day and age should need to download and install a program to play with BASIC. It should be possible to interpret BASIC directly in JavaScript, all within the browser. I don't believe any server round trips should even be necessary.
2) Have you let David Brin know about your effort? He seems to be doing talks on the subject still as recently as '09, so he might be able to at least mention it to people.
I also love how smoothly you can jump between git CLI and GUI in VS Code.
I'll have to look at how to compare arbitrary commits in Git Lens and whether it is in the free version. That's the one thing I still rely upon TortoiseGit for