Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Rfcs Alternatives
Similar projects and alternatives to rfcs
-
-
language-tools
The Svelte Language Server, and official extensions which use it (by sveltejs)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
TypeScript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
joystick
A full-stack JavaScript framework for building stable, easy-to-maintain apps and websites.
-
-
-
ember-render-modifiers
Implements did-insert / did-update / will-destroy modifiers for emberjs/rfcs#415
-
svelte-tippy
A svelte action for creating tippy.js tooltips with full typescript support
-
tauri
Build smaller, faster, and more secure desktop applications with a web frontend.
-
DefinitelyTyped
The repository for high quality TypeScript type definitions.
-
-
-
-
next-runtime
The Next.js Runtime allows Next.js to run on Netlify with zero configuration (by netlify)
-
-
ember-functions-as-helper-polyfill
Implementation of RFC 756, Default Helper Manager
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
rfcs reviews and mentions
-
Support for in/inter page linking / scrolling in EmberJS
Navigating to URLs with #hash-targets in them is not supported by most single-page-app frameworks due to the async rendering nature of modern web apps -- the browser can't scroll to a #hash-target on page load / transition because the element hasn't rendered yet. There is an issue about this for Ember here on the RFCs repo.
-
The road from Ember classic to Glimmer components
Ember.js development doesn’t stagnate. Progress is already being made for new improvements to the current component model. The RFC for first-class component templates has been accepted and merged in 2022 and will provide new benefits to Ember users. By first adopting Glimmer components, we’re prepared for what’s coming next.
-
"Why would I use Ember over Vue?" or "Are my impressions of the framework landscape based at all in current fact?"
yeah, I think that's being designed (for runtime).We have build-time efforts / validation already via official typescript support https://github.com/emberjs/rfcs/pull/748 with Glint: https://typed-ember.gitbook.io/glint/
-
[AskJS] What's your opinion about React 18 and do you feel the framework is at the forefront of innovation compared to Vue, Angular, Ember, Meteor, Mithril, Polymer and the others... is it going the right way for you or you would have changed a few things ?
During the 4.x series, we aim to finish the work to officially support TypeScript.
I do write app in Ember at work. Ts adoption plan is still in discussion https://github.com/emberjs/rfcs/pull/800
-
TypeScript Features to Avoid
The latest versions of Ember.js (Octane) have built-in decorator support and they're discussed in the RFC:
https://github.com/emberjs/rfcs/blob/master/text/0408-decora...
https://guides.emberjs.com/release/in-depth-topics/native-cl...
-
[oc] svelte-tippy a tippy.js action for svelte with full typescript support!
At ok, legit. that's like a modifier from ember.
-
Real talk: Did I make a mistake choosing Ember for my app?
have you seen: https://github.com/emberjs/rfcs/pull/779? I think that addresses the "where does this come from?" in completion.
-
Vercel Welcomes Rich Harris, Creator of Svelte
What I like about Ember is that it gives a lot of rigid structure that, at least at one point, made it comparatively easy to work on multiple Ember based projects and be productive sooner.
As you've pointed out, a problem with that project is that there's a ton of intimate knowledge for how things work under the hood or why things are the way they are. They also seem to oscillate between opting for simplicity and opting for complexity and magic.
One example would be the latest version of Ember which doesn't even ship with `@ember/render-modifiers` by default despite how everyone will end up installing it anyway because it's necessary; they were talking about providing an alternative based on the actor model, despite modifiers being far easier to understand, somehow they are still wrong:
> Either way, we recommend using these modifiers with caution. They are very useful for quickly bridging the gap between classic components and Glimmer components, but they are still generally an anti-pattern.
https://github.com/emberjs/ember-render-modifiers
Why on earth did they reinvent components and ship them without providing the supposedly correct way of interacting with their lifecycle? You actually have to install a separate add-on to develop a production-ready app with Ember, which completely flies in the face of the idea that you can run `ember new` and have pretty much everything you need.
Strangely (an thankfully), the RFC for the needlessly complicated alternative for lifecycle interaction is effectively stalled:
https://github.com/emberjs/rfcs/pull/567
By their own language, the only official way to interact with component/element lifecycle is an antipattern.
/rant
-
Why Blueprints in Ember Are Cool and How They Save You Time Writing Tests
For a recent app, which uses QUnit and the latest Ember QUnit API, your index.js could look like this:
-
A note from our sponsor - InfluxDB
www.influxdata.com | 28 Mar 2024
Stats
The primary programming language of rfcs is Shell.