Sat Jul 1, 2017
This is gonna sound like a negative essay. Which it kinda is. But it's very much not a condemnation of Vue!
Vue is great. You should try Vue.
If I had written What Vue Doesn't Need it would be an incredibly long post! This is just things I wish were better about it.
I’ve been using Vue a lot recently on a few test projects, and most notably on Buttondown.
Buttondown’s frontend is 100% Vue: around twenty screens (which are themselves components) and around thirty miscellaneous components, tied together with Vuex and Vue-Router.
Overall, Vue is a really great tool, and the first word I’d use to describe it is pragmatic. Almost everything feels and acts sensible; there are tremendously few times that I am confused or surprised by how it works, which is legitimately novel (and wonderous) after the hours and days and weeks I’ve spent pulling my hair out dealing with random React and Webpack arcana.
Still, there are some bugaboos that I think arise from Vue’s current niche as a “lightweight” approach to creating a functional SPA, in much the same way that Flask carved out a niche as being a lightweight alternative to Django.
Sat Apr 29, 2017
Kelly Sutton wrote a great article about how TDD impacts software design:
Design Pressure is the little voice in the back of your head made manifest by a crappy test with too much setup. It’s a force that says when your tests become hard to write, you need to refactor your code.
I think this is absolutely correct, and touches on a larger concept that I’ve been internalizing over the past few months – that the best methods for evaluating the soundness of a codebase come from activities adjacent to the codebase.
(Or, to use fewer syllables, if it sucks to do something with the code, then the code probably sucks.)
Sat Apr 15, 2017
I’ve read two bad takes recently on how “faux native” technologies are considered harmful.
The first is alarmingly titled Electron is flash for the desktop:
Also all you web devs: Go learn C or Rust or something. Your program runs on a computer. Until you know how that computer works, you’re doomed. And until then get off my lawn shakes fist.
The second, a little less insufferable, is about an iOS developer’s experience with React Native:
Chances are that your finished RN app is going to feel like a not-quite-native iOS app and a not-quite-native Android app. Some people will have a bigger problem with this than others and most users of the general population won’t notice. But you do risk losing platform specific niceties that users will notice.
Both of these articles make some fair points, even if they’re not cogent overall.
Thu Mar 9, 2017
Here’s an old joke (or story, or fable, or whatever you want to call it) that I’ve heard some variation of a dozen times.
The new Jewish bride is making her first big dinner for her husband and tries her hand at her mother’s brisket recipe, cutting off the ends of the roast the way her mother always did. Hubby thinks the meat is delicious, but says, “Why do you cut off the ends — that’s the best part!” She answers, “That’s the way my mother always made it.”
The next week, they go to the old bubbie’s house, and she prepares the famous brisket recipe, again cutting off the ends. The young bride is sure she must be missing some vital information, so she askes her grandma why she cut off the ends. Grandma says, “Dahlink, that’s the only way it will fit in the pan!”