Nadreamia
category: general [glöplog]
double x = 1.6180339887;
while( x < 2 ) x = x * x - 1.0;
Is this an infinite loop?
while( x < 2 ) x = x * x - 1.0;
Is this an infinite loop?
Funny thing I just noticed: All people at pouet beg me to find a job. All people at cpcscene command me to wake up and code that CPC demo. I can't decide what to force myself to do. Of course this is irrelevant because I just posted something else on the oneliner and couldn't repost but also I know that you don't care and neither do I. Help!!!
Otianist: While looking for work, wake up and code that CPC demo. Problem solved.
Optimus: I think that users on both sites are doing their best to convince you to
1) Stop using them as your personal blog
2) Do something useful
3) Not spam them
4) See items 1 and 3.
1) Stop using them as your personal blog
2) Do something useful
3) Not spam them
4) See items 1 and 3.
Quote:
As a bonus, Naprola supports infinite integer types, as well as pointers with infinite range. Those are integers that grow in size accordingly, to be able to represent any number that can fit in the computer's RAM. These are recommended for huge projects like those for artificial intelligence when you don't want your machine's intelligence to be halted at a certain level because of the limitation of the size of types. Sure, your current computer might be limited to 32 bit pointers. But you don't want to have to waste time porting it to 64 bits like so many people are doing with their code these days. Just use infinite range pointers, and the code will work whether the CPU only supports 32 bit pointers, or 64 bit pointers, or some other futuristic number you can think of. Preferably, we would have future CPU's that natively support pointers of infinite range. Together with Naprola, this would mean that if your artificial intelligence cries out: "I want more ram please!", you just need to plug more and more ram to your machine while it is still running and whining without rebooting or recompiling any of the source code. Apparently, 640k is not enough for your whining artificial intelligence, and he might not be happy if you turn him off and recompile him while you copy him over from the 8086 over to your shiny new 386.
I suggest to change the name of this "Nadreamia" project.
This should be properly called "¡Madre mía!". :)
By the way... Optimus, do a demo about it!
I just had this idea for the best song in the world.
I will probably release it in two years.
You want some samples? ok, it starts in E major and it goes like "dum dum bee da da daaa"
I will probably release it in two years.
You want some samples? ok, it starts in E major and it goes like "dum dum bee da da daaa"
We need a little fado for Breeze's 2009 invitation. Are you up to it?
This thing remembers me to this other, the Nullix OS:
http://babelfish.yahoo.com/translate_url?doit=done&tt=url&intl=1&fr=bf-home&trurl=http%3A%2F%2Fpepixlabs.net%2Fciencias%2Fnullix%2FLEEME&lp=es_en&btnTrUrl=Translate
And its source code:
http://pepixlabs.net/ciencias/nullix/nullix
http://babelfish.yahoo.com/translate_url?doit=done&tt=url&intl=1&fr=bf-home&trurl=http%3A%2F%2Fpepixlabs.net%2Fciencias%2Fnullix%2FLEEME&lp=es_en&btnTrUrl=Translate
And its source code:
http://pepixlabs.net/ciencias/nullix/nullix
sol_hsa:
Quote:
it's not your API that's crashes, it's the app, right?
Some code providing an API can crash, and if that code is part of an app, then I would say the app crashed too. They don't have to be exclusive. It's not the same as an OS which is not usually considered a part of the application that runs on it.
Quote:
...but nobody even builds reliable hardware anymore. Nobody wants it.
I'm guessing that by "nobody" you mean "almost nobody". Surely you konw there exist some people out there who build and want reliable hardware.
Quote:
or alternatively it will just be slow.
Yes, it's somewhat slow if you compare it to an average API doing the same thing. I didn't spend much time speed optimizing the validation code at the third layer, and that's where all slowdown comes from. But it's not too slow for regular use. I've been using it just fine for little apps I wrote for myself. There's only one program I wrote that makes heavy use of the API, and I temporarily turned off the validation of some of the inputs for that app, until I decide to optimize the validation code. If you're writing a demo, your code would spend most of its time in the inner loops for the effects, so you woulnd't be calling the API often, and in this case wouldn't notice any slowdown.
My website is running on a cgi that runs on top of that API. Of course it's a very tiny website, but it's an example of something of mine that benefits from the API without suffering from the unnoticable slowdown. I only wrote this API for myself. And for my own uses, I find it very convenient. I don't remember it crashing a single time in the years that have passed since I wrote it. About the essay, I only wrote it for my personal friends that asked me questions about how it worked. It wasn't written for total strangers that are interesting in insulting others.
The API is nothing amazing, I don't understand why some people here act like it should be considered an amazing accomplishment. Lots of people have done it. I'm sure there are lots of guys in this thread that can write one for themselves if they want to spend the time doing such a thing.
I'm not interested in spending time defending something that I didn't even release for analysis! I don't even understand why people are trying to criticize code that they've never even seen. If I want people to analyze my code to verify that I haven't made any mistakes, I would've released it a long time ago, or would've asked my friends if they could verify it, and get some real criticism based on the code itself, rather than people trying to sell me perputual motion machines.
Quote:
how much past experience do you have of working on real-world, large-scale software projects?
"large scale"? Hmm... not much really. There is some "large scale" stuff, my own stuff, that I've been working part-time on, for the past few years. That's all.
Quote:
And have you seen one fail horribly, first-hand?
No.
Quote:
The fact that you'd even *consider* to write an essay about bug-free code, when it's not released or documented yet, makes me...
I only wrote it cause my friends were asking me how it worked. I wrote it for them so they have a general outline of the main design.
It's not a crime to write an essay on something that wasn't released. The essay wasn't published anywhere, which is hinted on by the page the links to it. I only told my personal friends about the website. I never advertised my website anywhere, which is why I was surprised to find a thread here talking about it. I didn't think anybody else would be interested in my personal website.
Quote:
and *still* say that you're completely confident that there are no bugs
I'm not actually "completely" confident right now. I'd only be completely confident if I'd actually go through the process of proving it. I've mentioned in the introduction to the essay that "I have not yet proven that it is uncrashable,...". I'm not the kind of guy who fully believes in stuff like this without proof, so I wouldn't be incredibly surprised if anybody found a bug in the current code. Though I would be somewhat surprised, since I haven't found anything wrong with it in the past few years that I've been using it.
I have just updated the essay. I added two extra chapters at the bottom of the page. "6- Speed" and "7- Availability" based on your feedback.
http://www.nadreamia.com/humanoid/essays/uncrashableapi
Thanks to everybody who took the time to read my essay.
Humanoid: I think the point is that this sounds like a lot of hot air (which you might not give a fuck about) and without actual code or example applications nobody will ever be really interested or learn something from it. So if you have something nice, you could make it available in some way to make others and YOU benefit from it...
Besides that I don't believe in "uncrashable" anyway...
Besides that I don't believe in "uncrashable" anyway...
Quote:
I don't even understand why people are trying to criticize code that they've never even seen.
Because you have the aura of a snake oil salesman combined with a somewhat douchebaggy and pretentious attitude, and no proof whatsoever to any claims, only allegations of how great the thing you've supposedly made supposedly is. Whatever it is, that is.
This is the demoscene, bragging rights need to be earned here. Making a pink website that's out of touch with reality and having nothing to show doesn't really cut it.
...and I tried being nice... :D
rare:
I don't care if people think it's hot air. I have no interest in convincing people that the stuff I haven't released, exists.
I benefit from it already, since I'm using it a lot. Like I say in the new chapter I added: "My goal was only to write something for my own use that I can depend on and would never crash on me. It has not crashed in the years that I've been using it, so I feel that I have accomplished my goal."
It would be nice if others can benefit from it too, but I don't consider it worth it, to write all the documentation for it, and polishing it up, and releasing it. It's just too much trouble, for too little benefit. The API is custom designed for my own use. Each person has their own requirements, and many people can write an uncrashable API that fits their requirements if they spend the time doing it. My uncrashable api is NOT something amazing. It definitely doesn't compare to a perpetual motion machine as some people here might think.
Quote:
I think the point is that this sounds like a lot of hot air (which you might not give a fuck about)
I don't care if people think it's hot air. I have no interest in convincing people that the stuff I haven't released, exists.
Quote:
So if you have something nice, you could make it available in some way to make others and YOU benefit from it...
I benefit from it already, since I'm using it a lot. Like I say in the new chapter I added: "My goal was only to write something for my own use that I can depend on and would never crash on me. It has not crashed in the years that I've been using it, so I feel that I have accomplished my goal."
It would be nice if others can benefit from it too, but I don't consider it worth it, to write all the documentation for it, and polishing it up, and releasing it. It's just too much trouble, for too little benefit. The API is custom designed for my own use. Each person has their own requirements, and many people can write an uncrashable API that fits their requirements if they spend the time doing it. My uncrashable api is NOT something amazing. It definitely doesn't compare to a perpetual motion machine as some people here might think.
![[self-ban]](https://content.pouet.net/avatars/zulthoofd.gif)
Quote:
Because you have the aura of a snake oil salesman...
Am I selling anything? NOPE.
Quote:
only allegations of how great the thing
Did I say anywhere on my essay, that my uncrashable API is "great"? NOPE
Please stop making false assumptions about me, and putting words in my mouth.
For such a scientific man as yourself who has interests ranging from cold fusion research to nanotechnology to cutting edge artificial intelligence research and eradicating all disease from mankind, you're only too modest. To revolutionarize the world, it simply has to be great. Otherwise, we are forced to conclude that your claims are dubious as best, and with a person of your stature, that simply will not do. How could a person with such talents do something that's not utterly fantastic is totally beyond me.
Quote:
...we are forced to conclude that your claims are dubious as best.
You have absolutely no reason to believe anything I say. Why should you???
Why do I even have to mention this?
Quote:
You have absolutely no reason to believe anything I say. Why should you???
Are you saying that you might not be telling God's honest truth on your fine website that's running on top of an uncrashable API, a feat of computer engineering like which there's no other? What happened to all the revelatory insights and the total upheaval of modern science? Alas, I fear that the modern world will be doomed to shortage of food, pestilence and lack of cheap energy for an indefinite time period still, until some modern Leonardo da Vinci comes to save us and the rest of mankind from its peril. But for a while, we had a hope, a shining star in the horizon of our dreams, a glimmer of a bright future to strive towards to, and for that we have you to thank for, kind sir.
Do I also gather that there's no hope of Naprola, the programming language will change Everything, or do us mere programmers of modest stature need to stick with contraptions like C++, Python and Java still? And do we need to be stuck with our ordinary, crashable APIs, even though they make us pull our hair out and cry in despair in the middle of the night, or wake up in cold sweat in the hour of the wolf?
Quote:
Are you saying that you might not be telling God's honest truth on your fine website...
No. I'm not saying that. Stop putting words in my mouth.
Everything I say on my website is true. What I'm saying is that you don't have any reason to believe anything I say.
Can you understand the difference? Do the two sentences look the same to you? Cause if they do, I don't think there's any point in trying to reason with you anymore.
i still would like to see at least a few lines of code in Naprola
Quote:
Everything I say on my website is true. What I'm saying is that you don't have any reason to believe anything I say.
Ergo, nothing in your site is true. Thanks.
Gargaj:
Thanks for the interest. But like I said before... you'll have to wait at least 2 years. I'm only working on it part-time.
Quote:
i still would like to see at least a few lines of code in Naprola
Thanks for the interest. But like I said before... you'll have to wait at least 2 years. I'm only working on it part-time.
you mean there's not even a "hello world" in it? :(