Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment: Bill Riders (Score 1, Insightful) 160

by Jezral (#48762829) Attached to: What's Wrong With the Manhattan Project National Park

its inclusion in the National Defense Authorization Act (the park legislation wouldn't pass otherwise)

You guys seriously need to fix your shit. Having bill riders is a fundamental government fail.

In the civilized world, a bill has a strictly defined topic, and anything not directly pertaining to that topic simply isn't allowed to be attached.

Comment: Re:C is dead (Score 1) 641

by Jezral (#48555883) Attached to: How Relevant is C in 2014?

...just because you don't see it doesn't mean it's not there.

True, but so what? I can still write less C++ code but get the same performance as C. I don't care that it temporarily expands during compilation and then shrinks during optimization. I care about my code and the output - the IR is less interesting.

There is no standard ABI in C, the ABI is platform dependent and always has been.

I meant, the C Standard introduces new features in ways that won't break anyone's ABI. C11's _Generic is so bloody ugly compared to C++'s overloading, but it preserves the ABI. The fear of introducing ABI-breaking features is making C even more ugly to read.

I suspect you have very little experience with C and this is why you think C++ is always the right answer

Well, you suspected wrong. I have quite a lot of experience with C, C++, PHP, Perl, JavaScript, Java, Python, etc. I even started with C as my first real language. I just vastly prefer C++.

I do not think C++ is always the right answer, except when asked whether to use C or C++. The only cases where I'd say use C is when there is no choice, such as cross-language APIs.

Comment: Re:C is dead (Score 1) 641

by Jezral (#48554611) Attached to: How Relevant is C in 2014?

Well, the example I have laying around is one I made, just so my bias is clear: http://tinodidriksen.com/2010/...

C: http://tinodidriksen.com/uploa... - 77 lines, 2.4k
C++: http://tinodidriksen.com/uploa... - 33 lines, 1k

The C code is a mess of extra code and checks, compared to the C++ version. The C++ version is as readable as the scripting languages. And C vs. C++ perform almost identically.

Now, that is obviously a tiny example, but I find this to be true for larger codebases as well. If you use all that C++ offers you, you can make the code read like elegant functional or script (or a mix), and still have all the performance of C.

Comment: Re:C is dead (Score 1) 641

by Jezral (#48554561) Attached to: How Relevant is C in 2014?

The FQA? Really? Read it, laughed at it, moved on.

Modern C++ is as easy to learn as Python or Java or C# or similar. The code will even look superficially the same.

C++ is only hard to learn for those who insist on learning "C with Classes" and mix in all sorts of silly C'isms, like insisting on starting with raw memory management. If you start out with the high level stuff and containers, it's easy, safe, fast.

Comment: Re:C is dead (Score 1) 641

by Jezral (#48554523) Attached to: How Relevant is C in 2014?

Standard C++ has never been a strict superset of Standard C. You have never been able to take all C89 code and just compile it as C++98, primarily due to C++'s stricter type system (e.g. malloc() will need a cast added).

Anyway, sure they share a lot of syntax and basic concepts, but when you compare modern C++ with C, it's like comparing a high level scripting language with, well, C. If you take code in Python, Perl, PHP, Java, C#, and C++, they'll all look mostly alike. If you code the same in C, it'll look foreign and require many more explicit sanity checks. But the C++ and C code will have the same performance, while the other languages will suffer lots of overhead.

Comment: C is dead (Score 1) 641

by Jezral (#48553863) Attached to: How Relevant is C in 2014?

I always tell people who want to learn to code to go for modern C++ (preferably C++11 or newer) first, and then if necessary learn some C afterwards.

It is crazy how much more C code is needed to get the same level of performance and security that equivalent C++ has, and C coders know it. Just look at all the extensions that C compilers, and even the C11 Standard, borrow from C++ (generics, RAII) - but in a convoluted ugly way to preserve the precious ABI for 50 years.

And for all those who will say that C++ can't fit in the tight spaces that C can...well, you're wrong. Just disable the parts of C++ that you don't want (usually exceptions), and you can still get most of the benefits of clean code and RAII, with the same or better performance.

Comment: It can work... (Score 2) 2219

by Jezral (#46187017) Attached to: Slashdot Tries Something New; Audience Responds!

I fiddled with Firebug on the Beta site, and made a few changes that amazingly improves the look'n'feel of it:

- Remove article images.
- Remove the CSS line-height property from both submission and comments.
- Distinguish where submitter intro ends and submission begins. "Quotes" are not enough - the old blockquote worked nicely.
- Make the submission text color black. It feels hazy as it is now.
- Let comments flow full-width. Having them constrained by the huge sidebar is awful.

In general, it seems like you're turning Slashdot from a community driven site to a more modern publisher/aggregator style site, which won't work. If the comments aren't the primary focus, Slashdot loses what makes it Slashdot.

I can get up to date news everywhere - I can't get quality commentary anywhere but Slashdot.

+ - Slashdot BETA Discussion-> 60

Submitted by mugnyte
mugnyte writes: With Slashdot's recent restyled "BETA" slowly rolled to most users, there's been a lot of griping about the changes. This is nothing new, as past style changes have had similar effects. However, this pass there are significant usability changes: A narrower read pane, limited moderation filtering, and several color/size/font adjustments. BETA implies not yet complete, so taking that cue — please list your specific, detailed opinoins, one per comment, and let's use the best part of slashdot (the moderation system) to raise the attention to these. Change can be jarring, but let's focus on the true usability differences with the new style.
Link to Original Source

Comment: Re:Prepare for Debian (Score 4, Informative) 176

by Jezral (#44816943) Attached to: How To Turn Your Pile of Code Into an Open Source Project

I'd love to do that, but getting a package into Debian is a nightmare that I have simply given up on. Even the simple guides are 50 pages long and a mass of not quite up-to-date information.

Ubuntu makes it trivial. Even if you can't or don't want to get into Ubuntu base, you can just make a PPA on Launchpad and get automatic building for all supported editions and archs of Ubuntu.

Comment: Re:Awesome post (Score 1) 117

by Jezral (#42357711) Attached to: Why Google Hired Ray Kurzweil

We have something like that at VISL, but with zero statistical or machine learning or AI aspects.

We instead write a few thousand rules by hand (largest language has 10000 rules) that look at the context - where context is the entire sentence, and possibly previous or next sentences - to figure out what meaning of a word is being used and what it attaches to.

E.g.
Input: "They're looking at writing an AI which can in some sense understand what is being said."
Output: http://dl.dropbox.com/u/62647212/visl-eng.txt , http://dl.dropbox.com/u/62647212/visl-eng.png

This kind of system takes longer to develop and refine, but it also doesn't have any of the statistical problems. 95-99% "understanding" of text? Sure, we can do that. Statistics top out long before, and then have to add in rules to get the last 5-10%. And where statistics require giga- or terabytes of text, rule based systems only require a single example of a valid grammatical construct or word usage.

Logic doesn't apply to the real world. -- Marvin Minsky

Working...