New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.0.0-RC2 #259

Closed
piranna opened this Issue Jun 25, 2016 · 10 comments

Comments

Projects
None yet
2 participants
@piranna
Member

piranna commented Jun 25, 2016

Just exactly one month after my degree thesis (with distinction, f*ck yeah ;-) ) and with a lot of nights without sleep, we have available NodeOS 1.0.0-RC2.

There has been some problems lately with the packages and the build process, but they are due to the heavy changes on the architecture that I hope they are going to be better for the future. The main one, is the split of the different layers on independent, isolated and autonomous projects that are themselves published on NPM, but also (and that's the important part) they have their own tests passing on SemaphoreCI and configured to work with GreenKeeper, so when we'll move to 1.0.0 final we'll be able to work on a real Rolling Release distro, and also there have been suggestion to include an autoupdater on NodeOS itself. As an implementation detail, these layers and submodules (like qemu, that it's now published on npm) use extensively the prebuild-install module to distribute prebuild images of their components, so no more pop-corn & movies to build NodeOS but just only a coffee. Yes, build process it's blasingly fast, and there's also a lot of room for improvement so we could end up blurrying the line between install and compile times by merging both processes ;-)

Other important change due to the increasing number of installing problems is the movement to npm3 and deprecation of npm2, so now build process is deterministic, faster and use less memory (also in NodeOS disk images, that have decreased ;-) ). Only drawback is that since npm3 considers the install process a one-time execution it's needed to split the install of the dependencies (npm install) and the generation of the NodeOS image (npm run build), but this also allow better flexibility and also remove the need of network connection when building the system since all the modules included on the NodeOS images has been set as dependencies of the NodeOS module itself, so they are getting cached for later.

But probably the most important change is Node.js, because not only it has got it's own npm package downloading prebuild binaries based on musl (maybe we should propose to Node.js org to host and distribute them side-by-side with their glibc ones?), but also it has been upgraded to bleeding edge 6.2.2! :-D There has been some problems because /proc was not being mounted and it's needed by musl, but thanks to it I give the chance to do some improvements to nodeos-init and now it's easier to use and robust, cleanly clossing the system itself on shut-down :-)

Let's more to 1.0.0! :-D

@piranna piranna added the blog label Jun 25, 2016

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jun 25, 2016

Member

Yes, build process it's blasingly fast

About time! Yaay!

there have been suggestion to include an autoupdater on NodeOS itself

Haha hey look mom, it's me!

they have their own tests passing on SemaphoreCI and configured to work with GreenKeeper, so when we'll move to 1.0.0 final we'll be able to work on a real Rolling Release distro

This is fantastic! A completely automated self-maintained system on it's way! The auto-updater will seal the deal ;)

but also it has been upgraded to bleeding edge 6.2.2! :-D

There we go! Now we're a bleeding edge distro! The leading edge of technology, like we were always supposed to be!

Let's more to 1.0.0! :-D

Let's go! :D

Member

lite20 commented Jun 25, 2016

Yes, build process it's blasingly fast

About time! Yaay!

there have been suggestion to include an autoupdater on NodeOS itself

Haha hey look mom, it's me!

they have their own tests passing on SemaphoreCI and configured to work with GreenKeeper, so when we'll move to 1.0.0 final we'll be able to work on a real Rolling Release distro

This is fantastic! A completely automated self-maintained system on it's way! The auto-updater will seal the deal ;)

but also it has been upgraded to bleeding edge 6.2.2! :-D

There we go! Now we're a bleeding edge distro! The leading edge of technology, like we were always supposed to be!

Let's more to 1.0.0! :-D

Let's go! :D

@lite20 lite20 modified the milestone: 1.0.0 Jun 25, 2016

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Jun 26, 2016

Member

Haha hey look mom, it's me!

Lol! X-D

This is fantastic! A completely automated self-maintained system on it's way! The auto-updater will seal the deal ;)

Totally, in fact the cherry on the top of the cake would be to end up having semantic release :-D But it will be tough the get up to it in a sane and stable way... By splitting the layers in several projects tests have improved a lot, but they are a pain in the *ss and since now I will not have so much time as before due to work and personal life and maybe invest some time in other smaller side projects... :-/ That's one of the reasons I wantes to release the RC2 as soon as possible, to left NodeOS in a good state during some time, manage NodeOS is exhausting :-P Maybe it would be time to find some spondsors or fundraising...

like we were always supposed to be!

Totally... at least we are a showcase of the state-of-the-art on several topics, that's not bad too :-D

Member

piranna commented Jun 26, 2016

Haha hey look mom, it's me!

Lol! X-D

This is fantastic! A completely automated self-maintained system on it's way! The auto-updater will seal the deal ;)

Totally, in fact the cherry on the top of the cake would be to end up having semantic release :-D But it will be tough the get up to it in a sane and stable way... By splitting the layers in several projects tests have improved a lot, but they are a pain in the *ss and since now I will not have so much time as before due to work and personal life and maybe invest some time in other smaller side projects... :-/ That's one of the reasons I wantes to release the RC2 as soon as possible, to left NodeOS in a good state during some time, manage NodeOS is exhausting :-P Maybe it would be time to find some spondsors or fundraising...

like we were always supposed to be!

Totally... at least we are a showcase of the state-of-the-art on several topics, that's not bad too :-D

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jun 26, 2016

Member

Maybe it would be time to find some spondsors or fundraising...

haha yeah that's not a bad idea!

manage NodeOS is exhausting

Yeah! Even more a reason to get it to manage itself haha!

maybe invest some time in other smaller side projects

Ah you should check out some of my side projects if you have time; I feel you'd like them! HexCade for example, is an attempt to make a VM language but it implements a few awesome features most languages don't have and handles threads beautifully ^_^

Member

lite20 commented Jun 26, 2016

Maybe it would be time to find some spondsors or fundraising...

haha yeah that's not a bad idea!

manage NodeOS is exhausting

Yeah! Even more a reason to get it to manage itself haha!

maybe invest some time in other smaller side projects

Ah you should check out some of my side projects if you have time; I feel you'd like them! HexCade for example, is an attempt to make a VM language but it implements a few awesome features most languages don't have and handles threads beautifully ^_^

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Jun 26, 2016

Member

haha yeah that's not a bad idea!

There are several problems, like who is payed and how. Up this moment, beside the site domain that got payed by @groundwater (and anyway it's cheap) it's everything working on free services so there's no costs here, so it would make more sense to get sponsors to pay work hours or to fix some issues, but that's difficult to find and to do in a fair and ethical way... :-/ This would need a discussion on it's own, the debate would be really long...

Yeah! Even more a reason to get it to manage itself haha!

That's why I have been trying to automate it as much as possible ;-)

Ah you should check out some of my side projects if you have time; I feel you'd like them! HexCade for example, is an attempt to make a VM language but it implements a few awesome features most languages don't have and handles threads beautifully ^_^

Link or didn't happen ;-)

Member

piranna commented Jun 26, 2016

haha yeah that's not a bad idea!

There are several problems, like who is payed and how. Up this moment, beside the site domain that got payed by @groundwater (and anyway it's cheap) it's everything working on free services so there's no costs here, so it would make more sense to get sponsors to pay work hours or to fix some issues, but that's difficult to find and to do in a fair and ethical way... :-/ This would need a discussion on it's own, the debate would be really long...

Yeah! Even more a reason to get it to manage itself haha!

That's why I have been trying to automate it as much as possible ;-)

Ah you should check out some of my side projects if you have time; I feel you'd like them! HexCade for example, is an attempt to make a VM language but it implements a few awesome features most languages don't have and handles threads beautifully ^_^

Link or didn't happen ;-)

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jun 26, 2016

Member

Here you go!

P.S. I'm still organizing things and I'll probably split HexCadi and Unipop into two separate projects but if you have any questions about how underlying technologies work (especially the one's I haven't written yet) just create a thread! Create many threads if you so please!

Member

lite20 commented Jun 26, 2016

Here you go!

P.S. I'm still organizing things and I'll probably split HexCadi and Unipop into two separate projects but if you have any questions about how underlying technologies work (especially the one's I haven't written yet) just create a thread! Create many threads if you so please!

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Jun 26, 2016

Member

Why it's needed the preprocessor? Almost no languaje use them today or have
them integrated in the languaje itself...
El 26/6/2016 2:47, "Lite McFish" notifications@github.com escribió:

Here you go! https://bitbucket.org/Lite20/hexcade

P.S. I'm still organizing things and I'll probably split HexCadi and
Unipop into two separate projects but if you have any questions about how
underlying technologies work (especially the one's I haven't written yet)
just create a thread! Create many threads if you so please!


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#259 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAgfvgNJuPs9Wsp-kfakQcM5g9eLrrpKks5qPcwVgaJpZM4I-c-T
.

Member

piranna commented Jun 26, 2016

Why it's needed the preprocessor? Almost no languaje use them today or have
them integrated in the languaje itself...
El 26/6/2016 2:47, "Lite McFish" notifications@github.com escribió:

Here you go! https://bitbucket.org/Lite20/hexcade

P.S. I'm still organizing things and I'll probably split HexCadi and
Unipop into two separate projects but if you have any questions about how
underlying technologies work (especially the one's I haven't written yet)
just create a thread! Create many threads if you so please!


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#259 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAgfvgNJuPs9Wsp-kfakQcM5g9eLrrpKks5qPcwVgaJpZM4I-c-T
.

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jun 26, 2016

Member

Preprocessor allows developers to custom tween and optimize code before it's even shipped. Sort-of like javac for Java. @piranna

The client has it too though so it can be performed at runtime. Do you think this should be changed? (If so just create a new issue thread :D)

Member

lite20 commented Jun 26, 2016

Preprocessor allows developers to custom tween and optimize code before it's even shipped. Sort-of like javac for Java. @piranna

The client has it too though so it can be performed at runtime. Do you think this should be changed? (If so just create a new issue thread :D)

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Jun 27, 2016

Member

Preprocessor allows developers to custom tween and optimize code before
it's even shipped. Sort-of like javac for Java. @piranna

JavaC is the compiler... By far I only know of two languages that use a
preprocesor, C and Python, and this later one is only to clean-up the sugar
sintaxys and in fact is integrated on the bytecode compiler as a
transparent step. I think you should do the same... KISS, you know ;-)

Member

piranna commented Jun 27, 2016

Preprocessor allows developers to custom tween and optimize code before
it's even shipped. Sort-of like javac for Java. @piranna

JavaC is the compiler... By far I only know of two languages that use a
preprocesor, C and Python, and this later one is only to clean-up the sugar
sintaxys and in fact is integrated on the bytecode compiler as a
transparent step. I think you should do the same... KISS, you know ;-)

@lite20

This comment has been minimized.

Show comment
Hide comment
@lite20

lite20 Jun 28, 2016

Member

@piranna yeah I merged the preprocessor and the interpreter. It should be clean to take for a walk soon.

Member

lite20 commented Jun 28, 2016

@piranna yeah I merged the preprocessor and the interpreter. It should be clean to take for a walk soon.

@piranna

This comment has been minimized.

Show comment
Hide comment
@piranna

piranna Jun 28, 2016

Member

@piranna yeah I merged the preprocessor and the interpreter. It should be clean to take for a walk soon.

Cool :-)

Member

piranna commented Jun 28, 2016

@piranna yeah I merged the preprocessor and the interpreter. It should be clean to take for a walk soon.

Cool :-)

@piranna piranna closed this Apr 2, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment