2,589 karma · joined May 25, 2012
I had to chuckle. I remember back in the Windows 3.11 days, there used be a separate monochrome set of icons for all Windows (and Microsoft) programs.
Sun Microsystems had this. Didn't work too well for them.
It's not at all as simple as this.
This is one of the reasons why people write custom allocators - to suit a specific purpose where the allocation pattern is known well in advance.
Debugging it is great fun as well.
Apple was an early adopter of the standard. I remember when being amazed at being able to use a Bluetooth keyboard in the EFI!
Source? It's always stood for Gnome Toolkit. You must be confusing this with the GDK (GIMP Drawing Kit) that's between the library layer and the display server. The GDK is part of the toolkit.
P5 Pentalobe screwdriver: https://en.wikipedia.org/wiki/Pentalobe_security_screw
- Fields, or anything that uses fields: They're completely broken. They only seem to function in straight-forward case. For e.g: it's very easy for sequences to completely go off whack.
- File comparisons: this feature can only tolerate up to a certain number of pages. It will crash and burn for large documents. I sometimes wonder why this is even offered!
- Formatting: No matter how carefully paragraph spacing etc. is controlled there are always instances where things won't work as intended. A good example is cover pages.
- Hanging and freezing on large documents while Word figures out how to render them.
- Font rendering: it's never great. It never looks the same as what it would on a printer (irrespective of the printer). The Mac version does a decent job, but the Windows version, even with ClearType configured, is not great.
- Lastly, my biggest issue: feature incompatibilities between the versions of Word available on Mac and Windows. The Mac version (the latest O365) release doesn't have a lot of advanced features that are available on Windows such as document signing and style breaks.
For any serious writing, Microsoft Word is one of the worst pieces of tools out there. It starts showing its ugly side when start using anything remotely advanced.
Also, from what I can see, the documentation seems to be in Chinese: https://lcui.lc-soft.io/guide/zh-cn/
I do agree about the expensive programmers though. However, there were people out there who wired up their own using the STK200 configuration and put the schematics online for the community's use.
Programmers (irrespective of micros) have always been relatively expensive - even the home-brew ones. It's only recently (say in the past 5-8 years) they've become cheaper thanks to people's interest in hobby boards like the Rasberry Pi.
The biggest problem was the availability of JTAG debuggers. Atmel had the reference, closed-source implementation. Although the community managed to eventually reverse engineer their implementation and cheaper ones became available on eBay (usually from China).
Computer Systems: A Programmer's Perspective: https://www.amazon.com/Computer-Systems-Programmers-Perspect...
It's one of the best books ever written on this subject.
One of my courses at UQ (Australia) followed some of it and I'm glad that I took it. There's no better way to asses the skills involved in debugging/analyzing machine dumps than the binary bomb assignment.