Easier, Better, Faster, Stronger #267
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
campaign-blocker
consider soon
Content
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry.tech#267
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As I've worked on
.tech
, I've tried to make it an excellent example of what a documentation site could/should be. Currently it's decent but is hiding hacks and "short-term" compromises that shouldn't be there.What I propose is to transition
.tech
to Sapper, a framework based on a compiler for true reactivity with SSR support (needed for SEO). Benchmarks aren't everything but the compiler powering Sapper is insanely fast. This video by Rich Harris explains it better than I could: https://www.youtube.com/watch?v=AdNJ3fydeaoAdvantages
.tech
has been around for some time so we have a better understanding of what it is and what is needed of it. We aren't "figuring things out" anymore.It'd be great if
.com
was moved to this too, but at a later date. I'd like to see how.tech
fares before looking at other projects.