Forgot your password?
Close
typodupeerror
KDE

Submission + - Aaron Seigo talks about KDE SC 5.0 and more (derstandard.at)

Submitted by Anonymous Coward
An anonymous reader writes: After years of focusing on further improving KDE4 two weeks ago the developers of the free desktop announced the next big step for their project: KDE Frameworks 5.0. But as long-time developer — and Plasma team leader — Aaron Seigo points out in an interview with derStandard.at/web, the source-incompatible changes shall be held to a minimum. Also calls Frameworks 5.0 only the "first step", new Applications and Workspace releases are to follow later, Seigo goes on to talk about the chances in the mobile market with Plasma Active and further areas of collaboration with the other big free desktop: GNOME.

Comment Re:BASIC is irrelevant (Score 1) 548

by irishxpride (#31434020) Attached to: The Value of BASIC As a First Programming Language

It's far better to teach beginning programmers in Pascal or Java than it is to use Perl, for example.

Could you elaborate on this point? I am not primarily a programmer; I am a networking nerd for an ISP. I have however, in the course of my duties, had to utilize a variety of programmer-like skills. I learned programming originally in perl, because it was the closest thing to shell scripting (which I generally understood enough to accomplish my goals) that met my immediate needs. I'm curious what kind of bad habits I may have inherited from my initial exposure to perl as opposed to, say pascal. Specificity would be appreciated as my goal is not to argue, but to hopefully learn and save myself some headaches...

Submission + - Chilean earthquake shortens days (businessweek.com)

Submitted by ailnlv
ailnlv writes: According to TFA, days just got shorter. In brief, the recent earthquake slightly shifted the Earth's axis by about 8 cm and shortened days by 1.26 microseconds

"The changes can be modeled, though they're difficult to physically detect given their small size, Gross said. Some changes may be more obvious, and islands may have shifted, according to Andreas Rietbrock, a professor of Earth Sciences at the U.K.'s Liverpool University who has studied the area impacted, though not since the latest temblor."
Spam

Where Has All My Spam Gone? 597

Posted by kdawson from the yesterday-upon-the-stair dept.
An anonymous reader writes "I have my own domain, which has its own email server, where I receive all my personal email. I've been getting about 800 emails a day, of which perhaps 20 are real. Suddenly, Sunday or Monday evening, the spam pretty much stopped. My volume of mail has plummeted to less than 100 a day, and as far as I can tell, I'm not missing any real mail — I'm still getting the email list subscriptions I'm expecting, and every time I ask someone to send me a test message, it gets through. My domain host insists that it doesn't do any spam filtering before mail gets to my inbox, and that they've changed nothing about their configuration. I run SpamAssassin on my server to mark, but not delete, spam, and download the whole mess to my home client, and I'm still seeing the occasional message tagged by SpamAssassin. But it's virtually all gone. And I haven't changed anything about my own mail configuration, or the harvestability of my site (my personal email has been harvestable for almost a decade). So what's going on? I can't believe that several major botnets would have vanished overnight. Any ideas?"
Software

Submission + - Software Logging Schemes

Submitted by
MySkippy
MySkippy writes: "I've been a software engineer for just over 10 years now. I've seen several different styles of logging in the applications I've worked on over the years. Some were extremely verbose containing about 1 logging line per every 2 lines of code. Some were very lacking with maybe 1 logging line for every 200 lines of code. A friend of mine recently turned me on to log4j and log4net and I have begun using both. For logging, I personally find that writing debug and informational messages about every 2 to 5 lines works well for debugging an issue but can become cumbersome when reading through it for analysis. I tend to write warning messages when thresholds or limits are being reached. These tend to be much less in number. I log errors when ever I catch one and I have never put a "fatal" message in my code because if it's truely a "fatal" error that means I probably didn't catch it. After all, if I caught it, it's probably not a "fatal" error. That brings me to my question, what do the slash dotter's out there handle logging in their code?"

Slashdot Top Deals

"The great question... which I have not been able to answer... is, `What does woman want?'" -- Sigmund Freud

Close