live
handbook
Our great sponsors
live | handbook | |
---|---|---|
17 | 13 | |
613 | 6,275 | |
- | 0.4% | |
3.8 | 8.7 | |
5 months ago | 3 months ago | |
Go | ||
MIT License | GNU General Public License v3.0 or later |
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.
live
-
How to Fetch a Turbo Stream
Looks like there are a couple of attempts but my google fu didn't really yield a winner.
https://github.com/while1malloc0/hotwire-go-example
https://github.com/jfyne/live
if that's the case, there is definitely an opening on the market for such tech.
As someone who's been writing web apps since DHTML days, Livewire/Turbo feels like we've finally reached the future.
-
The secret weapon of LiveView development is …
You can see all those “live-” attributes in a small example above. We just say: “ live-click=’tempUp’ “ and Live implementation makes all bindings to our backend code and makes a websocket call for the appropriate Go handler.
-
Not a Go LiveView developer yet? Try to guess what this code is doing, though.
LiveView implementation for Go raised the same type of feelings in me when I went through this for the first time.
-
3 issues LiveView development in Go resolve efficiently for small teams
And here it is, where LiveView programming concepts help us in a great way. LiveView uses websockets to create a persistent connection between the client and the server, which enables the server to push updates to the client in real-time. This allows developers to build interactive user interfaces that can update dynamically in response to user actions or changes in the application state, without the need for traditional page reloads or AJAX requests. LiveView programming style is based on this excellent Live project that is an implementation of the LiveView approach in Go.
- Show HN: A Full-Stack Web Framework Written in Go
-
Spas Were a Mistake
I hate SPAs. I would never do another SPA again if it were up to me. It just adds too much mental context switching and overhead. I can develop fully server-side apps that are lighter, run faster, and at least 20% less development effort (I actually compared that for the same task: https://medium.com/@mustwin/is-react-fast-enough-bca6bef89a6). So why would I ever do an SPA again if it were up to me. I would use https://github.com/jfyne/live which is inspired by Phoenix LiveViews. This is my professional opinion having many years of experience in both kinds of web apps.
-
Show HN: LiveViewJS – TypeScript back end for LiveView Apps
I've been working on a Go implementation if you fancy trying it out
https://github.com/jfyne/live
- What frontend libraries do exist in Go?
-
Looking for early feedback on my new Phoenix LiveView inspired project.
I built it because I love building highly interactive web pages, but the current state of JavaScript leaves me cold. I got really excited when I saw what Phoenix was doing with LiveView and thought I could see the light at the end of the tunnel. There are already a couple of projects also inspired by LiveView (GoLive, live), but I had my own vision that I wanted to realise.
-
go-echo-live-view
Josh Fyne started a nice implementation of a Phoenix LiveView Go implementation here: https://github.com/jfyne/live
handbook
-
The 37signals Employee Handbook
As of the writing of my comment, 2 days ago:
https://github.com/basecamp/handbook/commits/master/
-
Designing a team that would produce software of good quality: set up dogfooding
37signals went even further, they build products for themselves first:
- Realizing I actively dislike this industry, but feeling trapped by the salary. Anyone pushed through this? What kind of roles does this skill set transfer to if you wanted to leave tech?
-
Spas Were a Mistake
That's definitely true at the organizational level, and it's an argument with some merits.
In practice though, I've seen this backfire. You end up with the frontend team blocked because the API they need isn't available yet, and then the backend team gets blocked because they shipped the API but they can't use it to deliver value because the frontend team don't have the capacity to build the interface for it!
My preference is to work on mixed-skll teams that can ship a feature independently of any other team. I really like the way Basecamp describe this in their handbook: https://github.com/basecamp/handbook/blob/master/how-we-work... - "In self-sufficient, independent teams".
- Basecamp Updates Code of Conduct
-
POS CEO? Piece of shit CEO?
The link: https://github.com/basecamp/handbook/pull/106
- “About one-third of Basecamp employees accepted buyouts today”
-
Basecamp implodes as employees flee company, including senior staff
https://github.com/basecamp/handbook/blob/63e97c8210465a5e7f1731eac76e6d9d9e20d29b/benefits-and-perks.md#profit-sharing
-
Basecamp can't seem to touch base with some very public updates to their company's rules.
No more paternalistic benefits. (Benefits like fitness allowances, wellness allowances, and notably not mentioned in their blog post, charitable donation matching. Instead that's changing to 10% profit sharing. As an aside from yours truly, this means those benefits only will do as well as the company does. Company has a year with a loss? Whoops! No profits to share.).
What are some alternatives?
bud - The Full-Stack Web Framework for Go
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
go-app - A package to build progressive web apps with Go programming language and WebAssembly.
Novo-Cantico - New kind of web development framework
hlive - HLive is a server-side WebSocket based dynamic template-less view layer for Go.
Apache Wicket - Apache Wicket - Component-based Java web framework
loopback-example-facade - Best practices for building scalable Microservices.
react-rails - Integrate React.js with Rails views and controllers, the asset pipeline, or webpacker.
golive - ⚡ Live views for GoLang with reactive HTML over WebSockets 🔌
yeti
diffhtml - diffHTML is a web framework that helps you build applications and other interactive content
htmx - </> htmx - high power tools for HTML