STRML

Joined 14 years ago

Karma
3,275
Submissions
599
Member since
Sep 2
Hey, I'm Sam. I'm a frequent contributor to open source, including a number of React projects and Babel core.

strml.net github.com/STRML bitmex.com securesha.re

[ my public key: https://keybase.io/strml; my proof: https://keybase.io/strml/sigs/Rr2YKiZGMMOgxiMMcgqAy5aykMgj0OxJamVQAZkQ0iE ]

View on Hacker News

Recent submissions

Comment · 1 year ago
Watch your power usage. With large windowed VSCode or Cursor, you will see far higher CPU and GPU usage by WindowServer and more system power consumption. It’s easier if you track it with stats.app.
Comment · 1 year ago
Comment · 1 year ago
Arguably, especially in the 8/10/11 era, few of these features are things that meaningfully enhance the user experience. Incredibly, we're still running NTFS and dealing with hacks on hacks on hacks. In the 8 era, a huge number of massive projects were started, promoted, and mothballed.
Comment · 2 years ago
Comment · 3 years ago
Does lead exposure have a "horrifying" story? It has measurable effects over years and decades, but very little acute effect.
Comment · 3 years ago
100%. Flow always had some great safety features and some complex type combinators. But the churn in the project and lack of non-FB participation made it hard to recommend.
Comment · 3 years ago
Flowtype works like this out of the box. In my opinion, it's a much better default.
Comment · 3 years ago
Your comment is mostly on point, but the download speeds are way off. By the time Flash was really getting big, everyone was on 56k, (rarely) ISDN, or ~1mbps broadband of one type or another. But even with 56k, you're getting 5kBps. So a 45-100kB download was 20sec at most, and 500kB was about 2 minutes.

That said vector graphics and extreme sound compression was just how shit got done. In those days gaming and entertainment online was all about CD deployment, extreme delta patching, low bit rate audio (Teamspeak et al) and vector graphics when possible.

I miss those days. On top of it not yet being spoiled by billion dollar businesses, the extreme constraints meant that creative minds could excel far above and beyond corporate types. And that's why the internet had the reputation it did. The ones who were making waves were individuals and small development houses that were founder-driven. It's nothing like today.

Comment · 3 years ago
This is good advice, although it made me chuckle a bit that he in fact recommends removing years entirely, but then still has (c) 2021 on the footer.

I'm always in favor of removing lawyer boilerplate though.

Comment · 3 years ago
You'd be surprised, on a solid connection the input latency is incredibly good
Comment · 3 years ago
We have a unique one: back before the z1d launched, we had a critical system that was very single-threaded and its performance drove revenue in an extremely direct way.

So we were, deep in the shit, fighting fires due to our systems being in a perpetual state of DoS, and we asked if they would rack a machine with a certain overclocked Skylake chip in it. We offered 7 figures to do it. It was worth that much to us to get ~40% more capacity without having to migrate off AWS. They said no :)

Comment · 3 years ago
https://docs.yubico.com/yesdk/users-manual/application-otp/s...

It's a nice option, but of course you need to back up this static pw somewhere or program a bunch of keys with it.

Comment · 4 years ago
It shouldn't work this way. Customer funds should be segregated from whatever prop trading the rest of the business is doing.

The only way this happens is if the prop trading business is over-leveraged somehow and the exchange bailed it out with FTT.

Customer deposits should meet liabilities 1:1. If they don't, somebody is lying.

Comment · 4 years ago
There are multiple tells that this move, just like the removal of radar, is supply-chain and cost-driven and not actually driven by engineering.

If this were a planned move, the software would already be ready to replace it. It is not. Cars without radar still aren't at parity with the car that have it, although they "fixed" this a few weeks back by simply turning off the radar on the older cars.

The parking sensors on the Tesla are really good and very useful. They show a rough outline of what is around you and are displayed very nicely compared to some other cars. It is a real shame to remove this, and downright dishonest to characterize it as some kind of leap forward.

The cheapest bargain-bin cars have this feature. Your $100k+ Model S or X will not.

Even more concerning: some features simply cannot be replaced by camera. Tesla infamously does not have a front bumper camera, making it impossible to detect obstructions occluded from view by the hood. For 3/S, which are low, this means it will be impossible to detect low obstructions like too-high concrete wheel stops and similar obstructions. Once the hood has occluded the view from the windshield cameras, these obstructions will cease to exist.

Laughable that this is being done on cars from a high-end brand, and that the remedy for customers who are getting worse cars today than you would get yesterday is to wait for these features to "be restored" at some indeterminate time in the future.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton