nimble
RxJS
nimble | RxJS | |
---|---|---|
9 | 98 | |
1,229 | 30,218 | |
0.5% | 0.5% | |
8.2 | 8.8 | |
1 day ago | 12 days ago | |
Nim | TypeScript | |
GNU General Public License v3.0 or later | Apache License 2.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.
nimble
-
Ask HN: What are some unpopular technologies you wish people knew more about?
I was using Nim for some of last years Advent of Code problems. I was mostly liking the syntax. Was a bit bother by the standard library have a snake case and camel case reference for each function (if I'm remember that correctly).
At the time nimble also required me to have NPM to install the the Nim package manager, Nimble. This was not ideal, but looking at [the nimble project install docs](https://github.com/nim-lang/nimble#installation) it seems like it is now package with the language.
Might try dusting it off for some AoC puzzles this year :)
-
My Nim Development Weekly Report (2/19)
nimble develop -g doesn't work A possible solution is to add "g" to where "global" is placed.
- nimble run --example (PR)
-
Question about nimble
I meant it's unfortunate that Nimble has no standard system-wide library management. It's one of the mains thing holding Nim back from being more prevalent in the Linux sphere in my opinion.
-
Alternative privacy-respecting front ends for popular services
`nimble` is the package manager for the programming language `nim` [1].
From [2], we can see that `nimble scss` simply generates the CSS files for the frontend.
The benefit of OSS is you can answer these questions yourself with a bit of poking around! IMO this is a fairly standard installation process, maybe the fact that it's using Nim instead of a more mainstream language makes it look more daunting than it is. The only out-of-the-ordinary thing here, IMO, is `nimble build` instead of `make build`.
[1]: https://github.com/nim-lang/nimble
[2]: https://github.com/zedeus/nitter/blob/master/nitter.nimble
-
Nim 1.6.2
Something I'm excited about: v1.6.2 integrates support for (not yet released) Nimble[1] v0.14, which introduces lockfiles. I've had terrible experiences with lockfiles in JS land, but they are sorely needed for Nim projects as (fingers crossed) they'll allow for reproducible builds without having to resort to the nimbus-build-system[2]. The latter isn't completely horrible β a lot of much appreciated hard work has gone into it, and it's been a real workhorse β but some days it feels like a big ball and chain.
[1] https://github.com/nim-lang/nimble#nimble
[2] https://github.com/status-im/nimbus-build-system
-
What are some anti features in a language?
So you wouldn't have a problem with a package manager where the configuration is in the same language, such as Nimble?
-
What best IDE/editor for NIM now.
if you structure your project with nimble (which can be be used for both libraries and applications) you can use nimble build and nimble run. While I do use nimble for managing dependencies for projects I don't use these commands that often while developing, e.g. because I'm working on a single test or something like that.
-
Using Ruby
Having similar syntax to Ruby makes it easier to port Ruby code to Crystal (ex: digest-crc -> digest-crc.cr). The Crystal stdlib is very complete and they have a growing "shards" ecosystem, roughly the same age as Rust's https://crates.io or Nim's nimble. You should look into Crystal again.
RxJS
-
Episode 24/13: Native Signals, Details on Angular/Wiz, Alan Agius on the Angular CLI
Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and moreβ¦
- Episode 24/09: Testing without TestBed, SSR & Hydration
-
10 Reasons for MiniRx Signal Store
RxJS is used for events and asynchronous tasks
-
Top 10 Things to Add to Your Angular App Coding: A Recipe for Programmer Success
Data flowing like a melody? Master RxJS, the reactive JavaScript library, to handle asynchronous data flows with grace and ease. Streamlined data, happy code.
-
What We Need Instead of "Web Components"
> This proposal makes the same mistake as various stream implementations (including RxJS in the past) of making operators methods on the observable.
I don't think they are making a mistake. I am sure Ben knows what he is doing, given how it was he who refactored rxjs 5 with all operators being methods on the Observable, to rxjs 6 with pipeable operators.
But, their objective is not to bring rxjs into the browser, but rather to bring the Observable primitive into the browser. And, like Array prototype, which has methods, Observable, in order to be even minimally useful, needs some methods, which they modelled from TC39 iterators, for the sake of consistency.
They say:
> We expect userland libraries to provide more niche operators that integrate with the Observable API central to this proposal, potentially shipping natively if they get enough momentum to graduate to the platform. But for this initial proposal, we'd like to restrict the set of operators to those that follow the precedent stated above, similar to how web platform APIs that are declared Setlike and Maplike have native properties inspired by TC39's Map and Set objects. Therefore we'd consider most discussion of expanding this set as out-of-scope for the initial proposal, suitable for discussion in an appendix. Any long tail of operators could conceivably follow along if there is support for the native Observable API presented in this explainer.
As to
> We really need a `pipe` operator, at minimum
Maybe we don't. Note that in RxJS version 8, they have introduced a new way of piping observables, which is the rx function [0]. Maybe they are thinking of something similar for the browser. Or maybe they are thinking of using the native pipeline operator if it ever gets approved.
In the meantime, for any complex manipulations on observables, users will probably still import relevant functions from libraries.
0 - https://github.com/ReactiveX/rxjs/issues/7203
-
Want to raise the bar π―
Hello and welcome! It's fantastic that you're looking to broaden your expertise in front-end development. Transitioning from Flutter to React and Angular is a great move, as it will provide you with a well-rounded skill set. ### Resources for Learning React: 1. **Official Documentation:** Start with the [official React documentation](https://reactjs.org/). It's well-written and comprehensive. 2. **React Fundamentals Courses:** Platforms like [freeCodeCamp](https://www.freecodecamp.org/) and [Codecademy](https://www.codecademy.com/) offer free React courses. 3. **React Hooks:** Understand the concept of hooks, a powerful feature in React. The [React Hooks documentation](https://reactjs.org/docs/hooks-intro.html) is a great resource. 4. **Project-Based Learning:** Build small projects to apply your knowledge. You can find ideas on platforms like [GitHub](https://github.com/) or [CodePen](https://codepen.io/). 5. **React Router:** Learn how to handle navigation in React using [React Router](https://reactrouter.com/). ### Resources for Learning Angular: 1. **Official Documentation:** Similar to React, start with the [official Angular documentation](https://angular.io/). 2. **Angular Tour of Heroes:** This is a hands-on tutorial provided in the Angular documentation. It's an excellent resource for getting started. 3. **Angular University:** [Angular University](https://angular-university.io/) offers comprehensive courses on Angular. 4. **RxJS:** Learn about reactive programming using RxJS, which is heavily used in Angular. You can find resources on the [official RxJS documentation](https://rxjs.dev/). 5. **Build Real-World Apps:** Build practical applications to solidify your understanding. The more you code, the better you'll become. ### Making a Mark in the Open-Source Front-End Space: 1. **GitHub Contributions:** Contribute to existing open-source projects. This not only helps you learn but also establishes your presence in the community. 2. **Create Your Projects:** Start small with your open-source projects. Share them on GitHub, and seek feedback from the community. 3. **Participate in Hackathons:** Join online hackathons or coding challenges. They're great for learning and networking. 4. **Follow Blogs and Newsletters:** Stay updated with the latest trends and best practices in the front-end world. Subscribe to newsletters like [JavaScript Weekly](https://javascriptweekly.com/) or [React Status](https://react.statuscode.com/). 5. **Join Forums and Communities:** Engage with developers on platforms like [Stack Overflow](https://stackoverflow.com/) or specialized forums for React and Angular. Remember, the key is consistent practice and learning by doing. Good luck on your journey, and feel free to reach out if you have more questions! π
- Ask HN: What are some unpopular technologies you wish people knew more about?
-
MiniRx Signal Store for Angular - API Preview
Signal Store helps to streamline your usage of RxJS and Signals: e.g. connect and rxEffect understand both Signals and Observables
-
Implement a simple bus event in Angular
Our bus event is really simple in fact. We have declared into the core module (provided in all the application) an rxjs Subject.
-
Web scraping LinkedIn jobs using Puppeteer and RxJS
Web scraping may seem like a simple task, but there are many challenges to overcome. In this blog, we will dive into how to scrape LinkedIn to extract job listings. To do this, we will use Puppeteer and RxJS. The goal is to achieve web scraping in a declarative, modular, and scalable manner.
What are some alternatives?
Arraymancer - A fast, ergonomic and portable tensor library in Nim with a deep learning focus for CPU, GPU and embedded devices via OpenMP, Cuda and OpenCL backends
Most.js - Ultra-high performance reactive programming
prologue - Powerful and flexible web framework written in Nim
MobX - Simple, scalable state management.
nimlsp - Language Server Protocol implementation for Nim
Bacon - Functional reactive programming library for TypeScript and JavaScript
nitter - Alternative Twitter front-end
kefir - A Reactive Programming library for JavaScript
nim-zmq - Nim ZMQ wrapper
Cycle.js - A functional and reactive JavaScript framework for predictable code
omni - DSL for low-level audio programming.
Highland - High-level streams library for Node.js and the browser