You should put this up on your site as a link to "Technical Details"! For anyone who knows networking stacks, this really clarifies the features/benefits and also shows there is some substance behind the protocol/stack. Otherwise, like everyone else pointed out, the web-site itself doesn't provide a clue as to why one would use this.
Maybe the consciousness of a baby is different from that of an adult and the baby has barely any consciousness? I guess everything depends on what you define as "consciousness".
It would be useful if the web-site had a real case-study where they show all the features in action. Right now it looks like vaporware -- like one of those sites people put up to see if there is interest in an idea.
And perhaps stuff like this should have on-site capability for enterprises that don't use github, gitlab and such?
> It would be useful if the web-site had a real case-study where they show all the features in action. Right now it looks like vaporware -- like one of those sites people put up to see if there is interest in an idea.
True. We'll add better images and case-study to avoid the confusion.
> And perhaps stuff like this should have on-site capability for enterprises that don't use github, gitlab and such?
I'm assuming you are talking about GitHub Enterprise, Gitlab Self-Managed and Bitbucket Server. We currently have support for Bitbucket Server and working on the rest.
I am not sure why a lot of the comments here are very negative. At least for me this was a well-written post that was very introspective and made me think about my own choices and if I was a lotus-eater or a pursuer of Ithaca!
But I think the point being made is that eating the free-lunch makes you "weak" (weakens your resolve) on your journey towards your Ithaca -- illustrating exactly the point being made about being a "lotus-eater".
And my point is that doesn't have to be the case. You can eat a free lunch at your current job without being weakened or distracted in any way.
It's good to keep your end goals in mind and make sure you aren't deviating from a course that will get you there, but a logical conclusion of taking this blog post literally (which many people are doing, because there's no obvious reason not to do so) is that the author is severely misguided at best.
I think part of the thing that people complain as complexity is the fact that there is too much choice in the web world and no one framework/tool/language is dominant and clearly better than the rest.
What GUI toolkit is used for the IDE? Is the IDE multi-platform? I tried the Windows application and it had complaints about Visual Studio not being found when building the sample app. What's the dependence on Visual Studio about? Also the IDE died in a unrecoverable way when trying to do a single-step on the first sample application.
The GUI is custom. The IDE is Windows-only at the moment, but there's also a command-line compiler for other platforms. VS is required for linking (even when using the LLVM linker).
I'd be interested in more information about the IDE crash.
Advice from a fellow dev: add a crash handler and set it up for an automatic submission of crash reports (symbolicated callstacks of all threads) via HTTP POST to a server.
Better yet, turn it into something that others can use easily by configuring things like the server to which send the reports.
How much work is it to port the IDE to other platforms?
The IDE is maybe one of the nice/important aspects of this project, but then this really should not be Windows-only. Or maybe that are your priorities, but then I would not expect that it gets much adoption outside of the Windows world, but maybe this is ok for you.
I picked the same and use the menu to build, but I don't have VisualStudio, so perhaps the sample didn't really build. Then I was clicking around the menu and chose the Single-Step option on the menu (F11? F10?) when the IDE crashed.
See the answer nabla9 gave. There is no real truth and the idea really is to just meditate and not worry about the truth or the nature of truth. So there is no point in the questions themselves.
No offense but this is incredibly unhelpful and useless to say. Maybe some people can pull it off but most people won’t make progress without some guidance. In addition most of us don’t live in a monastery or are independently wealthy so we have to live in the world and somehow find a positive path through it. Telling people to meditate and not ask questions is completely unproductive. Buddhism has a long history of inquiry and debate for that reason.
You need guidance for different reasons too. Vipassana meditation is serious business, and the early, 'easily'-reached stages that these first workshops tend to focus on (e.g. the 'Arising and Passing Away' stage, often mistaken by beginners as "enlightenment" itself) have a way of leaving you psychologically vulnerable to a sort of spiritual crisis, which is sometimes called the 'Dark Night of the Soul'. This problematic stage can and should be overcome by further developing in 'insight', but the whole thing is a lot easier and more comfortable if you know what to expect! AIUI, this is Ingram's main criticism (of sorts) of these workshops.
So you can use all the zillions of existing extensions/scripts, it really only makes sense to rewrite using VimScript as the scripting language to make it faster. Then you have a built in user base.
But according to the README, the new language is syntactically incompatible with the old VimScript. So you can’t reuse those extensions, they have to be rewritten.
Yeah, I didn't notice that. If that is the case, then perhaps there is no purpose in creating a new language. Perhaps the only benefit to creating the new language could be that it might be a little easier to mechanically convert from the existing VimScript to the new style VimScript they are thinking of.
How do actor model languages (like ponylang) handle this? It seems like not having back-pressure support would be a fundamental issue with the language.
It seems like the gist is that the responsibility is on the application to be architect-ed (perhaps using one of the various libraries/strategies) to handle flow-control/back-pressure. The language itself doesn't directly help.
