|
I switch between programming languages quite a bit; I often wondered what happens when having to deal with the different syntaxes, does the syntax allow you to be more expressive or faster at coding in one language or another. I don't really know about that; but what I do know what keys are pressed when writing with different programming languages. Let me guess: Lisp uses a lot of parentheses.
|
|
|
|
|
VB uses lots of 'backspaces'.
|
|
|
|
|
Ctrl, C and V for most of them, I suppose
|
|
|
|
|
Jarek Kruza wrote: Ctrl, C and V
Depends on the editor you are using
|
|
|
|
|
And Ctrl+Z
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Hard to say what to make of it. What would be more interesting is how many keys for the same functionality, or course I guess that would depend of the functionality desired.
|
|
|
|
|
Regardless of the language, a top contender of mine would be: CTRL+S.
I'm surprised C++ didn't have more "*"/"&".
|
|
|
|
|
for Java according to my keyboard:
A, S and the left Control button.
|
|
|
|
|
Visual * languages: F5
Debuggers, debuggers, debuggers!
|
|
|
|
|
It’s never good to scare away your customers. It’s even worse if you don’t realize you’re doing it. That was me. Turned out I’d been snared by IE’s SmartScreen filter. That’s an expensive bug.
|
|
|
|
|
More proof that it pays to know how your users work.
/ravi
|
|
|
|
|
Quote: Like most folks in the developer community, it’s been years since I last used Internet Explorer as my daily browser
I think the internet needs a [citation needed] badge.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Chris Maunder wrote: I think the internet needs a [citation needed] badge.
I first read this as "needs a 'explicit' badge." ... Then I realized you actually meant '[citation needed]'...
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill
America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde
Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
|
|
|
|
|
That's one of the reasons why software testing pays for itself. A developer is concerned with getting the functionality, the tester with making sure it works. Of course also a good idea to have some sort of spec to test against, of course the testers should be developing a test plan so they will know what to test.
|
|
|
|
|
I've heard many folks say that HTML is primarily for presentation and not for conveying information, and hence it isn't suitable for API use. Hogwash, I say! There are many web experts (like Kimberly Blessing) who would insist that markup is exactly for conveying semantics and that presentation should be a CSS concern. People seem to forget that web sites actually worked before CSS or Javascript was invented! I rely on this heavily for my HTML APIs. Semantic APIs built on a semantic web.
|
|
|
|
|
Scalatron is a free, open-source programming game in which bots, written in Scala, compete in a virtual arena for energy and survival. You can play by yourself against the computer or organize a tournament with friends. Scalatron may be the quickest and most entertaining way to become productive in Scala. We who are about to code, salute you!
|
|
|
|
|
Developers have created more than 100,000 apps for Windows Phone, as Microsoft continues its efforts to make the platform a viable alternative to iOS and Android for app developers. But how are those efforts going down? To find out, I posed some questions to five companies who've recently released Windows Phone apps, asking about their motivations for supporting the platform, how they've found it, and how they'd like to see it evolve. Is Windows Phone a lucrative – or even just a viable – platform for developers?
|
|
|
|
|
eBook DRM is not only undesirable for digital products, it denies users a fundamental function of a book: sharing. Clearly a reader cannot (easily) share an eBook that is “protected” by DRM. And publishers like to “protect” their content so that they can make dat money rather than have their content just given away and shared around. But, there is another side to the argument, beyond sharing, that is essential to understanding this issue: the ways in which people interact with books is an expression of their identity. Ebooks aren't free books.
|
|
|
|
|
I'm pretty sure I've heard of one of the popular eReaders being capable of "lending" an eBook. I guess that would mean that one person could access the content at a time. Sounds like an ok model to me.
As far as display, would be nice if you could just lay your eReader on a table and have a slideshow or gallery of the eBooks you own. And then there are possibilities for "social" features, such as having a Facebook section for your "bookcase". If it were well integrated, you could even lend from Facebook.
These problems are solvable even with DRM, if done properly. Though, I do question if DRM is necessary. I'm pretty sure all iTunes content is now DRM-free, so maybe eBooks could go the same route. One big problem I have with eReaders is that I'm locked into their format and their DRM, so if I get a new eReader (e.g., I decide to toss my Nook and get a Kindle), I can't transition my eBooks to the new device. Though, this would be solvable if there were a central license repository shared among all eReaders (so I can download the eBook on the new eReader).
|
|
|
|
|
Hadoop is on its way to becoming the de facto platform for the next-generation of data-based applications, but it’s not without flaws. If the growing number of options for replacing HDFS signifies anything, it’s that HDFS isn’t quite where it needs to be. Here are eight products and projects whose proprietors argue can deliver what HDFS can’t. Big data, no whammies!
|
|
|
|
|
I was in charge of scaling Dropbox for a while, from roughly 4,000 to 40,000,000 users. For most of that time we had one to three people working on the backend. Here are some suggestions on scaling, particularly in a resource-constrained, fast-growing environment that can’t always afford to do things “the right way” (i.e., any real-world engineering project). Simplify your life... by keeping those servers humming!
|
|
|
|
|
Password reuse—using the same password for multiple sites or services—is both rampant and dangerous. There is real evidence that people are getting robbed because they are reusing their passwords. Thieves systematically exploit reused password to pay for retail items or hijack accounts for other intentions. And yet, we are reminded again this week by the recent leak of almost half a million Yahoo passwords that a majority of people just can’t stop reusing passwords. I’ve seen password reuse and the damage done.
|
|
|
|
|
We can learn from the problems that lead to catastrophes and loss of life and apply them to the field of web operations, because the similarities in the systems and their operations are striking. The rather sad news is that only recently have these other fields and instrustries started to openly discuss failures in complex systems and how to respond to them. They're no different from us. What we have is the advantage that we can iterate quickly and make changes to improve our application's resilience. Let's build systems with humans in mind.
|
|
|
|
|
|
missing a link?
Be The Noise
|
|
|
|