Yes that is the point, to separate layout (styling) from semantics. Use a <style> tag if it bothers you that much.

FTFY. I work with developers who share your sentiments. I also feel like bashing my head into my desk when I work on the mangled, crufty, mess of nested tables that has been globbered together over 7 years. I will definitely agree with you that CSS is a pain in the ass to wrap your head around, but it really doesn't take much more than a basic understanding of margin/float/display/padding to do about 90% of layout work.

It cuts the amount of code required by at least a two-thirds. <table><tr><td>Foo</td></tr></table> is more typing than <div>Foo<div>

"There is a club for people who don't like their job, it is called "EVERYBODY"; they meet at a bar".

-Drew Carey

Interest is not purely profit. Interest is designed to offset inflation and the other ways you can spend your money. If I owed you $81,000 would you prefer that paid as a lump sum today or paid as a 0% interest loan over 25 years ($3,2400 /yr)?

So in order to make $100,000 today equal to $100,000 in 25 years, we need interest (at least to cover inflation). So for the purposes of this loan $100,000 (at time 0) == $181,000 (at time 25). In addition to the interest, you pay portions of the $100,000 you borrowed. Each payment of $687 is an uneven mix of Interest payments and Principal payments, the ratio changes as the loan approaches time 25.

So if you stop paying halfway through the loan, you may have paid in total $100,000 (combination of interest and principal). But $100,000 (at time 0) is less than $100,000 (at time 25), the lender loses money.

(Disclaimer: I do not work in the financial industry but as a math nerd I am familiar with basic financial math)

5.5% APR with interest payable monthly
Loan of: $100,000
Payment: $687

Present Value: $72,000
Total Profit: -$28,000

I don't think your math is correct.

Yea that's the way it works in the United States also... Student debts are not dischargeable through bankruptcy. Defaulting on student loans will make you ineligible for government employment, along with garnishments on wages, tax returns, and social security benefits.

I would be very interested to see what percentage of these debts are owed to for-profit institutions (e.g. University of Phoenix). Some of these colleges are owned by publicly traded companies, which provided ample incentive for unethical profiteering. There are colleges in my city that sell absolutely worthless degrees in media related fields, cosmetics, business, and healthcare that cost $60,000+.

If you can't make money, you can't repay debts (blood from a stone). It was a simple idea to follow in the U.S. until some schmuck decided to open for-profit colleges and game the system.

Real private and public modifiers would be nice, but I wish people would take the time to understand why the LISP-like qualities of JavaScript make it awesome. I often find myself wishing that .NET and Java were more like JavaScript. To be an exceptional .NET or Java programmer, you need to know tons and tons of specifics about the language. To be a good JavaScript programmer, all you really have to understand are the concepts related to objects and scope.

I think Java and .NET are great enterprise languages for applications that are 10,000+ lines of code. But writing JavaScript in a message-centric fashion (think LISP or Objective-C) is very pleasing with it's terse expressiveness. The language is flexible, and works great for applications that are developed and maintained by one or two programmers.

But the end seems to be near for good-ol-JavaScript; I feel the same way that the LISP programmers must have felt when C and COBOL began to assert their dominance. I'm sad that this inefficient toy-language will soon be relegated as an obsolete and inferior language.

What additional security measures can be taken to thwart script kiddies like this guy? Is MAC address filtering + WEP/WPA encryption (or one of those) sufficient security. At this point I want to shut the fucking WiFi off, but there are others in the household who wouldn't go for that.

I never meant to promote .NET as a superior alternative. I've probably written more PHP than .NET in my life, I love using it for my own projects. In terms of web stuff (and even the occasional PERL substitute), PHP is a damn good language.

JavaScript is a great language, but using it for full-blown enterprise app development would be a major setback. Strongly typed languages are great for the enterprise, because you know (and Intellisense knows too) at compile time what to expect from objects.

Furthermore, I'd speculate that the performance of the .NET Virtual Machine is miles ahead of any JavaScript VM. I cannot recall hearing about any JavaScript VMs that support multiple threads either.

Shit like this makes me not even want to come to this site.

Prototypal inheritance

http://en.wikipedia.org/wiki/Prototype-based_programming#Languages [wikipedia.org]

Q.E.D.

Prototypal inheritance

http://en.wikipedia.org/wiki/Prototype-based_programming#Languages

Q.E.D.

BECAUSE JAVASCRIPT OBJECTS ARE PECULIAR. The difference between those two syntaxes is VITAL to understanding WHY they are peculiar. JavaScript's objects don't function like objects in other languages, especially at the conceptual (abstract) level.

An object is a generic, fundamental aspect of JavaScript.

To correct your weak analogy, imagine an Engineer is building a bridge, and he doesn't understand tension and compression. "Bah", he says "It's stuff anyone could learn by just reading a sufficiently detailed reference". "Fuck it", he says, "I'll just use a bunch of solid rocks!". So he goes and piles together rocks to make a bridge. It takes him 5 times longer to build the rock bridge (instead of a suspension bridge), and he suffers many failures along the way. In the end the bridge is pretty shitty, but it works, barely. It certainly isn't something that is going to last for very long. God forbid you have to use this bridge.

The engineer is you, and the bridge is the style of coding you are suggesting. These details are not "quirks".

It's sad how few web programmers have read this text. Don't be intimidated by its size, most of it is simply reference material, and not part of the tutorial chapters. If you read this book cover-to-cover (well, except for the hefty reference pages), you will be a JavaScript expert.

If you are a web programmer, and you can't answer any of the following questions, consider reading this book.

1.) What does the "new" keyword actually DO in javascript (hint: if you don't say about .prototype you are wrong).

2.) How would you implement a hash in Javascript? Related questions, how are Arrays and Objects different and similar? What is the shorthand notation for them? What does hasOwnProperty do? What is the difference between writing "obj.property" and "obj['property']", when "obj = {}" ?

3.) Explain how scope works in Javascript. How does this relate to closures?

Javascript gets a bad repuatation mostly because it is misunderstood.