HNHacker News
TopNewBestAskShowJobs

biggestlou

1,422 karma · joined December 22, 2016

submissionscomments
biggestlou··on Recently minted database technologies that I find intriguing
This is a very interesting development that I'd like to learn more about. Whenever I've played around with writing databases (just as toy projects) I've always done so using RocksDB or something similar as a backend. This "thick client" model, though, seems to have a lot of potential benefits, most notably no need to worry about disk space or volumes (so say goodbye to a bunch of config parameters) and no need for a tiered storage setup or S3 migration tools (already accomplished!). Not ideal for most use cases but intriguing for some!
biggestlou··on Recently minted database technologies that I find intriguing
Derp! Fixed that.
biggestlou··on Recently minted database technologies that I find intriguing
I apologize for the strength of my language. There are several words I used in that comment that I should not have. It's far too easy to forget in the moment that there are real people making these decisions who may very well read what you say. I understand where you're coming from with the decision and will try to select more appropriate titles in the future. And will be much more mindful about how I register complaints.
biggestlou··on Recently minted database technologies that I find intriguing
REMOVED: I complained about the rewritten title in a way that was excessively harsh and have removed that comment.
biggestlou··on Recently minted database technologies that I find intriguing
I haven't come across Milvus but I'll check it out!
biggestlou··on Strapi – Open-source Node.js Headless CMS
I gave this a spin a while back and the experience was really really not great. I created a new content type and tried to name one of the fields "ID," not knowing that an ID field is automatically added to any content type. Instead of throwing a helpful error, that not only crashed the running server but also made it impossible to restart the server until I manually deleted the offending auto-generated JS file for the type. A minor quibble, perhaps, but the first impression stuck and I haven't touched it since.
biggestlou··on Why is Kubernetes getting so popular?
Kubernetes got popular because it was the first system that came along that provided a CRUD API for resources of all kinds, including custom resources (CRDs), and was immediately compatible with public artifact hubs like DockerHub and Google Container Registry. The second one is the real kicker here, and I think is why Kubernetes "won" and Mesos et al did not. With Mesos et al you had to set up your own artifact storage. As powerful as Mesos was, there was no MesosHub.

Longer term, I think the contribution of Kubernetes will be getting us used to a resource/API-driven approach to infrastructure that abstracts away cloud providers, hardware, etc. But it will probably be superseded in the coming years by something that honors similar API "contracts." Probably written in Rust troll

biggestlou··on Lovely Week with Elixir
I've used protocols, and they are useful as a kind of bare minimum interface/implementation abstraction. But they're nowhere even close to something like Rust traits. Which is totally fine given Elixir's goals.
biggestlou··on Lovely Week with Elixir
I learned Elixir a few weeks ago as a quarantine self-improvement project and pretty much loved it. There are some warts, as in any language. As someone who's primarily worked in Go and Java in the past and has also been learning Rust I don't super love the optional typing thing, and I end up missing higher-level data constructs like interfaces and traits.

But there are some great language features, like guards and pattern matching, that are hard to give up when you go back to other languages.

Plus it's great to have OTP goodies like GenServer at your fingertips if you run into performance bottlenecks (which you may not!). The OTP APIs are a bit weird coming from other languages but not too bad.

Other things I've liked:

1. Ecto is simply the best DB library I've encountered in any language. I'd almost recommend learning Elixir just to be able to use Ecto.

2. Plug provides great HTTP ergonomics highly reminiscent of Go's context-based middleware approach. Having direct access to the full request/response lifecycle is a win.

3. Phoenix is nice because it's essentially just Plug with some convenient helpers on top. Strikes a really nice balance between configuration and convention by letting you use only what you need. Haven't tried LiveView as I'd prefer to handcraft my own JS but probably worth a shot.

4. Absinthe is the best GraphQL framework I've encountered after many others in other languages left me completely cold.

biggestlou··on What every software engineer should know about Apache Kafka
Spreading data on all BookKeeper nodes, yes :) Pulsar brokers are themselves stateless.
biggestlou··on Kafka Removing Zookeeper Dependency
That is correct: Pulsar uses ZooKeeper relatively lightly and only for things strictly necessary for the cluster to run. Everything else (message data, topic info, cursors, schemas) is stored in BookKeeper.

Would still be great to see ZooKeeper made superfluous, though.

biggestlou··on What every software engineer should know about Apache Kafka
Pulsar is less mature but does provide functional equivalents to all of the above. Pulsar IO (Kafka Connect), Pulsar SQL (KSQL), Pulsar Functions (Kafka Streams).
biggestlou··on What every software engineer should know about Apache Kafka
Pulsar works quite well as a message queue: https://pulsar.apache.org/docs/en/cookbooks-message-queue/
biggestlou··on What every software engineer should know about Apache Kafka
But one of those moving parts of Pulsar, BookKeeper, means that you're no longer storing data on message brokers. Worth the extra puzzle piece for a lot of use cases.
biggestlou··on Next.js 9.4 – Fast Refresh, Incremental Static Regeneration
Or AlpineJS
biggestlou··on Don't write documentation in Markdown
I implore you: do not use anything but Markdown in environments where software engineers will be writing and maintaining the bulk of the documentation. I once worked on the docs team for a large org that used rST/Sphinx. Engineers complained incessantly and it was a constant struggle to cajole them to keep docs up to date.

My experience suggests unambiguously that engineers will not take the time to learn a different markup format. They will spend hours or days or weeks learning a new language, deployment tool, protocol, library, etc. But in most cases they will simply refuse to spend one iota of time learning documentation tools. If you think I'm wrong, try making it your day job to get engineers to write rST (or Asciidoc or anything they don't already know).

biggestlou··on Git-backed static website powered entirely by AWS
Kudos to the author for writing this up and making it work. The feeling that washes over me, however, is relief that we now have platforms like Netlify and a few others that do this for us.
biggestlou··on Show HN: An example GraphQL server written in Rust
I think it's more accurate to call it a language with high-level features
biggestlou··on Show HN: An example GraphQL server written in Rust
Yep, once you get the lower-level bits in place (which is still pretty tricky) you can iterate with confidence and surprisingly quickly. I created this project mostly to get people over the hump and into smoother sailing.
biggestlou··on Sir Ian McKellen's Lord of the Rings Production Blogs
Blog, not blogs
biggestlou··on Towards a Rust Foundation
Event planning resources for conferences, graphic design help, legal staff who specialize in OSS issues, money for infrastructure costs (CI/CD, compute and storage resources), money for day-to-day tools (JIRA, Slack, Zoom, Discourse), documentation and web design resources, and much more. Basically all of the background conditions necessary for collaboration and ecosystem growth to be as unimpeded by resource scarcity as possible.
biggestlou··on Towards a Rust Foundation
Wow. You created a Hacker News account an hour ago just to say this?

Who cares if it's "contentless?" Interactions on HN are frequently petty, mean spirited, and uncivil. Two people who are extremely active and give a lot to two different communities but don't know each other in real life had a pleasant interaction here that could have a fruitful outcome. Was this an event of Earth-shattering importance? No. But to read it as an illustration of the "vapidity...that infects open source projects" strikes me as noxiously cynical.

biggestlou··on Notes on Technical Writing
The problem with your perspective is an economic one. If you have the chops to be a hybrid TW/SWE, you will never take a tech writing job (or get out of tech writing as soon as you can) because tech writers simply make substantially less than engineers. Everyone acknowledges that tech writing is vital but until the pay story reflects that the status quo will persist.
biggestlou··on Apache Pulsar is an open-source distributed pub-sub messaging system
There are numerous places in the discussion where reasons for not choosing Kafka are elaborated.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Do you know of any particularly good libs for copy buttons, code tabs, and the like? I've seen a few out there but they seem pretty subpar to me.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Do you by chance have an article or some info you could share on this? I'm way out of my depth here.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
If you know of an all-CSS solution, I'm all ears
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Not so easy for a casual user. Building a nice interactive dropdown search widget (or something of the sort) requires solid JS chops and you need to know your way around Hugo to generate a search index. But others have done it and there are some good tutorials out there, so by all means give it a shot!
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Okay, I believe I've fixed this.
biggestlou··on Tract: A Hugo theme for ambitious documentation projects
Markdown parsers can auto-generate IDs for headers but they don't create a nice icon next when you hover over the header. That's what Anchor.js is for. For an example, see this page: https://kubernetescommunitydays.org/organizing.
← PreviousPage 5 of 7Next →