HNHacker News
TopNewBestAskShowJobs

biggestlou

1,422 karma · joined December 22, 2016

submissionscomments
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
I'm just not a fan of the aesthetic and it isn't as feature rich as I plan on making Tract. But if Docsy works for you, I fully support that!
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Definitely. Confluence is fine for some use cases, but personally I'm strongly in favor of a version-controlled approach.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Also, you win. I changed the color scheme.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Sweet! Definitely stay tuned!
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
It works as self-deprecation because it’s not really something worth getting all worked up about, and yet here I am
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Could you say more about this? What exactly is broken about the experience in Tract? I have never heard of Qutebrowser.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Docusaurus is a very nice tool but in my extensive experience React-based static site generators really suffer when building large sites, much like Jekyll does. I've worked on projects with well over 1,000 pages and Docusaurus, VuePress, and others simply don't have access to the jet engine that is well engineered Go. But if it works for you, run with it!
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Yep. Love the static approach. I haven't yet a use case for a React/Vue static generator but a lot of really powerful stuff is being built.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Nice work! Very cool project. Love to see it.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Yeah, this is something I plan on playing with a bunch leading up to the alpha launch, potentially making this configurable.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Yes, I'm working on the navigation. Tract is currently pre-alpha and this will improve by leaps and bounds in the next few weeks.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Nice! I hadn't seen Fuse but it looks like a great option. I've used lunr.js on other projects and liked it but always open to explore new things.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
I plan to offer several options for search (as covered in the blog post). Some existing themes provide search. YMMV.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
I personally find RTD far too drab for my tastes but to each their own. If it works for you, run with it!
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
That color is mostly a placeholder, and in the actual theme you'll be able to change the color scheme in the site configuration (without needing to touch CSS).

I agree that aesthetics are absolutely CRUCIAL and this will be a MAJOR focus of the project.

You can see this in action here: https://github.com/tract-docs/tract-docs.dev/blob/master/con....

biggestlou··on Purple: An all-in-one data service for microservices, FaaS functions, and more
Bot
biggestlou··on The Updated Draft Design for Go 2 Contracts
What in the draft is unclear?
biggestlou··on Bacteria can travel thousands of miles through the air on their own
*on their own
biggestlou··on K3s – Lightweight Kubernetes
That's literally not Kubernetes, though. Does it support custom resource definitions? Services? Deployments? ConfigMaps? Multiple containers on a single host, i.e. Pods?

Your project does sound very cool but I don't think provides a fair basis of comparison re: size and RAM usage.

biggestlou··on PlanetScale makes it easy to build multi-cloud databases
The drawer could use some polish on mobile
biggestlou··on Netlify raises $30M to replace webservers with Application Delivery Network
Sure, but GitHub Pages is a relatively “dumb” host. You don’t get preview builds, branch deploys, and lots of other things. It’s nice for a minimal approach but for a large site with lots of people working on it I would not recommend it.
biggestlou··on Everyone does not, in fact, have a book in them
This is one of my biggest grammatical pet peeves. The title (and corresponding sentence in the article) should really be "Not everyone, in fact, has a book in them." I'm finding this more and more frequently even in legitimate publications and it's maddening.
biggestlou··on Migrating from Jekyll to Hugo
An asset pipeline (and templatized at that) is being added to Hugo as we speak. Just Sass support to begin with but more later. Once that’s added the reasons to use Jekyll, which is essentially abandonware, will shrink to zero.
biggestlou··on Show HN: An Example Microservice Back End for Kubernetes, Bazel, Go, Java, GRPC
I must say, Java was pretty seamless. I followed the instructions and it came together quickly. Go was harder because there's a vendoring issue (surprise!) in that Bazel requires two versions of the gRPC for Go library ("google.golang.org/grpc"), one for Bazel, the other in Go's vendor directory. Gazelle tries to make you use the vendored version, which leads to a conflict, so I had to figure out how to disable that default behavior, which took a few hours of banging my head against the wall followed by reaching out to the Bazel Google Group, which quickly yielded a workaround (thanks, Ofer!).

Beyond that, the real issue is that no other languages have "official" gRPC support, i.e. support from the core Google team rather than from third parties. I do hope that they expand the number of languages soon.

biggestlou··on Show HN: An Example Microservice Back End for Kubernetes, Bazel, Go, Java, GRPC
Things have improved but only marginally. Java and Go are the only languages that have "native" gRPC support in Bazel. For others you need to rely on an external repo whose connection to Google is unclear (https://github.com/pubref/rules_protobuf). I find this disappointing, as a gRPC-connected microservice architecture that Just Works and easily interoperates with Docker/Kubernetes/whatever seems like it could be THE "killer app" for Bazel. I built this project to say "look, it's easy!" But alas, it wasn't, and I've communicated that to some core Bazel folk.
biggestlou··on Show HN: An Example Microservice Back End for Kubernetes, Bazel, Go, Java, GRPC
Fair enough. I even joked about this on Twitter: https://twitter.com/lucperkins/status/1000878351903477765
biggestlou··on Show HN: An Example Microservice Back End for Kubernetes, Bazel, Go, Java, GRPC
Just out of curiosity, what about it strikes you as potentially satirical?
biggestlou··on Show HN: An Example Microservice Back End for Kubernetes, Bazel, Go, Java, GRPC
Very cool. Eventually I'd like to turn Colossus into something more like what you have here, i.e. a "real" backend that does something meaningful. The good news is that the Bazel + gRPC plumbing was the hard part. Adding new, meaningful services will be pretty trivial going forward.
biggestlou··on Show HN: An Example Microservice Back End for Kubernetes, Bazel, Go, Java, GRPC
It was a hassle mostly because a lot of the libraries are new and the interfaces are still changing a lot. Bazel is a fantastic build tool that I'd recommend for large projects. The Bazel + gRPC story, though, has a ways to go.

But I don't see any reason why you shouldn't use Bazel + gRPC for a larger project. You may have to tweak small things in the future but I suspect that the UX will only improve. Plus, you can always write your own Skylark rules if Bazel isn't cutting it for you in some way.

biggestlou··on A Case Study in LASP and Distribution at Scale [video]
You can't, as far as I know. You can do this, though: https://www.skill-space.com/blog/2015/11/16/create-an-auto-i...
← PreviousPage 6 of 7Next →