HNHacker News
TopNewBestAskShowJobs

montroser

3,628 karma · joined December 27, 2018

submissionscomments
montroser··on Dumb TVs deserve a comeback
Why wouldn't streaming devices do all the same surveillance? Don't they have as much financial incentive and broad access as tv manufacturers?
montroser··on The correct amount of ads is zero
It's a funny anecdote and cool hack to be able to skip streaming video ads, but it's also kinda entitled to leech the content and shift the burden onto everyone else.
montroser··on Generate video sprites using just FFmpeg
A long time ago, we used this approach to play videos at 15 fps in IE6, with no flash or realplayer plugins required! No sound though...
montroser··on TrunkVer
A sequential build/release number would suffice in many cases.

If the thing you're shipping isn't meant to be a dependency for other projects, then semantic versioning doesn't really fit.

In trunkver though, using the timestamp of the build time is a little weird, since you could inadvertently end up building an earlier version of trunk at a later time.

Putting an identifier of the job that built the release in the version number also seems heavy for what could just be an entry in a log file for when you need those forensics.

montroser··on How I configure my Git identities
I used to work at a startup with a character who would set his identity to be random fairytale-sounding nonsense, changing every day. So his commits on Monday would be attributed to Mr. Bunnymann, and Tuesday would be Doctor Funtime, etc.

It was super unhelpful when trying to do version control forensics. But if I'm being generous, I think maybe he was trying to remind everyone that anyone can put anything in their identity config, and we shouldn't trust whatever is in there for all that much.

montroser··on Don’t look down on print debugging
Some of the trickiest bugs to hung down are those involving concurrency and non-deterministic timing. In these cases, stepping through a debugger is not at all what you want, since you may actually change the timing just by trying to observe.

To see the nature of the race condition, just put some print statements in some strategic locations and then see the interleaving, out of order, duplicate invocations etc that are causing the trouble. It's hard to see this type of stuff with a debugger.

montroser··on Delta: A syntax-highlighting pager for Git, diff, grep, and blame output
Not as fancy, but if you want halfway reasonable word-level diffs with just standard issue git, this is often good enough:

  git diff --color-words --word-diff-regex='\w+|.'
montroser··on Ask HN: How to roll out an internal UI component library
Having both failed and succeeded at this many times in companies from 20 to 1000 people -- here is my advice for you:

Start with the absolute gnarliest, high-traffic, most intricate UIs that are in production now. Design your components to accommodate those most important and valuable use cases, in partnership with the teams responsible for those interactions. If you can handle those, and if you can get those developers to prefer your components because they're easier to work with and they solve the problems the existing tangle is solving, then you will win. Everything else after that will be smooth and easy and it will work.

On the other hand, if you design in isolation, you will likely end up with another beautiful "living style guide and component library" that no one ever uses, because it is not flexible enough to handle real-world interactions, where the designers and product people and engineers all have hard-won legitimate strong feelings about how it all should fit together in the actual product that's making all the actual money.

montroser··on Why NPR conversations sound so fake: Reporter two-ways
This "training" document tries to convince reporters that they can have natural-sounding conversations on air, that are actually preplanned and fully scripted. Of course in practice, it is nearly impossible.

In fact, it seems a misplaced goal in the first place, for a news organization presenting itself as an authentic source of information, acting in the public interest -- to invest so much in a format that is fundamentally inauthentic.

Could this be part of the reason that listenership is declining?

montroser··on The "email is authentication" pattern
I am one of those people who always clicks "forgot password", and sorry but it's actually fine. I type a long, completely nonsense sequence of words and characters for my new password, then ctrl-c to copy, then log in with that password, and then promptly forget it.

It cannot be more secure to store it in a password manager than not to store it at all. The email recovery path exists in either case, so that part is a wash.

montroser··on Code Review Anxiety Workbook
Yeah, agreed that it is a good mindset to approach as a teaching and learning opportunity.

On the anxiety aspect, I think my point is that -- okay, exercises and workbooks can have their place, but the real way forward is to have a thorough understanding of the task at hand and provide your constructive criticism and help your team make their way.

If you need more context, ask questions. If you need to poke and prod to understand how the pieces fit together, then poke and prod. With all of that knowledge you can have a productive conversation about the proposed changes.

On the other hand, without all of that, then it is guaranteed to be anxiety inducing, since with your review, you are taking some amount of responsibility for a thing you may not sufficiently understand.

montroser··on Code Review Anxiety Workbook
That workbook is all about anxiety in general, which is fine, but there's almost nothing specifically to do with anxiety as it relates to code review.

Here's my advice: Focus on whether the change actually solves the problem it's trying to solve. Run the code; does it work? What regressions could it cause? Is there any way it could be simpler?

Along the way, you may notice style guide offences, or minor nitpicks. It's good to take note of those things, but only raise those issues once you've addressed the fundamentals.

At the end of the day, confidence comes from understanding. So dig in and understand the context, understand the effects of the change, and give the best feedback you can to help get to the best solution.

montroser··on Signals for Tailwind CSS (styling based on ancestor state via style queries)
Tailwind is both great and terrible. The trick is to take just the good parts and not let it poison the rest. Let it make easy things easier, but don't let it take over and make the hard things impossibly difficult.

Here's how to do it: use Tailwind only for layout (margin, padding, flex) and brand consistency properties like text size, line height, colors etc. Beyond that, anything that requires changing presentation based on state, embrace CSS. It was meant for this, and remains the best solution. Invest in learning CSS because it will still be here in 20 years.

montroser··on Mozilla removes telemetry service Adjust from mobile Firefox versions
Speaking of mobile Firefox, they're pursuing this abomination of a UI update for Android too: https://connect.mozilla.org/t5/discussions/updates-to-androi...
montroser··on Why is a Guillotine blade diagonal?
It'd be tough to keep that inside corner sharp...
montroser··on Police cannot seize property indefinitely after an arrest, federal court rules
The standard for arrest, probable cause, is far too weak to be any basis for indefinitely seizing property. A precedent ruling on this by the Supreme Court would be welcome, but it's hard to say which way it would go, given the current makeup of the court.
montroser··on Dasel: Select, put and delete data from JSON, TOML, YAML, XML and CSV
Cool project -- but we need a standardized/spec'd query language in order to realize the goals in the "one tool to rule them all" section of this readme.

I have a hard time internalizing the jq query syntax, and am not overly excited to invest in learning all the quirks when it's not based on a widely-adopted open standard. Maybe `JMESPath` could be the way forward.

Sometimes `gron` can be a pretty great alternative approach, depending on your use case. At least it is very intuitive and plays nicely with other tools.

montroser··on Automerge: A library of data structures for building collaborative applications
See also Pigeon[1], which is inspired by automerge but takes a different approach:

> While Automerge optimizes for working offline and merging changes periodically, Pigeon is optimized for online real-time collaboration.

[1]: https://github.com/frameable/pigeon

montroser··on Jelly Star – The Smallest Android 13 Smartphone
Well hey, that does look interesting! I wonder what the screen resolution will be, and whether it will actually make it to market. But either way, nice that there might be something in the works.
montroser··on Jelly Star – The Smallest Android 13 Smartphone
Yes! That first generation Moto X was the premature peak of the small Android phone. After that everything just got bigger and increasingly less beautiful.
montroser··on Jelly Star – The Smallest Android 13 Smartphone
This is cool as an option. But, why oh why mustn't we have any 5 inch Android phone on the market? It's not as if there's no demand, as evidenced by iPhone SE on the iOS side. The last real Android choice was the Pixel 4a and beyond that, everything has been mega huge.
montroser··on Firefox Android to scrap URL from new address bar
Yeah. As if URLs are somehow "not for regular people". That only the dorks and nerds could possibly understand such things. The idea that we must hide this type of information both underestimates humanity and undermines the whole concept of the world wide web.
montroser··on Firefox Android to scrap URL from new address bar
Firefox Nightly now has a double-height address bar with only the domain, instead of the full url. And then a non-optional second row with a toolbar containing dedicated back and forward buttons. No option to turn this insanity off...
montroser··on Show HN: Dut – a fast Linux disk usage calculator
Yeah, maybe approximation is not really possible. But it still seems like if you could do say, up to 1000 stats per directory per pass, then running totals could be accumulated incrementally and reported along the way.

So after just a second or two, you might be able to know with certainty that a bunch of small directories are small, and then that a handful of others are at least however big has been counted so far. And that could be all you need, or else you could wait longer to see how the bigger directories play out.

montroser··on Show HN: Dut – a fast Linux disk usage calculator
Nice work. Some times I wonder if there's any way to trade away accuracy for speed? Like, often I don't care _exactly_ how many bytes is the biggest user of space, but I just want to see some orders of magnitude.

Maybe there could be an iterative breadth-first approach, where first you quickly identify and discard the small unimportant items, passing over anything that can't be counted quickly. Then with what's left you identify the smallest of those and discard, and then with what's left the smallest of those, and repeat and repeat. Each pass through, you get a higher resolution picture of which directories and files are using the most space, and you just wait until you have the level of detail you need, but you get to see the tally as it happens across the board. Does this exist?

montroser··on GPU-Friendly Stroke Expansion
Stroke expansion is one of those things that initially seems obvious and intuitive, but then turns out to be wildly complex once you embark upon handling all of the many edge cases.
montroser··on Copy and Paste context menu entries sometimes disabled when they should not be
Overall, Firefox is wonderfully fantastic these days.

I can see how this is frustrating to some, but sometimes that's how the priority nets out. It looks like the bug was triaged, investigated, took its time finding its way to the right developers, and now a fix will land soon.

This is mostly just the process working. I for one, am grateful for these folks' good work.

montroser··on Exploring Randomness in JavaScript
Here's my favorite deterministic PRNG optimizing for implementation simplicity:

    function random() {
      random._s = random._s || 11224; // seed
      return (random._s = random._s * 16807 % 2147483647) / 2147483646;
    }
Wikipedia says this approach has been around at least since the 1950s.

https://en.wikipedia.org/wiki/Linear_congruential_generator

montroser··on Texture Enhancement for Video Super-Resolution
No, that appears to be incorrect.

It is the case that with completely generative models, you will get hallucinated details very likely to be untruthful. But with this approach, you can see blurry input images of license plates that with our naked eye we could not possibly decipher the characters, then put through this model where the output is very close to the actual ground truth.

https://dachunkai.github.io/evtexture.github.io/static/image...

Where does this information come from? It seems they are generating synthetic "event camera-like" events just from diffs between still frames? So maybe they trained a model based on real events from a real event camera? It's hard to tell from their write-up. But these results are very impressive.

montroser··on NPM and NodeJS should do more to make ES Modules easy to use
Node should just do like bun and support intermixing both. It was a mistake to force this schism -- untold hours of frustration and busywork for maintainers and developers with no hope of actually "completing" a mythical full transition to the new world.

And for what? In Node specifically, it's not as if esm actually solves any real problem! In the greater ecosystem, sure it has some benefits, but Node doesn't even have to choose. Just support both at once, like bun and build systems have for a while, and let's move on from this nonsense.

← PreviousPage 9 of 21Next →