Recent submissions

Comment · 1 year ago
I think it was a beta and not a demo but either way, it contained 95% of the game not obfuscated in any way. So I saw the ActionScript code quite a while ago!
Comment · 1 year ago
Comment · 3 years ago
There is a hardware button on Subarus to disable EyeSight when you go through the car wash.

Anecdotal, but the alarm before the auto braking in my Crosstrek (2020) saved me two times. And I was in the car with a friend who activated the auto braking when they had just purchased it and weren't used to driving it.

Comment · 4 years ago
I interviewed years ago with someone who let me know that they use a pseudonym as an employee and their chosen name even got posted as the author for articles they wrote for the company. They were very concerned about their privacy.

I know their blog, which is their HN username, and this tool found their other account.

Perhaps ironically, this person stood out a lot because of this and I didn't forget them.

Comment · 4 years ago
This is basically what iOS shortcuts is hoping to be. You can do some simple coding with widgets like that and then you can invoke your shortcut like `hey siri, <shortcut>`.

Avoids reciting the steps you want and gives you reliability, but I suppose requires any 'variables' to be hardcoded (or for you to create multiple instances)

Comment · 4 years ago
I made a few Atmosphere packages back in the day, some of them had a good # of users.

Aggregate database queries using Meteor (at least as of 1.0) would create an immense amount of backend overhead if you queried through minimongo. And the overhead was incurred as long as a user was on that page because of how the reactivity worked. I tried making a PR to optimize this but apparently it wasn't comprehensive enough. I kept checking for years but no one attempted to fix this. Before you get nostalgic for Meteor, issues like that were awful.

Meteor (and RethinkDB) were just* pub/sub you had almost no control over. Was fun playing around with, though!

* (also, being able to automatically add accounts and authentication was great)

Comment · 4 years ago
True enough overall, but I'm surprised no one has let you know that NPM actually doesn't allow you to delete packages anymore (after the left-pad controversy). You have to email them and then you are judged by how many downloads you have. If you have users relying on your package, they do not let you delete it.
Comment · 4 years ago
Thanks for posting this. An acquaintance of mine did this job 6 years ago and I wasn't sure if it still existed.

Crowd-sourced humans are making Google appear more intelligent than they actually are. I always envisioned that spam efforts would just immediately set off an alarm that would be handled by a bot to blacklist you without a human even knowing your site existed, but there still seem to be at least a few ways to game Google's search ratings.

Comment · 4 years ago
In the 2010s, there were a lot of posts about how C# could never even match F# even in 30 versions from that time.

But then C# started adding compiler flags that allow a redo of past suboptimal decisions (nullable reference types) without breaking existing code.

What is the current feeling on this? It seems kind of countered by the fact that the C# team is no longer bound by any past decisions.

Comment · 5 years ago
Wow Hackernews never ceases to amaze me, I enjoyed this. TIL I missed my 1 billionth second. You should also make a programmer mode, one that shows you powers of 2 (like 1024 days old)
Comment · 5 years ago
Comment · 5 years ago
Yes it will have to do that. Some packages .npmignore the source files so those may not even be present.

But doing that is actually easier than having to deal with all the different ways of versioning packages. For example, I am not using git tags in my project, some others may be, some may be using a branch not named `master` to deploy from. They're going to have to intelligently traverse the git tree to draw meaningful conclusions.

Comment · 5 years ago
Comment · 5 years ago
Wishing you hadn't worked so hard on your deathbed in your 80s is something people say after they have already saved enough money to live out their post-career life.

When you're in your youth working, you have no idea what this number is and better to be safe than sorry. If the amount of work you need to do to get through life with your target level of comfort were "solvable", then people would do it. But capitalism is a world of exponential growth, decay, and unpredictability.

When all financial advisors stop padding the hell out of their client's target retirement date just to be safe, then we can say this regret is solely on the conscience of the person on their deathbed.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton