Recent submissions

Comment · 8 years ago
This is a huge achievement - props to the Gradle maintainers for delivering so much with such careful adherence to backcompat! I’ve had two enableFeaturePreview lines in my repos for a few weeks now and it made upgrading to Gradle 5.0 a zero manual action upgrade!
Comment · 8 years ago
We require all teams to use semver and usually define the Conjure API in the same repo as the server that implements it (so they are versioned together). Most of the time teams want to preserve wire-format back compat (i.e. only add optional fields to requests and don’t remove things from responses). Devs are pretty good at this, but we actually run a conjure-backcompat checker as part of CI to catch any unintended breaks they might have missed.

When it comes to intentional breaks, teams save up a bunch of carefully documented changes and then tag the next semver major version (i.e. 2.0.0). This is safe to do because all microservices and frontends we build actually contain embedded minimum and maximum version constraints on the backend services they require. Our deployment infrastructure knows about all these constraints and can then ensure that new major releases will only be rolled out in production when all their callers have explicitly declared support.

Comment · 10 years ago
It's definitely not as elegant as Scala or Haskell, but I think their justification is very reasonable. The current implementation is maximally compatible with existing usages of tagged unions (e.g. Redux actions), because it allows you to choose whatever discriminant you like ('type', 'kind', whatever). Keeping very close to JS seems to be a core tenet of TypeScript and is quite valuable in my opinion. It means they can adopt new ECMAScript syntax without clashes and also ensures that newbies have a smaller learning curve. Also, they can always add in some syntactic sugar later if they want to!
Comment · 10 years ago
I usually want to keep an eye on my Selenium tests so I can debug them if they get stuck. When I don't have enough space to leave the selenium VNC window open, I put it underneath a semi-transparent terminal window which allows me to keep working.
Comment · 11 years ago
Nicely comprehensive blog post, Zorium looks like it is the result of a lot of hard work! Since this looks like a serious library (rather than a personal dev exercise), I'm curious about why you decided not to go with React:

1. The React source is definitely intimidating - what extensions did you feel it needed?

2. Animations are a tough problem, but I was under the impression that the communication isn't usually the problem, it's meshing a declarative representation with a mid-transition DOM. How is the Zorium approach better than the React one?

3. Flux, JSX and mixins are all completely optional and not compulsory to write a frontend in React; why did these motivate you to write a new library from scratch?

I hope these don't come across too critical, I have a lot of respect for anyone who can even finish a project like this, let alone document it. I've heard lots of good things about React, so I'm curious to hear other perspectives!

Comment · 11 years ago
Comment · 11 years ago
Comment · 11 years ago
There's a gem right at the end from 1878:

"Oldest known publication of a recording of recognizable phrases in the English language (“Brown University”; “How do you do?”)"

Comment · 11 years ago
Comment · 11 years ago
Comment · 11 years ago
Comment · 11 years ago
Comment · 11 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton