I've seen similarly bad tutorials about templating. The way they teach how to cut your basic HTML and CSS apart in chunks is complete nonsense. They're showing people to always copy a whole empty framework and call cut-out parts all over the place. And then inside those cut-out parts, call out other parts. I've seen this done five levels deep.
It still works, but trying to way your way around all is extremely tedious. And if you need to make a change to the basic original framework, you're out of luck because the idiots made that code NOT part of a template and replicated it manually in all the pages of the website.
If a bridge collapses, do you blame the production workers who followed the plans exactly as they were or do you blame the engineer who was too lazy to make the proper calculations and didn't get the tests done for the bedrock foundation, etc?
You're doing the popular "snowflake attack" thing here, when in fact you're the snowflake thinking that everyone is as good as you are. The thing is, as I said, it's not everyone's job to be a security expert. We should expect security to be part of the tools instead of expecting everyone to be a security expert. The first is possible, the second will never be.
People learn not by memorizing but by looking at examples.
Most of the people working in Web-related jobs are not security experts, their job is to get things done as quickly and cheaply as possible. You might think in terms of huge corporations were IT is divided in groups, each working on specific parts of the whole. At the smaller scale though, the same person responsible for the front-end with HTML, CSS and Javascript has to work on the back-end with PHP and MySQL. The second their code does what it's supposed to do they just keep going to the next item to be completed.
So really, blame the examples and especially the tools. This is a similar problem to languages that allow you to point outside the bounds of an array or operating systems that can't protect themselves from applications gone rogue. Security should be part of the OS, part of the languages, part of the frameworks. Only then can you blame the coders at the bottom for security holes.
To reply the thread, my vote is also for basic, specifically GW-Basic on the TRS-80 Colour Computer 2.
Advanced stuff, like dealing with floppy disks, came much later if at all. The computer was a BASIC computer straight away.
Can you imagine the reaction* of people if you took a 256GB microSD card and showed it to them? Told them about the speed of the thing?
* to the kids out there, you'd first have to teach people of that era what a megabyte is (maybe), then explain what a gigabyte is (most probably). You could also tell them that this fingernail-sized storage device can store 256000000000** bytes or 347222 of their double-sided, 80 cylinders floppies. They would not believe you.
** manufacturers use power of 10, not power of 2. Get with the program already.
Of course designing hardware is hard! Look at Apple! Even with more money in the bank than small countries they are incapable of updating their computers properly every year! Hell, in 2014 they even downgraded the Mac mini! That's how hard it is to design hardware!
There's almost a half-dozen common artificial sweeteners on the market right now. Are they saying they're all bad or just a particular one? Maybe some of them? Was this research funded by the sugar industry? They're the new tobacco industry, after all. If you think this is a propaganda movie, think about the tobacco industry fifty years ago. And search for "sugar industry lies", plenty of facts out there.
Sent from my 2010 Mac mini because I'm not going to buy a used 2012 Mac mini nor an overpriced, underpowered 2014 Mac mini that was a pathetic can't-even-upgrade-the-RAM joke from day one.
You know when it comes to racism, people say: " I don't care if they're black, white, purple or green" Ooh hold on now: Purple or Green? You gotta draw the line somewhere! To hell with purple people! - Unless they're suffocating - then help'em. - Mitch Hedberg
Yes I have! President of the chess club in 1987, SIR!
Not needed. You people keep telling others to stop living in areas prone to flooding. Well, stop living in earthquakes-prone areas you numb-nuts.
That's because he hasn't picked a name yet.
Okay, AC. You win the Internet for today.
But only for today. Make good use of it.
The [URL] thing is done automatically by Slashdot.
https://en.wikipedia.org/wiki/...
I've seen similarly bad tutorials about templating. The way they teach how to cut your basic HTML and CSS apart in chunks is complete nonsense. They're showing people to always copy a whole empty framework and call cut-out parts all over the place. And then inside those cut-out parts, call out other parts. I've seen this done five levels deep.
It still works, but trying to way your way around all is extremely tedious. And if you need to make a change to the basic original framework, you're out of luck because the idiots made that code NOT part of a template and replicated it manually in all the pages of the website.
If a bridge collapses, do you blame the production workers who followed the plans exactly as they were or do you blame the engineer who was too lazy to make the proper calculations and didn't get the tests done for the bedrock foundation, etc?
You're doing the popular "snowflake attack" thing here, when in fact you're the snowflake thinking that everyone is as good as you are. The thing is, as I said, it's not everyone's job to be a security expert. We should expect security to be part of the tools instead of expecting everyone to be a security expert. The first is possible, the second will never be.
People learn not by memorizing but by looking at examples.
Most of the people working in Web-related jobs are not security experts, their job is to get things done as quickly and cheaply as possible. You might think in terms of huge corporations were IT is divided in groups, each working on specific parts of the whole. At the smaller scale though, the same person responsible for the front-end with HTML, CSS and Javascript has to work on the back-end with PHP and MySQL. The second their code does what it's supposed to do they just keep going to the next item to be completed.
So really, blame the examples and especially the tools. This is a similar problem to languages that allow you to point outside the bounds of an array or operating systems that can't protect themselves from applications gone rogue. Security should be part of the OS, part of the languages, part of the frameworks. Only then can you blame the coders at the bottom for security holes.
predict
prdikt/
verb
say or estimate that (a specified thing) will happen in the future or will be a consequence of something.
Touché, Gravis Zero.
To reply the thread, my vote is also for basic, specifically GW-Basic on the TRS-80 Colour Computer 2.
Can you imagine the reaction* of people if you took a 256GB microSD card and showed it to them? Told them about the speed of the thing?
* to the kids out there, you'd first have to teach people of that era what a megabyte is (maybe), then explain what a gigabyte is (most probably). You could also tell them that this fingernail-sized storage device can store 256000000000** bytes or 347222 of their double-sided, 80 cylinders floppies. They would not believe you.
** manufacturers use power of 10, not power of 2. Get with the program already.
Raspberry Pi to the rescue!
I wish it were sarcasm, but who can predict the future at this point.
I think they need to manufacture those computers to control the CNCs. Oh wait.
Of course designing hardware is hard! Look at Apple! Even with more money in the bank than small countries they are incapable of updating their computers properly every year! Hell, in 2014 they even downgraded the Mac mini! That's how hard it is to design hardware!
So they're going to copy your data from one cloud to another.
When will the madness stop?
Clouds... apps.... hosts... files.... must resist madn....... MOO!!!!
There's almost a half-dozen common artificial sweeteners on the market right now. Are they saying they're all bad or just a particular one? Maybe some of them? Was this research funded by the sugar industry? They're the new tobacco industry, after all. If you think this is a propaganda movie, think about the tobacco industry fifty years ago. And search for "sugar industry lies", plenty of facts out there.
If not, then in the future other countries might very well join the Chinese space station and China might ban the USA from joining.
Still in the same country counts as "local" to me. What if Russia nukes the whole of USA? Heck even the same continent is local.
Me: I don't want your clouds, why should I waste my bandwidth and endure slow access times when I can store my files and my backups locally?
It's horses all the way down.
Expensive outdated PC.
Sent from my 2010 Mac mini because I'm not going to buy a used 2012 Mac mini nor an overpriced, underpowered 2014 Mac mini that was a pathetic can't-even-upgrade-the-RAM joke from day one.
Slashdot, HackADay, etc...
You know when it comes to racism, people say: " I don't care if they're black, white, purple or green" Ooh hold on now: Purple or Green? You gotta draw the line somewhere! To hell with purple people! - Unless they're suffocating - then help'em. - Mitch Hedberg
If you don't like using excessive PC language maybe you could try excessive Mac language?
https://media.giphy.com/media/...