Opal | vite | |
---|---|---|
37 | 801 | |
4,815 | 65,232 | |
0.3% | 1.6% | |
9.0 | 9.8 | |
21 days ago | 5 days ago | |
Ruby | TypeScript | |
MIT License | MIT License |
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.
Opal
-
RubyJS-Vite
It's been a long time dream for me since about 2013 when I started getting deep into Ruby and Rails, to be able to write Ruby code for the frontend instead of JavaScript. I was a lover and adopter of CoffeeScript (which had it's flaws and imperfections), but that mostly got killed by ES6. I wrote some PoCs with Opal[1] that felt pretty good to write, but the overhead was rough (this was many years ago so things might be different now) and I never really felt like I didn't have to know about or care about the underlying javascript. I tend to discard leaky abstractions as I feel they often add more complexity than they were meant to cover in the first place.
Has anybody used this or Opal or anything else? What is the state of "write your frontend in Ruby" nowadays?
[1]: https://github.com/opal/opal
-
Non-code contributions are the secret to open source success
Every time I see a respectable project use a Code of Conduct I remind myself that, unfortunately, Caroline Ada won[1]
[1] https://github.com/opal/opal/issues/941
-
Coming to grips with JS: a Rubyist's deep dive
But we shouldn't overstate the difference: the JS and Ruby object models are actually similar in how dynamic both of them are. This makes Ruby-to-JS compilers like Opal easier to implement, according to an Opal maintainer.
-
Opal – a Ruby to JavaScript source-to-source compiler
This is an interview with the author of Opal, here's the project:
https://github.com/opal/opal
-
GCC Adopts a Code of Conduct
Not the OP, but from what I remember they would seek out every possible opportunity in every single possible open source community they could find and propose the CoC that they wrote. 0 contributions to the projects, with the exception of demanding that people implement incredibly verbose CoC's in their projects under the guise of "protecting the minorities contributing to the projects".
Most infamous instance is probably this one, in the Opal repo: https://github.com/opal/opal/issues/941
As well as this thread in the Ruby issue tracker that devolves into pure chaos with Ada refusing to actually participate in any of the valid points others bring up: https://bugs.ruby-lang.org/issues/12004
And I'm sure there's many other instances if you look around a bit.
-
Hackers Flood NPM with Bogus Packages Causing a DoS Attack
My experience with ruby for front end web dev is via https://opalrb.com/
-
The Rust Trademark Borrow Checker : Rust Foundation Solicits Feedback on Updated Policy for Trademarks
Here's an example of the creator of the most adopted CoC (the Contributor Covenant) trying to get an open source contributor removed from a project due to his political opinions expressed on Twitter which she didn't like and found offensive.
-
Launch HN: Pynecone (YC W23) – Web Apps in Pure Python
So ruby has a JS transpiler - opal - https://opalrb.com/
I tried using it a little bit but the reality is if you need JS to make your app more interactable it's really worth it to just learn some JS. As soon as you need something complex the extra layer of abstraction just gets in the way and becomes more of a headache, and if you don't need anything complex then you don't need JS in the first place.
-
DebunkThis: Coraline Ada Ehmke hasn't really contributed that much as far as code goes
I stumbled upon this thing from years ago. I did some more digging to see what other communities thought about it. Turns out that a lot of people are really against Coraline's side.
- All web applications may be created in the optimal environment created by Ruby, JS, and Vite.
vite
-
Comparing Hattip vs. Express.js for modern app development
As of this writing, initializing a Hattip project requires some manual commands. However, keep in mind that a zero-config development environment based on Vite is in the works.
-
React TypeScript - Vite + React
import { defineConfig } from 'vite' import react from '@vitejs/plugin-react' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 4200, } })
-
I Disappear
For the frontend of "I Disappear," I leverage the automated build & deploy system provided by Netlify, which seamlessly integrates with Vite. This setup ensures that every deployment is optimized for performance, utilizing Vite’s modern build tools to enhance speed and efficiency.
-
FlowDiver: The Road to SSR - Part 1
Given our team's collective proficiency within the React ecosystem, we decided to leverage this expertise for our project. Initially, we contemplated utilizing Next.js; however, due to the limited practical experience with this technology among key engineers and the pressing timeline to develop the first prototype, we opted for a Single Page Application(SPA) approach. For bundling, we selected Vite, primarily due to its super fast build times, simplicity of configuration, and potential for a nearly seamless transition to server-side rendering.
-
Inflight Magazine no. 9
We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.
-
Top 12+ Battle-Tested React Boilerplates for 2024
Vite focuses on providing an extremely fast development server and workflow speed in web development. It uses its own ES module imports during development, speeding up the startup time.
-
Vite vs Nextjs: Which one is right for you?
Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.
-
Setup React Typescript with Vite & ESLint
import { defineConfig } from 'vite' import react from '@vitejs/plugin-react-swc' import path from 'path' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 3000 }, css: { devSourcemap: true }, resolve: { alias: { '~': path.resolve(__dirname, './src') } } })
-
Approaches to Styling React Components, Best Use Cases
I am currently utilizing Vite:
-
Getting started with TiniJS framework
Homepage: https://vitejs.dev/
What are some alternatives?
MRuby - Lightweight Ruby
Next.js - The React Framework
JRuby - JRuby, an implementation of Ruby on the JVM
parcel - The zero configuration build tool for the web. 📦🚀
Rubinius - The Rubinius Language Platform
esbuild - An extremely fast bundler for the web
Reactrb
swc - Rust-based platform for the Web
yjit - Optimizing JIT compiler built inside CRuby
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
natalie - a work-in-progress Ruby compiler, written in Ruby and C++
Rollup - Next-generation ES module bundler