Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 2019 12:51
    pushqrdx edited #176
  • Jan 31 2019 12:51
    pushqrdx edited #176
  • Jan 31 2019 10:18
    pushqrdx opened #176
  • Jan 31 2019 07:20
    pushqrdx commented #169
  • Jan 31 2019 01:04
    iamtirado commented #169
  • Jan 29 2019 22:04
    shreeve commented #175
  • Jan 29 2019 13:09
    somebee closed #173
  • Jan 29 2019 13:09

    somebee on master

    Reset Stack.tag before each com… Bump version to 1.4.2 (compare)

  • Jan 29 2019 12:24

    somebee on master

    Lookup event handlers up the ow… (compare)

  • Jan 29 2019 12:23

    somebee on master

    Reset rewriter between runs Merge branch 'master' of https:… (compare)

  • Jan 29 2019 07:40
    shreeve opened #175
  • Jan 28 2019 21:26
    shreeve closed #174
  • Jan 28 2019 21:26
    shreeve commented #174
  • Jan 28 2019 21:24
    shreeve edited #174
  • Jan 28 2019 21:24
    shreeve opened #174
  • Jan 27 2019 14:37
    darcyturk opened #173
  • Jan 27 2019 10:04
    darcyturk commented #128
  • Jan 26 2019 11:56
    Alhadis opened #172
  • Jan 22 2019 01:29
    CassianoSF closed #171
  • Jan 22 2019 01:29
    CassianoSF commented #171
Sindre Aarsaether
@somebee
It might be better to start thinking about it when v2 is released and stable. We ought to rewrite the compiler itself to v2 at some point anyways :)
Fedor Leschinsky
@altteo
At the moment i have all time in the universe. And there are a lot of things to be done: compiler, online repl, components library, components playground, documentation, some stunning examples.
but there are things that i would change in the language itself and in the render engine.
the only thing i still have no opinion is state managment. I mean whether we should have some special declarative syntax for describing state.
@somebee i meant that i could do it.
Fedor Leschinsky
@altteo
@somebee if you support me, i will do it all, but you will need to spend time with me (so i don’t cut things that are critical for you)
cstffx
@cstffx
Why don't work in a language specification before any next step?? Like the ISO 16262 but for Imba.
Sindre Aarsaether
@somebee
I'm very time constrained (even more than usual), so I probably won't have too much time to follow up. But before we/you start rewriting it all I think we ought to discuss and look at proposed user facing changes. Even if the compiler is pretty messy I'm extremely satisfied with the tag compilation in v2 :)
Alexander Alemayhu
@scanf
How about starting off by cranking out a few blog posts about Imba internals on your own? This can be useful for you and others :+1:
@altteo ^
Would be amazing if you did it in the same style as Fabien http://fabiensanglard.net/quakeSource/index.php
Eric Vida
@ericvida
@scanf I see a lot of docs pages that had content are now blank? I used those everyday, Are you planning to replace them soon? Why not leave them until you get around to updating them?
Fedor Leschinsky
@altteo
@scanf That is the problem - the internals of imba never been readable and understandable. It is more a proof of a concept than an open source project with community. That was an internal tool made and used by Sindre. And than just opensourced. So it’s time to make it shine. But the first thing to do is to set goals of the language and its major features. So when there will be a dispute we could choose that point of view which is more relevant to the principles.
Fedor Leschinsky
@altteo
My vision is that imba should be the 5-th gen language. The first was machine codes. The second was asm. The third was C. And the fourth is JS. Each next generation was closer to humans than to bare metal. And starting from js we could code without thinking of computers at all. So imba should become more clear and friendly.
And though js is very universal it was designed (pretty good) in 10 days in times that a lot of concepts does not exist. I mean interface and state management. And Sindre’s approach to interface is brilliant (custom syntax for modeling interface and that interface is a function).
Fedor Leschinsky
@altteo
If we could figure out how to make state management clear and easier than with universal language (i mean its a good idea to design specific syntax for state management) it will be i think the first 5 gen lenguage.
Fedor Leschinsky
@altteo
Ideas i came to for the moment is that state could be changed from two different sides - from user through the interface and from other computers (like requests or realtime dbs). And when it is changed functional programming again come into place - all other stuff could be calculated automatically (mobx approach). And with special syntax we could make some garanties (like elm) on compiler level.
So we could do two gateways - one from the interface and other from requests. Set “quarantine” for side infuantion.
Fedor Leschinsky
@altteo
Maybe i went too deep. But i faced an exponential growth of complexity when I tried to handle events from ui and from db in one place (through event bus).
Maybe it is not a matter of special syntax but a proper architecture. But it is a good thing to be opinionated in such things and force them.
Alexander Alemayhu
@scanf
@iamtirado making your old pages blank are not intentional. I have no idea why GitBook keeps doing that. I thought it was due to a save / merge issue. Do you know why it does that?
I was actually telling Sindre about this yesterday too. Hopefully I will get a chance today to read through the GitBook manual.
Eric Vida
@ericvida
Hmm. Is it synced with github?
might be able to chat with support.
Alexander Alemayhu
@scanf
I will try that and also look up how to change color on existing syntax. Thanks.
Alexander Alemayhu
@scanf
*language
Alexander Alemayhu
@scanf
The windows issues should now be resolved in 2.0.0-alpha.31, tested it earlier.
Alexander Alemayhu
@scanf
Sent message to GitBook support, hopefully they can clarify what is happening otherwise we need to consider alternatives...
Alexander Alemayhu
@scanf
Two new Imba Changelog episodes straight from the oven, https://users.imba.io/t/new-imba-changelog/59
Enjoy!
@altteo would be cool if you and @somebee did some new episodes on the Dialogs about Imba.
Since you have written so much Imba code it would be interesting to hear a discussion of some of the ideas Sindre has for the future.
Fedor Leschinsky
@altteo
My view on implicit self and tag <self> and !,? I have written in github issues. Pretty good idea to put model handlers in tag event handlers. But with @ it looks very magical. I’d rather would call it more explicitly :click=model.resolve
Eric Vida
@ericvida

Imba has made a lot more sense to me without inplicit self.

i like the <self> tag.

Alexander Alemayhu
@scanf
New Imba Changelog episode on the experimental syntax for event modifiers https://users.imba.io/t/imba-changelog-improving-event-handlers/60
Fedor Leschinsky
@altteo
:click.stop.{@store.addTicket()} is pretty good. also I was thinking about :click->stop->@store.addTicket() syntax
Sindre Aarsaether
@somebee
alpha 34 just released with this event handler syntax (:click.stop.{@store.addTicket()}) :) Should be running on scrimba as well
Alexander Alemayhu
@scanf
I have not read the whole article but cloc supports Imba v1 since July AlDanial/cloc@907674e
So no execuse for them to include in the 2020 hindsight
:wink:
Eric Vida
@ericvida
i made a discord group: https://discord.gg/U2gY9RP
Sindre Aarsaether
@somebee
I made one today as well :P
Eric Vida
@ericvida
haha. let's go there
whats the link
Fedor Leschinsky
@altteo
Eric Vida
@ericvida

@all
Join our less buggy Discord Chat.
https://discord.gg/fT4tY8z

@scanf can you link to that from imba.io?
discord's native apps are much less buggy.

Alexander Alemayhu
@scanf
Courtesy reminder, the next Imba bi-weekly community meeting is on Monday at 07AM https://www.meetup.com/en-AU/Imba-Oslo-Meetup/events/qplnhrybcfbdb/
We can discuss discord then.