Новые сообщения [новые:0]
Дайджест
Горячие темы
Избранное [новые:0]
Форумы
Пользователи
Статистика
Статистика нагрузки
Мод. лог
Поиск
|
13.11.2013, 16:37
|
|||
---|---|---|---|
|
|||
Новый стартап в мире M(umps) - Mole, MemCog |
|||
#18+
Кто еще не знает - читайте - www.memcog.com :) Раннее было просто Mole, а еще ранее Atmus... И регистрируйтесь там! И комментируйте здесь! ... |
|||
:
Нравится:
Не нравится:
|
|||
|
11.12.2013, 17:24
|
|||
---|---|---|---|
|
|||
Новый стартап в мире M(umps) - Mole, MemCog |
|||
#18+
Если кому то интересно по этой теме: ответ на запрос по ней We have a 12 month roadmap for 2014. The main dates are for a beta release in the summer and a stable 1.0 release towards the end of the year. We are only able to deal with a small group of alpha testers which is why we are not actively promoting or advertising at this stage. The alpha release is probably going to be nearer the back end of Feb and I will be in contact nearer the time. Out of interest what is your background with Mumps and have you used the GT.m version. Mole is currently being developed on top of GT.m and will be ported over to other versions such as Caché. I was also wondering if you had any connections with the MiniM database. I have a customer who needs Mole to run on windows platforms and I have been looking at MiniM as a reasonably priced candidate, although I have yet to asses the technology. Would also be interested to know what sort of plans you might have for something like Mole. The motivation for Mole began as a personal need to do innovative solutions on a web scale environment. However, I am getting lots of interest from my old field within the health industry and will looking to ensure it has the right features for healthcare application development and modernisation of old M solutions such as the VistA patient system. Is there any specific feature that you would be looking for in version 1.0, we might be able to incorporate any suggestions. Mole could be categorised in the NoSQL group of products. There is a plan to plug in ANSII SQL into the database engine at some point, perhaps KBSQL. However, the emphasis will be on Moles innovative database features, adaptive indexes, its own MQL query language which is very simple and powerful. In terms of speed, it will be interesting to do both simple and complex benchmarks between Mole and something like MongoDB. I suspect they will perform very similar on the simple benchmarks, but then Mole will outperform the NoSQL world once you start to do complex joins and applying business logic to the data. Mole optimises the entire stack, whilst NoSQL are still dependent on other technologies. A stack is only as quick as its slowest moving parts. Mole is designed to not have any bottlenecks or unnecessary moving parts that traditional stacks suffer from. The only thing Mole wont have out of the box is mapreduce. If there is a demand for this at an early stage then I will look to escalate this feature. If not then I suspect it wont make it into version 1.0. I'm not sure its a feature I would use, even though I do want to scale data in a big way. I have other features going into the library which will get the same result, and of course something like GT.m will scale vertically very well. Thanks for keeping interest and being patient, its been a long haul to get funds in place so the project can go into full time production. Next year is going to be a very exciting year and I hope to shake up the old Mumps industry in the process. ... |
|||
:
Нравится:
Не нравится:
|
|||
|
04.03.2015, 13:17
|
|||
---|---|---|---|
|
|||
Новый стартап в мире M(umps) - Mole, MemCog |
|||
#18+
Забыл скинуть текст письма (октябрь 2014) Hi Sergey, Still plugging away. It's been a busy summer juggling contract work as well, but currently putting in long hours. I am aiming for a release before the end of the year, essentially release what I have and start moving into an agile release cycle, adding new features every month. The current status:- 1. Almost completed a dedicated web based IDE for developing Mole (and Mumps code). This will be an editor on par with Cache studio with more customisation. This will make editing against GT.m a breeze, especially when editing remotely (my vision is for Mumps in the cloud - where I have just recently moved all of my Mole development to). 2. Still tweaking around with the language specification and compiler, adding new features. There are a couple of essential ones that I must implement before Alpha. 3. Dashboard is half built. This is part generic for managing Mole and Mumps, but also to implement Mumps specific management (namely GT.m). This might not make Alpha. 4. The core library is growing. Currently supports web frameworks (JSON, REST etc). Comprehensive Types. I need to improve the cURL abstraction as it could be more OO like. Linux calls etc. I do have a persistence engine (like Cache %persistence), but I will hold this back from alpha release as it needs much more work and testing. I am also working on an external bridge to call other ODBC database from Mumps via a cURL > REST > JDBC bridge. So lots of potentially cool stuff getting into alpha. I haven't even made a start on documentation yet, and may not get much done for Alpha release. I also want to make sure that Mole compiles on to one other M implementation (other than just GT.m), to demonstrate the idea of Mole being a standardised OO implementation of M, as opposed to being vendor locked. I know this will go down well with the likes of the VA and VistA in the states. Just wondering what version of Mumps do you use most. Have you worked with MiniM much, as I really like the look if it. I might chose this version over Cache first, so as to not worry Intersystems too much in the early releases. Regards, Sean. ... |
|||
:
Нравится:
Не нравится:
|
|||
|
|
start [/forum/topic.php?fid=39&tablet=1&tid=1556712]: |
0ms |
get settings: |
9ms |
get forum list: |
14ms |
check forum access: |
3ms |
check topic access: |
3ms |
track hit: |
49ms |
get topic data: |
11ms |
get forum data: |
2ms |
get page messages: |
36ms |
get tp. blocked users: |
1ms |
others: | 14ms |
total: | 142ms |
0 / 0 |