core
hotwire-rails
core | hotwire-rails | |
---|---|---|
40 | 98 | |
960 | 960 | |
0.8% | - | |
8.4 | 3.2 | |
22 days ago | over 2 years ago | |
Kotlin | Ruby | |
GNU Lesser General Public License v3.0 only | 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.
core
- Show HN: Kweb – Kotlin Web Framework Blurs the Line Between Server and Browser
- Kweb 1.4.5 released, a remote interface to the browser's DOM
-
Get funding for your Kotlin project! Apply for a grant from the Kotlin Foundation.
Reasonable people can disagree on licensing issues, and obviously they can give out grants under whatever conditions they like, but telling developers that JetBrains knows what license is best for your project's users seems intrusive to me. My project has almost 900 github stars, it's under the LGPL and in almost 7 years no user has ever asked for a less restrictive license.
-
Kweb 1.4.0 released: Create beautiful and functional website with a unified Kotlin codebase
Anyone interested could create a plugin for tailwind similar to this one for another CSS framework.
-
On the Compose HTML rebranding (TL;DR - everything is fine!)
Kweb - A Kotlin web framework built on SSR (server side rendering)
- Show HN: Kweb: A remote interface to the web browser's DOM
-
Show HN: Kweb: A remote interface to the web browser DOM, in Kotlin
User Manual: https://docs.kweb.io/book
Kweb is a novel web framework that acts as a remote interface to the web browser's DOM (Document Object Model). With Kweb, you can create and manipulate DOM elements and listen for and handle events, all using an intuitive Kotlin DSL that mirrors the structure of the HTML being created.
Kweb manages state through observable mutable values called kvars:
import kweb.*
-
Kweb 1.3.5 released with update to Ktor 2.2.2, and Gradle 7.6
Github | User Manual | Release Notes
- Kweb - A server-side interface to the browser's DOM
- Show HN: Kweb 1.3.3 released, a server-side interface to the browser's DOM
hotwire-rails
- It's not Ruby that's slow, it's your database
- Howire Not Working after deploying to Heroku
-
What's New in Rails 7
Applications generated with Rails 7 will get Turbo and Stimulus (from Hotwire) by default, instead of Turbolinks and UJS. Hotwire is a new approach that delivers fast updates to the DOM by sending HTML over the wire.
-
Ask HN: What tech stack would you use to build a new web app today?
For Ajax-y stuff, I am really excited by the new crop of "HTML-as-a-Service" or "HTML-over-the-wire."
https://htmx.org/
https://hotwired.dev/
- Ask HN: Do we need JavaScript web frameworks?
-
anyone have full tutorial how to upgrade from rails 6.1 to rails 7 ?
For all the turbo/stimulus/hotwire mix, you want to add a new feature just for the sake of adding it? or do you have a use case that fits the feature? if you have then you probably already have an implementation with a different technology (stimulus reflex? some custom websockets or ajax implementation? something with anycable?) and you have to check how to migrate from that technology to hotwire. If you just want to use the feature with no real need for it to practice then just pick any tutorial from the internet (like the intro in the official website https://hotwired.dev).
-
Ask HN: What are you favorite goto frameworks when writing Web Aplications
I was recently interested in similar topic. Here are 3 similar solutions I found:
* https://htmx.org/
* https://unpoly.com/
* https://hotwired.dev/
My personal preference is Unpoly (the idea of "layers" is awesome). But the best explanation of concept as a whole (HATEOAS, keeping app state on server using partial page updates, etc) is at HTMX homepage, and in these essays:
* https://htmx.org/essays/hateoas/
* https://htmx.org/essays/locality-of-behaviour/
-
Hotwire isn't only for Rails
At the end of 2020 the Basecamp team released a collection of Javascript libraries called Hotwire. Modern web stacks have popularized javascript-rendered front ends and JSON transmissions. Hotwire's primary motivation is to reduce the Javascript footprint and allow application front ends to be created in primarily HTML. It pairs very nicely with the Ruby on Rails ideology and is often demonstrated in that context. I aim to write a series on how Hotwire can be used in any application to simplify development and reduce the need for heavy Javascript downloads. Hotwire currently consists of two javascript libraries: Turbo and Stimulus. The first part of this series introduces Turbo.
-
How do you handle views?
I've been doing that a while until I just got sock of the JS spagetti and often duplicated code and went full on Angular CSR and never looked back. That being said, I've been seeing a lot recently about Laravel's Livewire and Symfony and Ruby on Rail's integration with Hotwire (stimulus+turbo).
- Why learn Rails as a frontender?
What are some alternatives?
wasabi - An HTTP Framework
htmx - </> htmx - high power tools for HTML
GraphQL Kotlin - Libraries for running GraphQL in Kotlin
SvelteKit - web development, streamlined
kotlin - Starter project for Kotlin
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
ktor - Framework for quickly creating connected applications in Kotlin with minimal effort
Svelte - Cybernetically enhanced web apps
kraph - GraphQL request string builder written in Kotlin
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML
kotless - Kotlin Serverless Framework
inertia-laravel - The Laravel adapter for Inertia.js.