inai
30-seconds-of-code
inai | 30-seconds-of-code | |
---|---|---|
4 | 37 | |
8 | 119,340 | |
- | 0.5% | |
5.7 | 9.8 | |
almost 3 years ago | 3 days ago | |
JavaScript | JavaScript | |
Apache License 2.0 | Creative Commons Attribution 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
inai
- An experiment structuring a Node.js application internally using REST principles
-
Objective-S: architecture-oriented language based on Smalltalk and Objective-C
This is useful! Thanks for writing this out. I find in-process REST intriguing as it stands a little in contrast with OOP techniques. One possibility I’ve with in-process REST is that it seems to make live patches feasible - more feasible than in erlang. I use the idea as the core of Inai - https://github.com/imaginea/inai ... so am curious to play with that aspect of ObjS.
-
Monolith First
A bit of a shameless plug, but really looking for feedback .. I've been experimenting with Inai [1][2], a framework that can help build modular microservice-like software with similar Dev team independence properties but can independently be built and deployed as a monolith or as separate services operationally. So far, I've had fun building an internal project at much higher speed than I've managed any similar project and had more fun doing it. I feel the idea (which is still nascent) has some merit, but would like to know what folks think.
[1] source - https://github.com/Imaginea/Inai
[2] blog post describing Inai - https://labs.imaginea.com/inai-rest-in-the-small/
-
Oberon OS Walkthrough
At some point, this would be come close to the AppleScript protocol or Symbian OS.
> So the drawing part of an application would just be a process that sends the screen/compositor process a message describing the state of its window as a tree, and receives messages for events in response.
I've been toying with an interpretation of this here - https://github.com/Imaginea/inai - and kind of having fun with it .. and even built a prototype internal app using it. Super early stage and so stuff won't necessarily make sense at the outset .. or possibly ever. Thoughts welcome though.
> A big advantage is it makes the semantics of composing GUIs a lot more reasonable "replace this leaf of my tree with this other process' tree" ...
The "dom" service in Inai pretty much feels like that. I felt like an idiot to try and (for lack of a better expression) REST-ify the DOM, but it seemed to work to my surprise.
> An application could also "proxy" for a widget, including over a network link, so you get fairly simple network transparency this way too.
.. yeah due to the "REST" nature, this becomes pretty straightforward.
30-seconds-of-code
- 30-seconds-of-code: Short code snippets for all your development needs
-
What are the best open source repos in github that a beginner should READ?
You could also check out: 1. 30 seconds of code 2. JavaScript30 3. JavaScript Algorithms
-
Awesome Github Repos to Master JAVASCRIPT
😎 a quick reference with short solutions for your development needs in javascript -> 30-seconds-of-code
- 18 useful GitHub repositories every developer should bookmark
- 🧑💻 Short JavaScript code snippets for all your development needs
- GitHub Repositories : Part 1
- Seconds of code – short JavaScript snippets for all your development needs
-
19 Practical ES6 Snippets to Solve Common JS Problems 🚀💯
All of the snippets were handpicked from 30 seconds of code. It's an awesome resource, I would highly recommend going to check it out for more stuff.
- 30 seconds of code: Short JavaScript code snippets for all your development needs