Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Migrating Dillo from GitHub

dillo-browser.org

Post reply on HN
Print view View original

211–219 of 219 posts

Re: Migrating Dillo from GitHub

#211

Post by IgorPartola »

Etheryte wrote: post #203
IgorPartola wrote: post #153

Earlier quoted context omitted.

Setting up a server with SSH and GitLab is more work than setting up a server with SSH. Dropbox is great and I use it but only because I can’t get the same functionality out of rsync without major additional orchestration. But if I am the only one working on my own project why would I need a second read-only UI for my own code?

If you're working alone you can also send raw IP packets down the wire by way of telegraph key if you'd like. What you do alone behind closed doors isn't really anyone's business and is up to you. For everyone else, the benefit of using Gitlab is that once it's set up, a wide range of users of varying skill levels and backgrounds can use it to collaborate.

Which is why I asked if there is any benefit to that type of setup for personal projects. Your answer so far has been the least helpful or informative.

Re: Migrating Dillo from GitHub

#212

Post by ben_w »

simonw wrote: post #13
superkuh wrote: post #2

>frontend barely works without JavaScript, ... In the past, it used to gracefully degrade without enforcing JavaScript, but now it doesn't. And the github frontend developers are aware of these accessibility problems (via the forums and bug reports). They just don't care anymore. They just want to make the site appear to work at first glance which is why index pages are actual text in html but nothing else is.

I'd love to hear the inside story of GitHub's migration of their core product features to React. It clearly represents a pretty seismic cultural change within the company. GitHub was my go-to example of a sophisticated application that loaded fast and didn't require JavaScript for well over a decade. The new React stuff is sluggish even on a crazy fast computer. My guess is that the "old guard" who made the original…

> My guess is that the "old guard" who made the original technical decisions all left, and since it's been almost impossible to hire a frontend engineer since ~2020 or so that wasn't a JavaScript/React-first developer the weight of industry fashion became too much to resist.

I very much hope not, but fear you're right.

I'm (theoretically) an iPhone app developer, and I really dislike the Reactive idiom: I can see the theoretical benefits, but in practice, the magic glue has never worked right, and comes at a painful performance cost. React is to me what LLMs are to LLM-skeptics.

I'm retraining anyway due to LLMs and how well they eat UI, but I don't yet know where I'll end up next.

Re: Migrating Dillo from GitHub

#213

Post by RNCTX »

In the same post where the author of this blog article says they "don't like getting notifications about activity in my repo, and instead prefer to 'work offline' and 'only check in when I want' to... the author also details how they lost their domain which was bought by an ad spamming site guy.

I mean, are the scripts writing themselves here, boys?

Re: Migrating Dillo from GitHub

#214

Post by llbbdd »

yeasku wrote: post #167
venturecruelty wrote: post #157

Earlier quoted context omitted.

Why should you need JavaScript to render text and buttons? Were browsers unable to do this prior to the JavaScriptification of everything?

The same reason you need to use LLMs to code.

Do you copy and paste every comment you make on HN or is this just for me?

Re: Migrating Dillo from GitHub

#215

Post by llbbdd »

venturecruelty wrote: post #157
llbbdd wrote: post #120

Earlier quoted context omitted.

it's also a real accessibility problem if you're trying to use sticks and rocks to access the internet

Why should you need JavaScript to render text and buttons? Were browsers unable to do this prior to the JavaScriptification of everything?

It has been, this year, 30 years since JS became a normal part of the web. You don't need it to render text and buttons, but we do different things with the internet now.

Re: Migrating Dillo from GitHub

#217

Post by ffsm8 »

xrd wrote: post #19

I've been messing around with GitLab as a self hosted alternative for a few years. I do like it, but it is resource intensive! For the past few days I've been playing with Forgejo (from the Codeberg people). It is fantastic. The biggest difference is memory usage. GitLab is Ruby on Rails and over a dozen services (gitlab itself, then nginx, postgrest, prometheus, etc). Forgejo is written in go and is a single binary.…

And gitea is once again a fork from gogs that happened with some controversy in the beginning.

The gitea project has a lot more features such as CI and SSO at this point, gogs continues to be a viable alternative if you actually only want a git server with an UI like GitHub was in early 2010s - and are on resource constrained hardware

Re: Migrating Dillo from GitHub

#219

Post by SuperSandro2000 »

WD-42 wrote: post #30

> To avoid this problem, I created my own bug tracker software, buggy, which is a very simple C tool that parses plain Markdown files and creates a single HTML page for each bug. The hacker spirit alive and well.

No one should write C software in 2025...
Post reply on HN