Tell me which bit of my post was not factual?
612 karma · joined January 23, 2012
Tell me which bit of my post was not factual?
Please at least spare a thought for those around the world who are too busy trying to stay alive on this day to worry about a new monolith to worship.
I like technology, but I'm a human first.
Here in the UK, the free ones on the NHS are pretty good! If you don't want treatment, noone is going to lose any money (in fact they're saving cash) so you're fine.
If you could start again, would you really end up with HTML5?
I'm sure that and the rest of the process wasn't beyond people with a higher budget and requirements...
As for plants - it's all knowledge and experience. There is no abstraction. Eat this, don't eat that. I grow quite a few edible plants myself and there is little abstraction.
It'd be a better performance improvement to rewrite the stack entirely in C than change the web server and that's just illogical.
To be honest, the bedrock abstraction should stop at "what humans can realistically create with their own hands from nothing". You can make your own transistor quite easily and Ebers-Moll provides a nice set of rules to work with.
The quantum physicists and philosophers can remain arguing about technicalities then and let the rest of the world observe, understand and create.
application -> xaml -> framework -> server -> container -> c# -> cil -> bytecode -> x86 instructions -> microcode.
Now forth on a 68000:
Forth screen -> 68k instructions
To be honest, for what I consider to be life and death stuff, a 10MHz 68000 is good enough (I have one in my TI92 calculator).
3d printers are supposedly promoted as printing themselves i.e. as self-replicating. They are not. They print a small fraction of their own non-complex parts.
They were and still are extremely powerful and productive machines.
[1] http://en.wikipedia.org/wiki/BBC_Micro_expansion_unit#ARM_Ev...
I (the parent of your post) actually have a BBC Master (and the advanced reference manuals) lying around still for precisely that reason. It's quite a handy and very powerful little machine to be honest.
It even runs LISP (AcornSoft LISP).
To be honest, the "complete understanding" died way before the original post. It was the moment that they started building computers with integrated circuits inside them (before 1970) and complexity rocketed logarithmically. It died doubly so the moment that electrical engineering and the practical side of computer science diverged into "them" and "us".
If you want to use something which you understand, you will probably need to buy a crate of transistors, resistors and diodes and wirewrap yourself an entire computer from scratch PDP-7 style.
This fact is a warning: We really are building things with too deep abstraction hierarchies causing knowledge to be divided. One day we will never hope to comprehend anything in a lifetime.
Now I feel old.
If you take the UK as an example, a lot of the country (outside major cities and metropolitan areas) is still stuck on 512kbit. The same is true worldwide with even parts of SA on dialup. Shouldn't we be concentrating on throwing more resources into getting these connections usable rather than feeding crazy large bandwidth to the rich?
As the broadband speeds are controlled pretty much by consumer demand, isn't it better to have more people than an elite few?
On the same subject, I'm sitting here on approximately 12Mbits and I genuinely have no problems with it streaming HD iPlayer and with three computers on it. I don't need any faster and it costs a whopping $20 a month equiv (unmetered consumption).
Also, if you consider the cost of bandwidth and caps thrown on people in Europe, a gig connection would suck up your entire allocation in about 48 seconds...
That was the tastiest thing I'd ever eaten!
At the same time, I don't know why I do eat meat now but I seem to crave/need it and just can't shift that. I don't usually actually like it either ironically (apart from that one quarter pounder above).
I'm doing some in depth analysis to see if it's a suitable replacement for C#/.Net framework in our current application stack (message oriented CQRS architecture, web front end). We're doing this by rewriting a chunk of the stack in it and seeing where we get to.
At the moment, it's a very good fit. The time to market is an order of magnitude less than .Net framework. The tooling and mindset is cheaper and easier to maintain and we're not having to invent many solutions to problems - they are already apparent (or just not required).
The only trouble so far has been availabiliy of quality persistence libraries for database engines.
I'm not going to write anything up though until v1 is out and I've ported everything to that and tidied it up.
I don't know if it scales up linearly as the codebase grows yet. This is my only real worry.
It's terribly useful.
What you do is read the voltage you want from the device, turn the knob to the voltage you want and plug it in!
It was made in 1977. It works like the day it was bought i.e perfectly. I don't imagine a cheapy switch mode supply making it to 35 years old.
With regards to the "sweet DC juice" - it'll be full of noise if it's a switch mode supply. They're horrible devices that cause all sorts of local RF interference, noise and transients on the mains. Sometimes more than chucking an inductive load like a hoover on the line.
The only positive things is that they are small and cheap. They are definitely not good.
Also a switch mode supply does have a transformer! Just a small one.
However, I don't find that a problem. I tend to prefer the correctness of statically typed languages these days.