Re:Design and Implementation of a 256-Core BrainFuck Compute...
by qwertyuiop924 on Sunday October 16, 2016 @03:32PM
(#12720485)
Given, QNX never really caught on in the wider field of computing AFAIK. This may lend credence to the Godot team's theory that public visibility is based upon how big you are (https://godotengine.org/article/godot-aims-mainstream).
[ Parent
| on HN ]
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by nickpsecurity on Sunday October 16, 2016 @03:44PM
(#12720543)
I was talking complexity vs size. Gabriel's Worse is Better already tells you that growth has more to do with network effects and marketing than technical correctness. QNX lacked them for desktop or server use but did well in embedded. Almost had a mobile shot but Blackberry blew it totally with marketing plan.
EDIT: Read Godot. That was hilarious but I kept seeing too much reality in it.
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by qwertyuiop924 on Sunday October 16, 2016 @04:27PM
(#12720757)
Of course. My post was less about how QNX's lack of popularity subverts your point (it doesn't), and more about setting up that punchline.
There's quite a bit of reality in the article, but not quite enough to depress me. Maybe you've seen more of this sort of thing than I have.
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by nickpsecurity on Sunday October 16, 2016 @06:54PM
(#12721542)
Ahh gotcha. Far as other thing, have you seen the Web and enterprise BS getting lots of adoption since big names tried them out? And the drift to incomprehensible frameworks with huge dependencies that one can barely maintain with similar security problems and a tiny fraction of efficiency of C++? And now more of them as SaaS? Just thinking there's lots of that bullshit in the article going on in real life. It's that or legacy SAP, Oracle, COBOL, MFC BS. Competing BS exists but sanity gets rarer and rarer.
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by digi_owl on Monday October 17, 2016 @08:39AM
(#12724484)
Outsourcing was done with great care by a few big name corporations. And after their apparent success every two bit public traded company went on a "me too!" outsourcing rush to try to goose their share value.
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by nickpsecurity on Monday October 17, 2016 @11:44AM
(#12726045)
I'm not aware of its early history. Which were the ones that pulled it off first?
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by qwertyuiop924 on Sunday October 16, 2016 @08:10PM
(#12721843)
Oooh. That. I get a miss on a lot of it, because I'm not in industry, and I avoid Java (the natural focal point of incomprehensible frameworks), and frameworks in general.
On a daily basis, the worst I have to deal with is SystemD, which is creatively incompotent and best, and downright insane at worst. But it's got a pretty face, and the draw of easy-to-understand unit files (over, say, SVinit), so people don't realize the depths of the madness that lies beneath.
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by digi_owl on Monday October 17, 2016 @08:37AM
(#12724467)
> Gabriel's Worse is Better already tells you that growth has more to do with network effects and marketing than technical correctness.
Something that can readily be observed in action with systemd.
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by qwertyuiop924 on Monday October 17, 2016 @08:41PM
(#12731120)
...Exactly. It sure as heck didn't get into distros on technical merit, because it has none.
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by digi_owl on Monday October 17, 2016 @08:36AM
(#12724456)
Why license an OS when you can grab it for free (beer)?
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by nickpsecurity on Tuesday October 18, 2016 @02:57AM
(#12732635)
Had less attack surface (microkernel), isolated failures, easier to upgrade, and could be self-healing within one node. Important to some people. They kept paying for it until numbers justified RIM buying it for its potential. ;)
Re:Design and Implementation of a 256-Core BrainFuck Compute...
by qwertyuiop924 on Wednesday October 19, 2016 @07:53PM
(#12748764)
Indeed. It's one of the Microkernel architecture's (semi-rare) success stories. It goes to show that yes, Microkernels are complicated, and hard, but if you pull it off there are real benefits.