HNHacker News
TopNewBestAskShowJobs

wycy

1,504 karma · joined November 6, 2017

submissionscomments
wycy··on Blub Paradox (2014)
> not because they are inherently easier to understand

I'm honestly not sure that that's true. I would bet money that someone who primarily works in Lisp would still have an easier time sitting down and reading Python code than someone who works in Python sitting down and reading Lisp, because I think it might truly be inherently easier to understand.

There is intrinsic meaning in:

    x = 5
    let x = 5
etc., insofar as these translate character for character, word for word, into human language, whereas this simply doesn't:

    (let (x 5))
wycy··on Record Numbers of Americans Want to Leave the U.S
This does not imply that at all.
wycy··on Pathfinding for Tower Defense
Yeah, my day 15 part 2 is still somewhat bugged. At termination, I print out 6 possible answers, each of which represents an off-by-one error. My correct answer is fortunately one of these: its the round * (elves HP + 3), which indicates that my elves sustain one too many attacks before the game ends. I still have no idea where this extra attack is coming in, but I’ve basically given up on perfecting my day 15 code. It was incredibly frustrating.
wycy··on Pathfinding for Tower Defense
This would’ve been a handy article to have read before/during Advent of Code 2018. There were multiple path finding problems I struggled through.
wycy··on Essential C (2003) [pdf]
While this is a common idiom, I do think it is bad from a maintainability standpoint. Let’s say in the future you need to change make a change, and the value of a becomes the elemental sum of the vectors b and c.

    a = b[i++] + c[i++]
Errors like this are more avoidable by avoiding this sort of syntactical compression.

    a = b[i] + c[i]
    i += 1
wycy··on What I learned from reading a thousand emergency room bills
From what I understand (which is honestly not much), I think in cases like this you can contact the hospital and just insist on paying the same amount your insurance would have paid, and they'll often take it. That's just what I hear, though.
wycy··on Reasons Python Sucks
I frequently have to when copy/pasting code in VS Code and it assumes the wrong indentation level.
wycy··on Glitter bomb tricks parcel thieves
It does seem like our package receiving system needs updating in light of the huge rise in package deliveries. Maybe it's time everyone should have a large package delivery box similar to a mailbox where packages can be securely deposited out of view.
wycy··on Google's 'two-tier' workforce training document
Exactly. If you go to work every day at Google, you work at Google. It is unfortunate that laws don't reflect that, but of course if they did, companies would find loopholes. If working every day at Google were legally defined such that you work for Google, perhaps contractors would simply be forced to rotate between workplaces weekly to skirt these definitions.
wycy··on Using Zig to Provide Stack Traces on Kernel Panic for a Bare Bones OS
I really like the look of Zig syntax so far. I had wanted to use this year's Advent of Code contest as an opportunity to learn some Zig, but I had trouble getting the compiler compiled and working.

I see now that binaries are available (maybe they always were?)--maybe it's time to put Zig to the test on these toy problems.

wycy··on Firefox desktop market share now below 9%
I switched from Firefox to Chrome around 2009. I switched back to Firefox this year with the release of Quantum. Its performance has seemed fine to me even on my late 2012 iMac.

I think the switch back to Firefox was worth it if only for the privacy and to claw back some control from Google.

wycy··on U.S. Life Expectancy Falls Further
That's not my takeaway from Figure 5. The curve for "Non-Hispanic white male" seems to be dipping downward since 2014, and "non-Hispanic white female" appears to either also be decreasing or at best flatlining.
wycy··on Fortran is still a thing
Modern code often does, but I still see a lot of retro FORTRAN that maddeningly relies on implicits.
wycy··on Fortran is still a thing
That column of GOTOs in EMPIRE.FOR. That is the stuff of nightmares.

EDIT- Terrifying:

251 GOTO (21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37) I-20

wycy··on Fortran is still a thing
From what I gather, fixed columns was all FORTRAN versions up to F77, since Wikipedia says free format was introduced in Fortran 90 [0]. But it may have been the case perhaps that some compilers supported proprietary directives to support this in earlier versions--I wouldn't know, though.

[0] https://en.wikipedia.org/wiki/Fortran#Fortran_90

wycy··on Fortran is still a thing
Interesting, I've never seen this before. Seems like it would be easy enough for me to add this as an alternate means of initialization.
wycy··on Fortran is still a thing
I gather that gfortran can be built on Android, so presumably it's possible. I see conflicting information on whether or not it's actually possible on iOS. I've personally never seen it.
wycy··on Fortran is still a thing
The rationale was based primarily on 2 factors:

(1) Compatibility with legacy FORTRAN. Although it's not difficult to work with legacy FORTRAN via C, it's seamless to pass data around between legacy FORTRAN and Modern Fortran.

(2) The mathematical and array syntax. It's tough to beat Fortran's mathematical notation and easy use of multidimensional arrays.

wycy··on Fortran is still a thing
I believe free format came about in Fortran 90, and that FORTRAN 77 was still fixed format--at least that's what a quick Google suggests. But even still, fixed-format F77 has stuck around in lots of legacy code bases for a long time. We only migrated one of our large codebases to free format a few months ago.
wycy··on Fortran is still a thing
I'm actively working on multiple Fortran projects, including one that's being written from scratch just in the last year in modern Fortran 2018.

Modern Fortran looks completely different from the old school FORTRAN77 most people probably imagine. Gone are the days of fixed-format, where the columns actually mattered, and gone are the days of unreadable ALL CAPITAL LETTERS, and gone are the days of GOTO.

I developed a Fortran implementation of Python's argparse[0] recently to use for another project. The code is nothing like the monstrous spaghetti code of days past---although I do still obsessively line up my code in columns, this isn't important.

[0] https://gitlab.com/bwearley/f-clap

wycy··on The greatest sales deck I've ever seen (2016)
In what way is that a picture of legs? It'd be more accurate to describe it as a picture of a door.
wycy··on I Found the Best Burger Place in America, Then I Killed It
The high prices would be to ward off these one-time customers who are only there for the single instagram photo. If someone is invested enough to make a fake ID just for cheaper burgers, presumably they're going to be repeat customers that develop a relationship with the restaurant, which is what he wants.
wycy··on Kessler Syndrome
Kessler syndrome is why it was so irresponsible of the Chinese to blow up a satellite just to prove that they could.

* https://en.wikipedia.org/wiki/2007_Chinese_anti-satellite_mi...

wycy··on While iPhone sales remain stagnant, Apple services hit $10B in revenue
Out of curiosity, what do you use Siri for that it can be good enough?

I use Siri almost exclusively for reminders (e.g., "remind me at x PM to do y" or "remind me when I get home to do z"), and even with this limited use case I often end up with baffling reminders in the future (my favorite reminder is to "make farts"--I never did remember what it was supposed to be.) Beyond reminders I've yet to find a compelling, reliable use case.

wycy··on Not Lisp again (2009)
Serious question: what is it about the "beauty" of Lisp that the HN community seems to like so much? To me, how Lisp looks is its worst quality--the number of parentheses is just mind boggling. I want to understand why it is so loved.
wycy··on Apple and Samsung fined for deliberately slowing down phones
The linked MacRumors thread is from before this scandal even came to light, while Apple was still throttling. The thread begins in 2016 and ends in 2017. iOS 11.3 came out March 2018, removing the throttle.

Unfortunately I can't check the reddit thread at the moment, as its blocked at work.

EDIT: Reddit thread is also from prior to lifting the throttle.

wycy··on Apple and Samsung fined for deliberately slowing down phones
That argument could possibly be made for iOS 12, but not for iOS 11.3.
wycy··on Apple and Samsung fined for deliberately slowing down phones
Recent iOS updates turned off the throttling of phones with old batteries. Apple initially said this throttling was necessary to prevent unexpected shutdowns of older phones. Now that the throttling is gone, have we seen a rash of unexpected shutdowns?

I haven't heard of this happening, which leads me to believe the excuse was bs in the first place.

EDIT: To be clear, I know that iPhones have always been known to unexpectedly shut down. Throttling performance was ostensibly meant to prevent these unexpected shutdowns. My question is whether or not the incidence of unexpected shutdowns increased once Apple lifted the throttle.

wycy··on Apple and Samsung fined for deliberately slowing down phones
>It turns out that "high demand" scenarios that cause the phone to crash can be triggered by mundane actions like taking photos. If you disallow throttling by law, old devices will just crash all the time.

This was what Apple apologists said when this issue first came to light, but hasn't Apple already shot its own excuse in the foot? iOS 11.3/12.0 came out, removing the throttles, and I haven't seen anything about a rash of phones all constantly shutting off now.

wycy··on iPhones are hard to use
With the new FaceID features, I could see it being a nice touch if iOS were to ask users if they want to increase text size if it senses the user always holds the phone ridiculously close to their face and/or constantly squints.

Beyond that, I don't know how much of a responsibility it is for the phone to push its accessibility options on everyone after initial setup.

← PreviousPage 13 of 16Next →