HNHacker News
TopNewBestAskShowJobs

EddieRingle

1,438 karma · joined January 16, 2012

I like learning new things, making new things, and improving not-so-new things. Primary focus is on Android/Kotlin, but I have experience with C/C++, Go, OpenGL, etc.

Happy to talk - eddie [at] ringle [dot] io

[ my public key: https://keybase.io/eddieringle; my proof: https://keybase.io/eddieringle/sigs/QZtW0oYTMUR988YYBQpB7Mqfg775MsU3GCBvTTVaYX0 ]

submissionscomments
EddieRingle··on The Google Memo: Four Scientists Respond
The top sentence is followed by three full paragraphs you clipped out. Only then do we reach the bottom statement you've quoted, albeit in the source is prefaced with the following:

> Now, treating people as dichotomous sexes is exactly what many affirmative action policies do. As this is not my area of expertise, I can only offer my non-expert opinion on this issue, which is this: There have been (and likely will continue to be) many socio-structural barriers to women working in technological jobs. ...

EddieRingle··on On managing outrage in Silicon Valley
Thanks! However after looking through the slide deck, it seems that the author tries to argue that because mathematic ability isn't so important in CS, biological differences can't explain the disparity between the men and women in CS. That's a quite a leap, I think.

If CS doesn't involve a lot of math, what does it involve that might be impacted by biological or psychological causes?

(P.S. I went to a STEM high school and I know plenty of women who are absolutely stellar in mathematics and science, so I know that's not the issue here.)

EddieRingle··on On managing outrage in Silicon Valley
There were quite a few Medium posts as well. But no, I completely agree with you. I've discussed with others recently about how I'd love to have a tool or place where I can search for a given assertion and see the (scientific) evidence for and against it, as well as related assertions and opposing assertions.

And I'm not just talking about being able to "Google it". If I use Google or a general search engine then I have to wade through who knows how many links of ambiguous quality and/or bias.

EddieRingle··on On managing outrage in Silicon Valley
One of my first exposures to this "manifesto" was on Twitter with someone starting a thread with "Google has a Nazi problem." The majority of the other responses I read either attacked the author, dismissed the entire text in whole, and/or refused to actually argue the paper's points because they saw them as so ridiculous or "obviously" wrong.

I read the paper. I don't see at all how it relates to fascism, Trumpism, or whatever you want to call it.

I am against discrimination, and that includes positive discrimination.

If there were factual inaccuracies in what the author wrote, why not discuss them? Why not use high-quality sources to validate your argument? I wish it was the opposite, but I don't have the time to research the psychological/sociological perspectives on these issues. Human civilization has grown thanks to being able to specialize. I specialize and (hopefully) make contributions in one field, but I depend on others that have specialized elsewhere to provide knowledge and resources I can depend on.

EddieRingle··on Google employee anti-diversity memo causes row
Honest question: is the goal really to have a 50/50 split of men and women employed in the field? Because that's the general sense I get when the existing distribution numbers are cited. If so, why is that the goal?

And why is positive discrimination justified? Why not lift all the fingers off the scales and see where things end up?

EddieRingle··on Apple has proven me wrong about HomeKit
I don't have a coffee maker, but I just tried this with my Philips Hue lights and it was able to get the right state even after I turned the lights off manually through the Hue app.
EddieRingle··on Inside Patreon, the economic engine of internet culture
What happens when sensible humans are no longer at the helm?
EddieRingle··on Contributors Summit – The Go Blog

    To make critical fixes to packages in the standard
    library, one must wait 6 months for a new version
    of Go to ship (or a point release has to be shipped
    in the case of security issues, which drains
    team resources).
I realize the article suggests breaking more functionality out into external projects to get around this, but I'll also advocate for a shorter release cycle. 6 weeks makes more sense than 6 months, IMO. I'd be curious to hear arguments for the long cycles though, as so far I haven't been convinced.
EddieRingle··on Khronos Releases OpenGL 4.6 with SPIR-V Support
I posted the announcement via Phoronix here: https://news.ycombinator.com/item?id=14892967

But this one is probably better as it's coming from Khronos directly.

EddieRingle··on Pik – a new lossy image format for the internet
In addition to what other replies stated, you can read Google's documentation on how open source projects (official and unofficial are released) here: https://opensource.google.com/docs/
EddieRingle··on Raneto – Markdown Knowledgebase Platform
Why something like this instead of—for instance—a wiki?
EddieRingle··on How a VC-funded company is undermining the open-source community
> I think this issue deserves a more thorough response because there are a lot of misrepresentations in the article.

From the article:

> Smith also said that most of the negative reaction was due to confusion around what the tools actually do. (Connor pointed out that it’s not possible to review what Kite does, since it itself is not open source.) Then he blew this reporter off. “I apologize in advance that I can't answer any further questions,” he wrote. “I need to focus on other parts of the business, including continuing to improve the product for our users, and conflict like this is always doubly distracting.”

The above sounds like you were given the opportunity to explain things but shrugged it off as a distraction.

If it deserves a more thorough response, why hasn't that been given? Even in this reply you only "quickly highlight" one point.

EddieRingle··on Toward Go 2

    > To minimize disruption, each change will require
    > careful thought, planning, and tooling, which in
    > turn limits the number of changes we can make.
    > Maybe we can do two or three, certainly not more than five.

    > ... I'm focusing today on possible major changes,
    > such as additional support for error handling, or
    > introducing immutable or read-only values, or adding
    > some form of generics, or other important topics
    > not yet suggested. We can do only a few of those
    > major changes. We will have to choose carefully.
This makes very little sense to me. If you _finally_ have the opportunity to break backwards-compatibility, just do it. Especially if, as he mentions earlier, they want to build tools to ease the transition from 1 to 2.

    > Once all the backwards-compatible work is done,
    > say in Go 1.20, then we can make the backwards-
    > incompatible changes in Go 2.0. If there turn out
    > to be no backwards-incompatible changes, maybe we
    > just declare that Go 1.20 is Go 2.0. Either way,
    > at that point we will transition from working on
    > the Go 1.X release sequence to working on the
    > Go 2.X sequence, perhaps with an extended support
    > window for the final Go 1.X release.
If there aren't any backwards-incompatible changes, why call it Go 2? Why confuse anyone?

---

Additionally, I'm of the opinion that more projects should adopt faster release cycles. The Linux kernel has a new release roughly every ~7-8 weeks. GitLab releases monthly. This allows a tight, quick iterate-and-feedback loop.

Set a timetable, and cut a release with whatever is ready at the time. If there are concerns of stability, you could do separate LTS releases. Two releases per year is far too short, I feel. Besides, isn't the whole idea of Go to go fast?

EddieRingle··on Go 2 announced at Gophercon
I posted this earlier: https://news.ycombinator.com/item?id=14762299
EddieRingle··on Russ Cox announces plans for Go 2
I posted this earlier: https://news.ycombinator.com/item?id=14762299
EddieRingle··on What’s Next for Gitlab CI: Auto DevOps
> I think we use toml for the Runner since it is written in Go and should be deployed on another server.

Couldn't you just parse YAML in Go, or TOML in Ruby? (Or why not give the option of multiple formats?)

EddieRingle··on Introducing code owners
I was sort of hoping this would determine code ownership based on who wrote the lines being modified in the patch. This solution is simple and still useful, though.
EddieRingle··on Antisocial Coding: My Year at GitHub
> "I was well aware of GitHub's very problematic past, from its promotion of meritocracy in place of a management system"

I don't see what's wrong with meritocracy as opposed to an unspecified "management system".

--

> Feature releases such as these are frequently promoted on the GitHub blog, and the product manager on my team encouraged me to write a post announcing what I had shipped. Since it was so important to me personally, I wrote an impassioned piece talking about how this feature closed a security gap that had directly affected and provided an abuse vector against me. The post also served as an announcement to the world of the new team and the kinds of problems that we were charged with solving.

>

> The post was submitted for editorial review. It was decided that the tone of what I had written was too personal and didn't reflect the voice of the company. The reviewer insisted that any mention of the abuse vector that this feature was closing be removed. In the midst of my discussions with the editorial team, trying to reach a compromise, a (male) engineer from another team completely rewrote the blog post and published it without talking to me.

GitHub was correct here. Feature announcements on the company blog should remain neutral in tone. In addition, the published feature announcement seems to mention the motivations behind the feature quite well:

> Previously, anyone could automatically add other developers to their repositories without explicit permission. This model openly provided some users with opportunities to harass members of our community by inviting them to offensive or attention-seeking repositories.

So, it was rewritten to a neutral explanation of why this feature is a benefit to those who have had experiences like that of the author.

--

> In addition to my development work, I had started weekly mentoring sessions with one of my teammates (a recent boot camp graduate) on Ruby and Rails fundamentals that she had not been exposed to in her program. When I talked to my manager about how she was progressing, I was told to stop the formal mentoring and allow this person to "learn at her own pace, without any pressure from you." I was mystified: mentoring is an essential part of being a senior engineer, and this teammate seemed to be benefiting from it.

No quote was given from the manager telling the author to stop mentoring entirely, just that they wanted the _formal_ mentoring to stop (by formal, I assume it to mean it was initiated by the author, not the student). It's possible the manager's intention was as quoted: to see how this "recent boot camp graduate" was able to grow on her own.

--

> I was very disappointed at this 101 mistake, and sadly opened an issue referencing the question.

This has a presumptuous tone to it.

--

> The same day that I had this review, I got some devastating personal news. I have bipolar depression and was already in a bad place mentally, so I found myself feeling crushed and hopeless. In an attempt to deal with things I ended up taking a dangerously high dose of my anti-anxiety medication. When I reached out to my therapist for help, she recommended that I go to the emergency room. This was the start of an eight day ordeal involving involuntary commitment to a mental health facility. I shared this experience on Twitter and won't rehash it here, but suffice it to say that I was severely traumatized by what happened to me in the hospital.

I read the "experience on Twitter". It sounds to me that the author's judgement was impaired (re: the author's self-described overdose of anti-anxiety medication) and the hospital/psychiatrist believed they were enough of a risk to themselves to warrant admitting them as a patient.

--

> Thursday and Friday were not good days. I had a lot of trouble focusing. I was making simple mistakes and in some cases doing the wrong work. Friday afternoon I reached out to my boss to tell her that I was having trouble and that I didn't know what to do. She suggested that I take medical leave, but I told her what my therapist had said about the importance of getting back to normal life. My manager was adamant that if I couldn't work at full capacity that I had no choice but to take medical leave.

> ...

> The following week I had scheduled conferences to attend, so my focus on work was put on hold.

> ...

> After the meeting I messaged her and shared the more personal aspects of what I was going through, the trauma that I had experienced in the hospital and its lingering effects on my mental health. I was told that I should have accepted the offer of medical leave, and she said she felt like I was trying to manipulate her by sharing my feelings in the hopes of influencing the PIP. I was dismayed.

The author "had a lot of trouble focusing". It was recommended multiple times that she take medical leave. Instead, the author's "focus on work was put on hold" in order to attend conferences. I'm as suspicious of PIPs as much as the next person, but this seems pretty cut-and-dry to me as unsatisfactory work performance.

--

Regarding the firing on grounds of lack of empathetic communication, perhaps it was related to why this person was hired in the first place?

> They wanted to offer me a job. They had just created a team called Community & Safety, charged with making GitHub more safe for marginalized people and creating features for project owners to better manage their communities.

--

> I think back on the lack of options I was given in response to my mental health situation and I see a complete lack of empathy.

As stated above, they provided the option of medical leave. The author chose not to take it.

> In the past several months GitHub has fired at least three transgender engineers and many more cisgender women.

Why were they fired? How many others were fired in the past several months? What's the ratio there?

> In a return to its meritocratic roots, the company has decided to move forward with a merit-based stock option program despite criticism from employees who tried to point out its inherent unfairness.

Again, what's unfair about rewarding based on merit? Should people who contribute relatively little compared to others get just as much reward? Why would the higher-performers bother to burden themselves in that case?

> So yes, in looking back over my year at GitHub I see that there was, in fact, a real problem with empathy.

>

> But that problem wasn't mine.

So in the end, the author seems to absolve themselves of responsibility. This shows a lack of growth; in my opinion you should _always_ try to fault yourself if you're going to fault others.

EddieRingle··on Pony: Combining safe memory sharing with Erlang-like actors
By the way, I run the https://reddit.com/r/ponylang subreddit. I mentioned it a long time ago on the mailing list trying to get someone from the Pony team to join as a moderator, but don't think it ever fully panned out. If anyone on the team is interested, feel free to PM me on Reddit.
EddieRingle··on Apple’s AR is closer to reality than Google’s
For a moment I was confused why Trello was being mentioned and this and the other reply are the only mentions of it on the page. Easy typo to make or autocomplete false-positive, I suppose.

I'm excited for Treble, personally. I'd like to slightly modify your statement to say that it's available for any device that supports it. Google Pixel and Pixel XL shipped with Nougat but they are using it to test the transition from a non-Treble system layer to a Treble-ized (?) one with Android O's release. So other OEMs could choose to support Treble on older devices, given that they meet the requirements and also have support from the BSP vendors like Qualcomm.

That said, I agree with you that it probably will still take some time before we see a huge impact, and it's a shame it's taken this long; better late than never, I suppose?

EddieRingle··on iPad Pro
> Tablets and phones don't count yet.

You've been able to develop on Android for years now. See AIDE (http://www.android-ide.com/) and Termux (https://termux.com/), for example.

EddieRingle··on First Rule of Google Fuchsia OS Is to Not to Talk About It
This looks to be plagiarized from Android Police.

http://www.androidpolice.com/2017/05/19/googles-dave-burke-f...

EDIT: And the submitter has only submitted links from this blog.

EddieRingle··on Treble: A modular base for Android
Nope, they've introduced a HIDL for defining hardware interfaces. See https://news.ycombinator.com/item?id=13928385 which I posted back in March.
EddieRingle··on Treble: A modular base for Android
I discovered this back in March. This is pretty exciting!

Now all we need is to have Google distribute the framework over the Play Store instead of relying on OTAs, and all will be right with the world.

https://news.ycombinator.com/item?id=13928385

EddieRingle··on Universal USB-C charging: How the dream is coming true
I haven't had any problems myself, yet. If you buy something USB-IF certified at least, you're fine.

From https://plus.google.com/+BensonLeung/posts/LQ5df94bERb:

> One trend I will highlight is that more cables are getting USB-IF certified compliant. In fact, I see a number of cables on Amazon that not only claim to be USB-IF certified, they list the TID (Test Identifier) assigned by USB-IF for the cable in the product description.

Also, as for

> There's already competing standards for fast charging over USB-C.

Not really. There are proprietary options, yes, but USB Power Delivery is THE standard. Google even strongly recommends OEMs not implement anything besides Power Delivery (https://source.android.com/compatibility/android-cdd#7_7_usb):

> * Type-C devices MUST detect 1.5A and 3.0A chargers per the Type-C resistor standard and it must detect changes in the advertisement.

> * Type-C devices also supporting USB host mode are STRONGLY RECOMMENDED to support Power Delivery for data and power role swapping.

> * Type-C devices SHOULD support Power Delivery for high-voltage charging and support for Alternate Modes such as display out.

> * Type-C devices are STRONGLY RECOMMENDED to not support proprietary charging methods that modify Vbus voltage beyond default levels, or alter sink/source roles as such may result in interoperability issues with the chargers or devices that support the standard USB Power Delivery methods. While this is called out as "STRONGLY RECOMMENDED", in future Android versions we might REQUIRE all type-C devices to support full interoperability with standard type-C chargers.

Were there issues early on? Yes. Will there be many issues going forward? I don't think so.

EddieRingle··on GNU bc ends 11-year beta test, releases 1.7
Unsure, but it broke compilation of the Linux kernel for me. (linux-mainline on Arch)
EddieRingle··on Developer Preview of Android O
I was curious so I took a look: It seems they're implementing a new system; there are shared libraries in /vendor/lib/hw on my Pixel running O that aren't there on my Pixel XL running 7.1.

  sailfish:/ $ ls /vendor/lib/hw                                                                                                                   
  android.hardware.audio.effect@2.0-impl.so        android.hardware.graphics.composer@2.1-impl.so  android.hardware.vibrator@1.0-impl.so  
  android.hardware.audio@2.0-impl.so               android.hardware.graphics.mapper@2.0-impl.so    android.hardware.vr@1.0-impl.so        
  android.hardware.boot@1.0-impl.so                android.hardware.keymaster@3.0-impl.so          flp.default.so                         
  android.hardware.camera.provider@2.4-impl.so     android.hardware.light@2.0-impl.so              gatekeeper.msm8996.so                  
  android.hardware.configstore@1.0-impl.so         android.hardware.memtrack@1.0-impl.so           keystore.msm8996.so                    
  android.hardware.contexthub@1.0-impl.so          android.hardware.nfc@1.0-impl.so                sensors.vl530l0.tof.so                 
  android.hardware.drm@1.0-impl.so                 android.hardware.power@1.0-impl.so              sound_trigger.primary.msm8996.so       
  android.hardware.gatekeeper@1.0-impl.so          android.hardware.sensors@1.0-impl.so            vulkan.msm8996.so                      
  android.hardware.gnss@1.0-impl.so                android.hardware.soundtrigger@2.0-impl.so       
  android.hardware.graphics.allocator@2.0-impl.so  android.hardware.thermal@1.0-impl.so
You can see some development in the AOSP repos (follow https://r.android.com) that supports this. For example, libhwbinder (https://android.googlesource.com/platform/system/libhwbinder...) looks to be an interface for talking with a /dev/hwbinder device, and the kernel seems to have been updated recently to support multiple Binder device instances. HAL interfaces are defined in HIDL, which looks to be implemented here: https://android.googlesource.com/platform/system/libhidl/+/m... (along with a separate hidl tool in another repo).
EddieRingle··on Saving Data: Reducing the Size of App Updates by 65%
That's no longer the case with Nougat. Apps are now interpreted with a JIT compiler and a profile is created for performing optimized AOT compilation when the device is charging and unused for subsequent executions.
EddieRingle··on MicroG Project: A re-implementation of Google's Android apps and libraries
> With things like Doze, the only thing that can wake the device is a push message FROM GOOGLE.

That isn't entirely true: https://source.android.com/devices/tech/power/mgmt.html#doze

EddieRingle··on Behind the Pixel: Google’s First Real Threat to Apple’s iPhone
7.1 is a maintenance release of Nougat.
← PreviousPage 4 of 6Next →