backend-GPT
turbo
Our great sponsors
backend-GPT | turbo | |
---|---|---|
13 | 145 | |
2,952 | 6,415 | |
0.4% | 1.6% | |
2.4 | 8.7 | |
10 months ago | 6 days ago | |
JavaScript | JavaScript | |
- | 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.
backend-GPT
-
Sometimes I wonder if some of you have ever do a code refacto
Mmm, there is a real concern that even the average programmer will be replaceable quite a bit sooner than they expect. Even GPT-3 can operate as a simple application merely by being told in English how to behave. Currently this is kind of a joke, but the main constraint is memory size.
- Do any of you actually use ChatGPT for work?
-
Wtfdoesthiscompanydo.vercel.app
Why bother writing each backend separately? https://github.com/TheAppleTucker/backend-GPT
-
AITodo: Todo app powered by a GPT backend
I saw https://github.com/TheAppleTucker/backend-GPT and decided to give this a go myself. Pretty fun stuff.
- I felt compelled to see what would happen
- TheAppleTucker/backend-GPT
- OpenAI might be training its AI technology to replace some software engineers, report says
- Ask HN: What would be your stack if you are building an MVP today?
- GPT is all you need for the back end
turbo
-
Turbo Streaming Modals in Ruby on Rails
I also recommend checking out the docs for Stimulus and Turbo to familiarise yourself with all their features and the APIs used in this series.
-
Htmx vs. React: A Complete Comparison – Semaphore
https://github.com/hotwired/turbo
- Turbo 8 has been released
-
What is JSDoc and why you may not need typescript for your next project?
Turbo 8 remove typescript without using JSDOC
-
Coming to grips with JS: a Rubyist's deep dive
Experiment using Turbo to drive front-end behavior: "Turbo 7.2.0 (currently in beta) allows you to define your own Stream actions which can be any JS code you want. By combining a custom Stream action or two with web components, you can essentially drive reactive frontend behavior from the backend stupidly easily. Loooove it! 😍 […] For a turnkey example, you could check out https://github.com/hopsoft/turbo_ready " —Jared White on The Spicy Web Discord
-
Improving a web component, one step at a time
This handles disconnection (as could be done by any destructive change to the DOM, like navigating with Turbo or htmx, I'm not even talking about using the element in a JavaScript-heavy web app) but not reconnection though, and we've exited early from the connectedCallback to avoid initializing the element twice, so this change actually broke our component in these situations where it's moved around, or stashed and then reinserted. To fix that, we need to always call addSparkles in connectedCallback, so move all the rest into an if, that's actually as simple as that… except that when the user prefers reduced motion, sparkles are never removed, so they keep piling in each time the element is connected again. One way to handle that, without introducing our housekeeping of individual timers, is to just remove all sparkles on disconnection. Either that or conditionally add them in connectedCallback if either we're initializing the element (including attaching the shadow DOM) or the user doesn't prefer reduced motion. The difference between both approaches is in whether we want the small animation when the sparkles appear (and appearing at new random locations). I went with the latter.
-
Mastering Rails Web Navigation with link_to and button_to Helpers - Part 2
If you think you have seen enough Rails magic, you are mistaken my friend. Rails have a new trick up its sleeve: Hotwire. And with the magical Turbo tool that comes with it, you can create modern, interactive web applications with minimal, or sometimes no JavaScript at all, providing users with an incredibly smooth experience.
-
Why you should choose HTMX for your next project
There is also Turbo and the frameworks who adopt them, Ruby on Rails, PHP Symphony and possibly others that solves the same issue in the same manner as HTMX. And the choice for HTMX is only a personal taste in this, but you should definitely learn about this, this is as cool as HTMX!
-
JavaScript First, Then TypeScript
Most controversially, the Turbo framework dropped TypeScript support altogether after assessing that strong typing was the culprit behind poor developer experience.
-
Rack Attack – Rails Tricks
Turbo[0] has been solving this for years. Quite the contrary, front-end frameworks have started to think "sending JSON is good, but actually sending HTML could be great!".
DHH's presentation[1] during Rails World 2023 is quite interesting in that regard, I recommend you give it a go (start around minute 16). I am actually very excited with his vision of the web.
[0] https://turbo.hotwired.dev/
What are some alternatives?
supabase - The open source Firebase alternative.
htmx - </> htmx - high power tools for HTML
CompCert - The CompCert formally-verified C compiler
Turbolinks - Turbolinks makes navigating your web application faster
create-t3-app - The best way to start a full-stack, typesafe Next.js app
hotwire-rails - Use Hotwire in your Ruby on Rails app
pocketbase - Open Source realtime backend in 1 file
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
vite - Next generation frontend tooling. It's fast!
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)
wasp - The fastest way to develop full-stack web apps with React & Node.js.
importmap-rails - Use ESM with importmap to manage modern JavaScript in Rails without transpiling or bundling.