|
Security expert says we're in a cyberwar arms race, and with the Sony attack, North Korea has already taken the first shot at the United States. "We are Samurai... the Keyboard Cowboys... and all those other people out there who have no idea what's going on are the cattle... Moooo."
|
|
|
|
|
Need to provide a link to SchneierFacts.com as reference material.
|
|
|
|
|
Numerous recent blogs and web postings are erroneously claiming that an asteroid will impact Earth sometime between Sept. 15 and 28, 2015. Now I have to cancel that party
|
|
|
|
|
In fact, NASA's Near-Earth Object Observations Program says there have been no asteroids or comets observed that would impact Earth anytime in the foreseeable future.
Riiight. And that one that hit Russia last year, the NEOOP had no idea because it came essentially directly from the direction of the sun, which of course is a blind spot to the NEOOP.
Marc
|
|
|
|
|
Marc Clifton wrote: from the direction of the sun
Which direction is that?
|
|
|
|
|
PIEBALDconsult wrote: Which direction is that?
Up
|
|
|
|
|
Except at night, when it is down.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Even if there were an imminent asteroid impact, sure they would go and say "of course, you're right, it'll be the end of the world, go have some fun before it's too late". Let's face it: Every serious threat would be denied just as well.
|
|
|
|
|
The founder of Linux explains why he's not thinking about the next 10 years of Linux and why security is all about finding bugs. Linux has security problems?
|
|
|
|
|
I would say they are called users 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Enthusiasm for a technology is understandable, especially if you've had previous success. "All we are saying is give peace a chance"
|
|
|
|
|
Solving today's problem with yesterday's tools might not be that smart - but it is a lot smarter than solving today's problems with tomorrow's tools.
|
|
|
|
|
While I've seen failures in all, I have actually yet to see what I would consider a success with something written in a language other than C++ or C#, at least recently. And by success, I mean what's on the inside as well as what's on the outside.
Farcebook, for example, doesn't count, as according to Quora:
Most of it is written in PHP running on top of some software called HiPHoP they created, which basicly allows php to be compiled and run magnitudes faster.
Marc
|
|
|
|
|
There was a company that sold an MRP (Manufacturing Resource Planning) package called BPCS running on the IBM AS/400 and written in RPG.
Around 20 years ago, they were bitten by the Unix/C bug and decided to rewrite their software.
$400 million later (that was their annual sales, all from the RPG-based software, not profit), they went under.
|
|
|
|
|
Vivic wrote: they were bitten by the Unix/C bug and decided to rewrite their software.
Well, that was the problem -- Unix!
Marc
|
|
|
|
|
They still use it where I work.  Even twenty year old interfaces beat the pants off that monstrosity! Just the fact that I'm responding to a BPCS reference requires more 'unwell' emoteicons -
|
|
|
|
|
I remember some other company bought out BPCS.
I am surprised your company hasn't moved to Oracle or SAP.
My employer was using not BPCS but a competing package from Computer Associates.
Consultants came in and recommended SAP.
This was a company with $900 million in sales but our total product list was 400 products, customer list was 1,200.
On top of that with 2 major product lines each trading places every 18 months, we either had 7 customers or 100 customers.
It should have been run off a PC but connectivity for 250+ employees and security considerations dictated a midrange AS/400.
Management blew $40+ million on the SAP implementation!
Such is life.
|
|
|
|
|
Funnily, I once had to learn RPG as part of a similar porting effort. It went swimmingly, was completed in 6 months. I bumped into an old colleague recently and its still in use today and profitable.
ps. No one should ever, ever, ever, have to program in RPG.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Report Program Generator (RPG) is a joke perpetrated on the programming public by some IBMer.
As a name, I mean.
Very few people understand how this language came about.
The old IBM 407 accounting machines were controlled by a plug board where one wired up a "program" to perform specific calculations.
The program always would follow this following format:
Read a card
Use the values on the card and perform the required computation
Print a line of output
Repeat.
That is exactly the format used for programming in RPG. The idea was that you could get the folks who did the plug board wiring to program the IBM System/3 which IBM hoped would wean small companies away from the electromechanical relay based accounting machines.
Later more control structures were added to this cycle and you ended up with RPG IV but the basic cycle remains unaltered.
The interesting thing is that a machine like the AS/400 could "eat DEC's lunch", to quote Ken Olson of DEC.
Other than PCs, it probably is the only machine to reach sales in excess of 1 million. Today, you could network several of them together and such a network would rival the power of mainframes.
And like COBOL, RPG is another language that would never quit.
|
|
|
|
|
Yep, when dealing with RPG, its nature is very evident (at least to someone who, as a child, saw punched cards being used to program a computer, my mother learned programming as part of a maths degree, and we a fairly endless supply of punched cards around the house that were used as partly a study aid, partly as a construction toy).
I also remember that the first few columns of a source file (if "file" can be applied to something on the AS/400) were reserved for indicators, types (single letters) and other abuses. Probably the worst programming language I've ever come across (at least amongst those that are not intentionally bad, like brainfuck).
<<shudder>>.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
No matter what your style of coding is, it should follow one rule: Keep It Simple, Stupid! There is no silver bullet (but sometimes you just need a simple bullet)
But why is the article so long (and unsimple?) 
Also, where have I seen this clever fellow before? 
|
|
|
|
|
Simple Programmer wrote: Keep It Simple, Stupid!
FTFT
|
|
|
|
|
And it's 25% more simple!
TTFN - Kent
|
|
|
|
|
|
But I like calling people stupid... 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
