Q:	I've opened 10 windows. Conholio feels jerky.
A:	Don't be a jerk.
	 - Use tabs instead. It's faster.

Q:	I've opened 10 windows, and Conholio uses 67 gigabytes of RAM.
A:	Each window requires an offscreen buffer used for fast text rendering.
	 - Use tabs instead. It's faster, and uses less memory.

Q:	I have a 16MHz Falcon. Conholio is slow.
A:	Yes it is. It's designed for faster machines, and really needs Fastram to be able to perform well.

Q:	I heard Conholio is a hack because it uses menus in windows.
	Is this true?
A:	No. But the window menu API implementation in XaAES stinks, and I'm forced to use it.

Q:	I heard Conholio is a hack because it renders graphics in a device specific off-screen buffer.
	Is this true?
A:	This is perfectly legal and is even mandatory in many screen modes.
	It's also the only way to get fast output on machines with poor video bandwidth.
	It would be better to use VDI-based offscreen buffers, but several VDIs lack this functionality.

Q:	Have you seen my tin foil hat?
A:	Ah. Paul, you need to take your meds.