Ayjay
If you don't know how Steam ads work, when you first log in to Steam, it will pop up a window with several pages of ads for different deals and promotions going on. Given how low some games on Steam cost, I find that I very frequently will click through and buy the games advertised (things like $5 for an otherwise $50 game can be so attractive!)
I guess the criteria I use for ads is relevance. The only thing I really ever buy over the internet is games, so advertising on the internet for anything that ISN'T a game just won't get my attention, no matter how well you write it.
Coding at the bare-metal level is a very slow, tedious, error-prone and silly way to code unless you're doing, or have some external constraint that forces you to (and, no, efficiency isn't usually a reason not to use C++ or the STL, it almost always compiles to the same as using strcpy's and malloc's.)
-- Ayjay on Fedang/coding
Australian, btw.
-- Ayjay on Fedang
When there's a limited supply of anything, naturally the price will rise. In every other market, there is no benefit to being "first in line" for the product - the price is the price.
Why not have an auction system for getting tables? Whenever a table becomes free, the maitre d' asks everyone to bid on the table. If no-one bids, then whoever is first in line gets it. That seems like the fairest system - no-one can game the system by bribing because it's all completely open and honest.
Why don't any restaurants do this? As a bonus side effect, you'd probably attract the people with more money to spend, as they figure they can guarantee themselves a quick table. Also, this allows the people that really want to go to a restaurant to splurge on getting the first available table, while someone who doesn't really care might leave and go somewhere else.
Basic market forces causing the most optimal distribution of a limited resource.
-- Ayjay on Fedang
Also, maybe then you can push lower-level pixels around?
-- Ayjay on Fedang
A much better solution is to write things in the easiest way for coders to change - that way, when something is found to be the actual cause of slowness, anyone can easily go in and optimise it or move it to a background thread. Optimising EVERYTHING in the hopes of obtaining speed is a fool's errand - due to the 90/10 rule, 90% of the code you optimise will never be the bottleneck.
-- Ayjay on Fedang/coding
I don't think it really needs to be made more accessible, but what would have been AWESOME would be to have known about vim-tutor. I only just found out about it after I've spent a few weeks working in Vim, and have largely passed the time when vim-tutor would have helped. It REALLY should be on the main vim screen, not in the help.
Maybe I'm weird in that I have an inherent distrust the help in open source apps. Most of the times, they seem to be archaic, and targeted at the very advanced users (see man pages).
Thankfully, I've passed the initial stumbling-around period, and now know that the help is actually written in a very readable format. Maybe all that needs to happen is for that to be better communicated.
-- Ayjay on Fedang
mozz on fedang
Most of us probably started with BASIC interpreters, so easy and readable code is obviously not a prerequisite. What BASIC interpreters did tend to do well was allow you to write a few lines, then run it and have it do what you said.
To answer the question then - I think any non-compiled language would be fine. I think things like Python is probably the best, as you're not required to program in an OO style, or in a functional style - just write lines, and they'll work.
Once the kids are interested and know a bit about how programming, sure, then teach them proper style. The important part is getting them to realise how to formulate thoughts in a structured manner - once you've done that, forming them in a different structure doesn't seem too hard.