News for hackers. Stuff that matters.

easter6

Re:Why Is It So Difficult to Develop Drugs for Cancer? (2010) on Wednesday September 30, 2015 @03:02PM (#10306271)
I had to look up what immunotherapy is... not sure if it would do much good in my case, because I don't have much of an immune system at this point. I've already quit chemotherapy.. think I went 6 rounds before 'throwing in the towel'. Seems pointless to postpone what is inevitable, but I can understand how some might want to hang on.. particularly if one is married and with children.
Re:Why Is It So Difficult to Develop Drugs for Cancer? (2010) on Sunday September 13, 2015 @12:36AM (#10210364)
early detection is great, if you're being specifically checked for cancer. the problem is that you can have tumors growing inside you for years, and during that time, the effects of those tumors may lead your doctor to misdiagnose the problem. And by the time those tumors make themselves painfully obvious, you've got Stage 4 cancer which is pretty much a death sentence.

In the US you can order your doctor to arrange a cancer screening for you (scan or blood test), if you are worried you may have cancer. It's your money, after all. In other countries such as Canada, that's not so easily done. You're at the mercy of whatever doctor you've ended up with, and that doctor is not going to do anything for you unless it makes sense to him.

This has basically been my experience, anyhow. Thanks to my doctor's inaction I have maybe 6 months to live.

Re:GEOS For the Commodore 64 on Saturday September 12, 2015 @10:54AM (#10208235)
And in that same year you could get a sub-$600 machine that could do more than that C64 or Mac: the Atari 520ST! :)

of course the Amiga could do more than all 3 machines, but it cost even more than the ST (but nowhere near the cost of a Mac.)

Re:A Chronology of Microprocessors on Saturday September 12, 2015 @10:27AM (#10208172)
also missing is the Four-Phase AL-1 which was operational by 1969, a year before the F14 Tomcat processor design was completed.

The AL-1 came almost 2 years before Intel and TI's first microprocessors debuted and ran 10 times faster than those chips.

Well if nobody is passionate about it, nothing will change. I'm sure I look like a fool for it, but someone has to.. might as well be me! :)

My interest in AI and computer architectures never went away.. I just decided not to turn certain interests into a career, and walked away from the chance to be gainfully employed as a programmer. At the time I felt there had to be a 'better way', and I've been trying to come up with that 'better way' ever since.

I'm probably somewhat bitter that my research (probably) won't get translated into something physically tangible and complete, as I'm running out of time. Cancer is unkind that way.

It's entirely possible that I've been chasing a pipe dream all these years though, and while that would be a shame I'm realistic enough to entertain that notion. I've already accepted death, so at this point I can accept this, too. But of course I don't really believe that is the case here. ;)

Re:All Scientists Should Be Militant Atheists on Friday September 11, 2015 @08:35AM (#10203271)
Real scientists recognize Atheism as being illogical as both it and Theism are based on faith.

The Agnostic position is the only logical position one can take, as it is not faith-based and it makes an assertion that is true: we don't really know if a God(s) exist or do not exist. There's no proof that one does, and there will never be proof that none do.

yeah, my bad. thought you were the guy above me. Apologies.

As for the career I chose, you can assume it wasn't anything to do with computers, lol. (Although I almost went the Cognitive Science/Computer Science route back in my younger days, before realizing I wasn't nerdy enough!)

A computing architecture doesn't need to use a language.

The language is there for our benefit, not the machine's. I'm merely suggesting that all these (by now, countless) languages are getting in the way of efficiency. If we have something in mind that we want the computer to do, why not just do it in hardware directly, as that would provide the most optimal efficiency?

I don't 'feel similarly about written language', because written language is kind of important for human communication. Last I checked, human brains have very little in common with computers and our capabilities are not the same as a computer's. We are not computers, we're social organisms. So we need written language. One could even say that we need written language to do 'our work'. Society would fall apart without it.

But I guess if there were a better way to communicate or record/relay our thoughts to others, I'd be all for it.

I'm curious why you think things can never change. Maybe you can't imagine anything different. That's OK, other people will drag you into the future.
Wheels are the most effective way to transport things on land. So of course it's in our best interests to keep improving that wheel.

Certainly, language is useful when hashing out a problem on paper (be it pseudocode or math equation or whatever). The abstraction is convenient. But programming languages are not a requirement for computers to do their work. Languages exist for our benefit, not the machine's. One can use software to do work on a computing architecture, or that same algorithm can be implemented in hardware and run a hell of a lot faster.

The problem is that, while we can come up with all kinds of algorithms, we can't seem to agree on what programming language to use when implementing those algorithms. I guess I'm arguing that the languages are getting in the way of the algorithm, and it would be nice if there were a way to achieve something closer to a 1:1 relationship between algorithm and implementation. We're always going to be inventing new programming languages because we can't reach a consensus on what is the 'best' abstraction. It's become ridiculous at this point.

Algorithms are currently expressed by programming languages because they have to run on general purpose, programmable von Neumann architectures. I mean, yeah we could skip the language and just input machine code, but that would of course be ridiculous. That's why we use compilers.

If there were an easy way to implement algorithms directly in hardware, why would we bother with programming languages?

Take, for example, a supercomputer. If the kinds of work a supercomputer does could be implemented directly in hardware, I think it would be safe to assume that researchers would be all over that. The gains would be enormous.

If there were a hardware-only 'Travelling Salesman' algorithm that showed astronomical gains in efficiency compared to the conventional software implementation, don't you think that would be important and useful?

Well, even today there are computing devices that don't require an ordered series of logical steps (in the form of program code) to solve problems. So you don't need to wonder about it. The future is already here.

However, there could one day be a means to easily implement algorithms in hardware.

To clarify, I'm not thinking of ASICs or FPGA's, which of course already exist and have for quite some time. Neither are very 'easy', and the expense is real.

Just out of curiousity, do you honestly believe that the way we've been getting computers to 'do things' is never going to change?

Today's computers are limited in what they can do, by way of their architecture's constraints. The von Neumann architecture has served us well up to this point, but going forward it's going to be a real handicap. But it isn't just the architecture that needs rethinking. As you say, 'we probably won't program these new machines in the traditional sense'. And you're probably right. Programming languages are also part of the problem. We've wasted so much time reinventing the wheel, over and over again. I don't know what form the next computing architecture will take, but I do know there will come a time when the notion of using a 'programming language' to get things done will seem quaint. Hell, I thought it was an archaic way of doing things 20 years ago, and it's why I didn't pursue a career as a programmer. The tedium was incompatible with my temperament!