jcparkyn

20 ms·

181.
by jcparkyn 4y ago
> Using a debugger is much too slow. This varies, but in a lot of environments, using a debugger is much _faster_ than adding a print statement and recompiling (then removing the print statement). Especially when you're trying to lo
182.
by jcparkyn 4y ago
I'm pretty sure it's been faster for as long as it's existed.
183.
by jcparkyn 4y ago
Brazil is an internal tool used at Amazon.
184.
by jcparkyn 4y ago
> it's not dead; it's just really stable. Am I the only one who thinks this idea is somewhat contradicted by the TODOs that are still in the official docs, and seem to have been for years?
185.
by jcparkyn 4y ago
> Research of A/B experiments carried out independently by multiple companies suggests that, at best, 1 in 3 ideas will have any measurable impact, and the industry average is likely 1 in 7 (14%). Everything else either has no impa
186.
by jcparkyn 4y ago
Buying a lottery ticket is a choice.
187.
by jcparkyn 4y ago
> least verbose language I have ever seen You'd love APL.
188.
by jcparkyn 4y ago
Probably because you'd want to access the value in either case, depending on your application.
189.
by jcparkyn 4y ago
> NaN's are already an option type, although implemented in hardware The compromise with this is that it makes it impossible to represent a non-optional float, which leads to the same issues as null pointers in c++/java/
190.
by jcparkyn 4y ago
I'm not sure I follow. How does that relate to my comment?
191.
by jcparkyn 4y ago
They can pay you lots of money to buy it off you, and then do what they want with it. Great for you, but (potentially) bad for all the prospective users. It also might be bad for all the users who would have kept using Google either way, si
192.
by jcparkyn 4y ago
> type hints are too much clutter. Any sufficiently detailed python docstring contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of a type annotation.
193.
by jcparkyn 4y ago
Imagine how much worse those structs with pointers to structs would be without static typing though. This feels like a complaint against C, not a complaint against static types.
194.
by jcparkyn 4y ago
It makes generics and higher-order functions much more elegant. Any function of `(a->t)->t`(or many other similar signatures) will automatically be able to return the correct error type if t is a Result<>. Compare this to checke
195.
by jcparkyn 4y ago
If you haven't tried micro-cap, I'd recommend checking it out. It became free a few years ago when the company liquidated, and it's orders of magnitude more powerful than LTspice (and quite a bit more intuitive, but still not
196.
by jcparkyn 4y ago
As someone who has done "ethics training" as part of an engineering degree, I don't believe for a second that it has a significant impact on the choices most engineers would make in their jobs. Sure it helps to have establish
197.
by jcparkyn 4y ago
I would also suggest increasing the spacing around the comma and [ characters (and probably others that aren't shown in that screenshot). I find that non-monospaced fonts make it hard to see where the cursor is in those situations, bec
198.
by jcparkyn 4y ago
I guess because it would be a total pain for humans to read and write without specialised tooling. Imagine trying to add a word at the start of your document.
199.
by jcparkyn 4y ago
I think it would be reasonable to also have overflowing and checked versions of the operators, for cases where the compiler can't guarantee the size (e.g. mutable variables in loops).
200.
by jcparkyn 4y ago
Bonus tip: set `display: block` on a style tag and add `contenteditable`, then users can even edit your page styles in real-time.
201.
by jcparkyn 4y ago
> feel free to chime in Pun intended?
202.
by jcparkyn 4y ago
Since no-one else in the comments seems to have pointed this out, I'm pretty sure these are all examples from real apps, which is how they're deciding which is correct. It's not so much about choosing the "better" d
203.
by jcparkyn 4y ago
Yeah that qualification helps a lot.
204.
by jcparkyn 4y ago
That logic (your last paragraph) essentially assumes that people only care for selfish reasons. Plenty of people contribute for the sake of giving back to the project (by e.g. taking the time to write a high-quality bug report or PR).
205.
by jcparkyn 4y ago
I'm not saying I think the maintainers have any obligation to do things for me (I tried to make that clear in the original comment). What I was really trying to say is that I don't think this model would apply well to most project
206.
by jcparkyn 4y ago
I totally agree for things that would normally be described as support (e.g. feature requests or low quality bug reports), but a lot of things aren't that. Personally, if I submit a bug report or PR to an OSS project (which admittedly
207.
by jcparkyn 4y ago
I'm not sure how I feel about this one. Sure, the maintainers have no obligation to review and merge other people's PRs. But when this also applies to genuine high-quality community contributions, I feel like there must be some ne
208.
by jcparkyn 4y ago
> Tabs are simply inferior to spaces... I think you wrote this the wrong way around?
209.
by jcparkyn 4y ago
Out of curiosity, do TryStartNoGCRegion and/or GCLatencyMode.SustainedLowLatency not meet your needs?
210.
by jcparkyn 4y ago
I don't use zig, but it seems to me that functions can choose exactly which type of allocator they want to accept (just by changing the type of the allocator parameter), making his point invalid.

More ›