brundolf

51 ms·

781.
by brundolf 4y ago
Yeah that makes sense too
782.
by brundolf 4y ago
Apple's trade-in prices have always been lowballed, but they aren't normally this extreme. Usually you get just enough that you might choose to take the loss instead of dealing with Ebay or something But I wouldn't be surpr
783.
by brundolf 4y ago
Firing a bunch of people impacts morale, PR, etc. So there may be a bunch of people they'd like to fire but not badly enough to deal with those consequences. But a public narrative of "it's the economy" or "layoff
784.
by brundolf 4y ago
Until very recently, MacBooks were famously stuck with 720p webcams. So from that perspective 1080p is a feature worth mentioning In any case, I personally don't really care how much fine detail my friends and coworkers can see when I&
785.
by brundolf 4y ago
If you're moving a terabyte of music to the device from your computer where it lives, that could matter
786.
by brundolf 4y ago
I'm sure this appeals to a market segment: > Anyway, back to this $800 model. Unlike regular phone equipment, this has a proper audio amplifier with big, beefy capacitors to power the analog audio output. That makes it much bigger t
787.
by brundolf 4y ago
The transfer speeds wouldn't be as good as a built-in SSD though, right? Maybe that's just not a big enough deal to matter?
788.
by brundolf 4y ago
It's bizarre to only have 32GB/64GB storage. I remember getting a dedicated music player with 80GB in 2008 . Bulk storage seems like it would be one of the few good ways to differentiate these from a smartphone Maybe I'm jus
789.
by brundolf 4y ago
I don't have firsthand knowledge, but based on their product I get the feeling Discord must have an amazing dev culture
790.
Ask HN: Are you glad you're using Material UI (React library)?
1 points by brundolf 4y ago|0 comments
791.
by brundolf 4y ago
Totally disagree. Trying to fully understand a stack this tall from the get-go would be a huge barrier One of the best things about Next is that it configures everything for you and lets you just start writing some React code and seeing res
792.
by brundolf 4y ago
The native <dialog> does very little on its own in terms of functionality. It's mainly there for accessibility/semantic markup
793.
by brundolf 4y ago
Sure, that can happen. I guess I feel like if it's that much of a problem for any given library, you always have various ways of disabling checks where you need to and still benefiting from them elsewhere. So it's still a net be
794.
by brundolf 4y ago
> many useful and popular libraries do not include full documentation of their types > but many authors choose to show their examples in JS, in order not to be too opinionated This is certainly true sometimes, but I don't see why
795.
by brundolf 4y ago
Unit tests only trace one path at a time; static types cover huge possibility-spaces at once. But of course there are things they can't reason about, which is why we still test, but each of the two is better for catching different kind
796.
by brundolf 4y ago
> you’re better off just starting with typescript It depends. The tooling is still a barrier (even though it's gotten smaller); the cost is small for a real project, but for someone who's learning and knows nothing about the ec
797.
by brundolf 4y ago
I don't have a lot to add except that my experience with it has been very positive; your complaints are mostly valid, but for me those pain points disappear in the shadow of all the things I no longer have to spend time stressing about
798.
by brundolf 4y ago
> Vulkan is so painfully verbose in unnecessary ways, forcing you to be explicit about everything It's my understanding that Vulkan (like Metal) has fundamentally different goals than OpenGL OpenGL is like if the lowest-level progra
799.
by brundolf 4y ago
I don't think there's a binary between "totally open, general-purpose language across all platforms" and "closed-source/proprietary". Even if Swift remains a decidedly Apple language, developers can still
800.
by brundolf 4y ago
I've had this happen while under a flex/unlimited policy. It all depends on the company and the manager
801.
by brundolf 4y ago
To add to the anecdotes, I've never felt pressured by any of my employers (explicitly or implicitly) to talk publicly about them on social media, my blog, or anything else. I would feel pretty weird if that happened, especially on a re
802.
by brundolf 4y ago
Something to be careful about here is that browsers/proxies/etc have arbitrary length limits on URLs, and they can vary by quite a lot We did this once with a web-based REPL, where you could click a button to copy a link to someth
803.
by brundolf 4y ago
Many companies have a dedicated technical track that runs in parallel with the management track, specifically for cases like yours (which are very common) You could suggest adopting that kind of structure at your current company? Or otherwi
804.
by brundolf 4y ago
Sure, fair. I guess in my head I meant "only modern ecosystem" and/or "only major ecosystem that gets used in web development"
805.
by brundolf 4y ago
You can face the diamond problem in NPM, it just deals with it internally (usually by installing both versions under node_modules). But I don't see that as related to whether dependencies are project-specific or system-wide
806.
by brundolf 4y ago
A key thing for Node is that NPM (in addition to being first-party and having a standard manifest format) installs all dependencies in the project directory, under node_modules People complain about node_modules, but the benefit is that e
807.
by brundolf 4y ago
Thinking about how python is the only ecosystem where you need to deal with any of this, and how many thousands of developer-hours are spent on it
808.
by brundolf 4y ago
tsc does that, but yes, you'd still have to run tsc which was part of my original point
809.
by brundolf 4y ago
> there's no way to run a build/compile step for running 'javascript' to catch these type errors before runtime I don't think I follow what you mean here, can you clarify?
810.
by brundolf 4y ago
I say this as a huge proponent of TypeScript and static types in general: I'm fairly bearish on this proposal 1) TypeScript supports a huge set of syntax for describing types, and I would be surprised if the standard ever supports all

More ›