jjnoakes

15 ms·

151.
by jjnoakes 3y ago
I don't understand why the RSU basis adjustment isn't reported automatically. All of the information is available without my involvement...
152.
by jjnoakes 3y ago
The Makefile is going to be running external commands, no? So you still have the same problem (what are those external commands written in?) - whatever the answer to that question is, your task runner could be written in as well, probably.
153.
by jjnoakes 3y ago
I assume one could just use 'fn' and 'var' and 'let' and get all the nice benefits of the static-ness of those features in any kind of code.
154.
by jjnoakes 3y ago
Mojo is taking this approach. I think it's a good idea.
155.
by jjnoakes 3y ago
The point is that the part of mojo that is new allows you to write early bindings that can't change, immutable variables, values that are accessed without indirection, types, ownership annotations, etc, and uses all of that to do preci
156.
by jjnoakes 3y ago
There's a ton of middle ground though. It just didn't catch on as much. Unfortunately, ecosystem is still king.
157.
by jjnoakes 3y ago
Language evolves and it can't be contained. It's a fact of life.
158.
by jjnoakes 3y ago
I don't mean to pick on your comment specifically, but I really dislike the notion that someone who appreciates, prefers, or relies on static types and a more strict compiler or toolchain is somehow not a grown-up. [Edit]: Added a miss
159.
by jjnoakes 3y ago
Another happy Aegis user here adding my support for using it over alternatives.
160.
by jjnoakes 4y ago
Maybe, maybe not - but in my experience, a dumpster fire with static types is easier to read and understand and also easier to refactor.
161.
by jjnoakes 4y ago
Why can't you release features whenever you like under this model?
162.
by jjnoakes 4y ago
Yeah even though the moves are all the same in 4d space, some of them get complex in 3d space.
163.
by jjnoakes 4y ago
Why couldn't Google just count the file name length and perhaps a small constant metadata size against your quota?
164.
by jjnoakes 4y ago
A huge majority of folks wouldn't need to bother, and the rest could make changes if they are needed.
165.
by jjnoakes 4y ago
For example (continuing my sibling comment), if you unroll it properly, you do get TypeScript complaints. parseInt("10", 0, ["10", "10", "10"]) parseInt("10", 1, ["10", &quot
166.
by jjnoakes 4y ago
I disagree that the code is "correct". TypeScript warns for passing too many arguments to functions in other contexts even though that could also be called "correct" because even though it works, it was probably unintent
167.
by jjnoakes 4y ago
Map passes three arguments to parseInt but parseInt only takes two. I think a language with a type system ought to have a way to get a warning for that kind of thing. Especially when it does so in other contexts. I understand why it is this
168.
by jjnoakes 4y ago
TypeScript has its own WATs too, and to me they are almost worse, because you have this false sense of security based on it being TypeScript and not JavaScript. https://www.typescriptlang.org/play?#code/MYewdgziA2CmB00Q
169.
by jjnoakes 4y ago
...and is more recently making great inroads into places where garbage collectors (and other features of those popular languages) aren't desired.
170.
by jjnoakes 4y ago
I'm not so sure. If developers and testers and QA teams can spend less time on a class of issues, I imagine they'll have more time to spend on the other classes of issues, lowering their exploitability as well.
171.
by jjnoakes 4y ago
Does the outcome justify the risk if the outcome could have gone radically differently? Is driving without a seatbelt not a poor decision if one walks away from the wreck?
172.
by jjnoakes 4y ago
The most recent example I debugged for a colleague was a container of callbacks, and one of them ended up changing the container while it was being iterated over. Nothing crazy, just no easy way that we were aware of to catch that kind of t
173.
by jjnoakes 4y ago
Do you have any large open source code bases that you could share?
174.
by jjnoakes 4y ago
> I think it's mutual responsibility on both API provider and user to engage in communication before mixing parts And I think it is the responsibility of the type system to at least catch if I'm passing too many arguments to a
175.
by jjnoakes 4y ago
TypeScript flags when I call a function that takes two parameters max with three arguments as an issue in many contexts, but not in contexts like this. I understand why they chose to do this, but I reach for better type systems any time I h
176.
by jjnoakes 4y ago
When I see things like this I have a visceral reaction that I just can't get over. https://www.typescriptlang.org/play#code/MYewdgziA2CmB00QHMA...
177.
by jjnoakes 4y ago
Agreed. If this was a truly remote position permanently, I'd apply right now and take a pay cut. I'm at the point in my career where social impact at this scale would be a higher priority than pay for me. But remote is the highest
178.
by jjnoakes 4y ago
A panic (deterministic, guaranteed, immediate, and worst-case a dos) is an order of magnitude better than memory corruption (non-deterministic, not guaranteed, eventual-if-at-all, and worst-case-rce).
179.
by jjnoakes 4y ago
I think I would love an ML-like language built on the go runtime and standard library and ecosystem.
180.
by jjnoakes 4y ago
> How would you change the Type System to fix this particular issue? In TS you really can't (that's my point and why I prefer to avoid the language) because of JS and API baggage. But just about every other static language that

More ›