![]() However compare that to operating system development - or to be more specific: reverse engineering undocumented APIs that receive updates every few years - and you have yourself a whole order of magnitude more difficult job to even just reach a usable parity let alone being a competitive alternative.Īs quickly as ReactOS developers can reverse engineers Windows, Microsoft will progress their flagship OS. This has made it easier for open source competitors to catch up with Microsoft. Often just with pointless UI tweaks in the aim of milking their proverbial cash cow. But feature MS Office reached a plateau in the late 90s so a significant amount of work since has been about user experience instead. Sure there have been some noticeable advancements such as the introduction of ribbon bars and zipped XML documents replacing undocumented binary blobs. The office suite market in general has been relatively stagnant over the last couple of decades. ReactOS has been around at least this long, and due to the nature of the project isn't quite as fast, but each time I read a new release it occurs to me that development is accelerating rather rapidly! So give it time - it's been just over 16 years since it the StarOffice source was opened to anyone. Since then has stagnated and withered on the vine, whereas LibreOffice has had entire swathes of old and cruddy code rewritten and each point release has not only got huge numbers of bugs fixed, but often new features - and often entire subsystems have been rewritten without the end user ever knowing. Then Oracle bought Sun and really pissed off key external contributors so they forked the product and in 2011 The Document Foundation was formed to oversee LibreOffice development. Then the OpenOffice developers and Sun started stymying contributions, and eventually Michael Meeks setup Go-OO with a bunch of patches that made the program easier to use. By 2004 was making steady progress, and had captured quite a bit of market share. StarOffice was open sourced in 2000 by Sun as and started somewhat slowly. These things start off very slowly, and then tend to somewhat exponentially grow and improve over time. (I'm explicitly not comparing the feature set, which stems from different usecases or ease-of-use, which is somewhat subjective: this is in comparison of rudimentary editing operations) JOSM, on the other hand, is not quite native (Java being a memory hog of its own), but is capable to use persistent caching and relatively efficient memory structures. iD has very low barriers to entry: it's all in-browser, integrated with the website, nice rounded corners, and no dependencies - but it's slow and unable to keep up with edits > 500 nodes (because it's a memory hog built on a memory-hog JS framework running in a JS+DOM memory-hog virtual machine inside a memory-hog application). It works, yes and I'm glad I'm not getting as many "Linux? Go away" issues these days yet the bloat and latency of web-stack is something that remains largely unadressed in 2017.Ĭase in point: OSM editors. That's very nice, but I feel that the price we're paying for running the Web-stack on top of normal application stack is atrocious, especially where a native, local application would be far more efficient. There are not versions released for Windows 10 yet (and will there ever be? It's a constantly moving target). I recommend buying Windows Internals 6 volumes 1 & 2 to understand what is going on, at least under Windows 7. It is very odd because Microsoft has its own SQL Server division (and SQLite is free if they want to use that!) as well as embedded SQL Server for file-based database systems yet their start menu search is horribly slow so as to be useless (for me at least). I have found it to be slow to type something into the Start menu (just type), particularly compared to the results from Everything (mentioned above) or Apple's Spotlight. This is meant to make Cortana be able to give you helpful results when you search for things like files locally. ![]() I believe this is similar to the Indexing Service found on Windows XP that would give you hopeless results (duplicates between its database and the actual file system). There is the NTFS MFT which is used by tools such as Everything by "void tools", but Windows also has its own Windows Search (WSearch) service which indexes files and contents. It could be the indexing service for files. Did you ever run a profile to see what was going on? Or run ProcessMonitor to see what was using the disk etc.?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |