Live data from Hacker News

Opossum: Cross-platform web browser written in Golang, optimized for Plan 9

github.com

1–10 of 98 posts

Re: Opossum: Cross-platform web browser written in Golang, optimized for Plan 9

#3

Has anyone built this? I'd love some screenshots of my website.

https://i.imgur.com/GPdnYBa.png

Building on mac was easy. It compiled fine with just go. But then to run it I needed:

git clone --depth=1 https://github.com/9fans/plan9port.git cd plan9port ./INSTALL

Re: Opossum: Cross-platform web browser written in Golang, optimized for Plan 9

#6
I fully acknowledge that Plan9 had a cool vision, maybe a superior one to the world we’ve got. But is it practical as an operating system for day to day use, particularly when working with other people using conventional Linux/Mac/Windows?

Re: Opossum: Cross-platform web browser written in Golang, optimized for Plan 9

#7

http client, UI interactions logic, domain models, utilities like tree operations, browser domain logic and all of that inside single go file? I think you'd make your life 10 times easier by splitting it better

What difference does that really make? In Go, all files in a directory share a namespace. I think the only impacts of splitting a file are build tags and shortening the import list, and neither really applies here.

Those components you listed could be in separate packages, but in a program this small that seems merely different, not better or worse.

Re: Opossum: Cross-platform web browser written in Golang, optimized for Plan 9

#8

http client, UI interactions logic, domain models, utilities like tree operations, browser domain logic and all of that inside single go file? I think you'd make your life 10 times easier by splitting it better

What difference does that really make? In Go, all files in a directory share a namespace. I think the only impacts of splitting a file are build tags and shortening the import list, and neither really applies here. Those components you listed could be in separate packages, but in a program this small that seems merely different, not better or worse.

>What difference does that really make?

Depends if you want to continue developing this (or any) project

If you want, then it makes huge difference, the faster you refactor it, then the easier the development will be.

If you want to stop putting effort into it, then there'll be no difference.

One file doing everything is almost always more annoying than stuff splitted correctly.

Re: Opossum: Cross-platform web browser written in Golang, optimized for Plan 9

#10

Earlier quoted context omitted.

What difference does that really make? In Go, all files in a directory share a namespace. I think the only impacts of splitting a file are build tags and shortening the import list, and neither really applies here. Those components you listed could be in separate packages, but in a program this small that seems merely different, not better or worse.

>What difference does that really make? Depends if you want to continue developing this (or any) project If you want, then it makes huge difference, the faster you refactor it, then the easier the development will be. If you want to stop putting effort into it, then there'll be no difference. One file doing everything is almost always more annoying than stuff splitted correctly.

Not just for continuing development in general, but it would be nice for potential contributors too!
Post reply on HN