Firefox app on my Android phone was updated yesterday to 67.0.3, and the release notes mention the security fix.

There's more than one mobile version.

Latest Android Nightly build is 68.0a1 from 2019-05-04.

Latest Android Beta build is 68.0beta, from May 21, 2019 (actually from APK name it's 68.0b11).

Latest iOS Release build is 16.0, from April 15, 2019.

By the way, latest Desktop Beta build is 68.0beta, from May 22, 2019, and latest Desktop Nightly build is 69.0a1, from May 20, 2019 - and there's no information about whether they affected too.

The iOS version should be unaffected, as Firefox for iOS does not include its own JS engine (it uses the one provided by the system), which is where this vulnerability is.

For the Desktop version at least, if you download the current beta (68.0beta11), you'll notice that it was built two days ago. The latest nightly was built today. The changelog for these is just not kept up to date.

My biggest issue with navigating Go codebases is that sometimes it's cumbersome to find where a specific type/function is defined, when there are multiple files under the same directory.

A simple text search will find it every time. Since Go code should always be formatted, it's pretty trivial to search for `type HTTPServer` or `func NewServer(` ... even over fairly large codebases this will give few enough hits that you can just search everything most of the time.

Not to mention trying to figure out which types implement a given interface. You'll get completely unrelated types you don't care about a lot of the time.

Would this not be solvable with something like ctags or godef?

(I'm a newbie with Go so I've probably missed something in the problem you're describing).

I've had this issue as well and found that it makes using an IDE almost mandatory for large code bases.

I agree with you. Of course, an iPhone can surf the web, make calls, take pictures, run the calculator, etc. However, lack of means to install apps without the App Store (besides sideloading), can render any phone pretty much useless.

Android has problems of its own though. Yes, you could install apps easily without access to the Play Store. But most Android apps rely upon Google's Play Services one way or another, so those apps wouldn't work properly, if at all.

I think that the issue is not whether remote work sucks, or working in an office is superior, but it's more about hiring the right people. This gets a lot harder when hiring for remote work, which is why many remote companies require previous remote experience.

Could it be that it's a case of multiple APK? Perhaps different CPU architecture? In any case I would check the value of versionCode first (https://developer.android.com/guide/topics/manifest/manifest...).

I guess they did...

Up until Swift 4, compilation took longer than with Objective-C according to my experience. Not sure how much Swift 5 has changed things.

I agree with you, in that it's an essential skill for our job. However, from my experience at least, I've found that going head first into the source code of something you don't really understand how it works, is not the best course of action.

For example, I would make sure to read about B+ trees first, before reading the implementation of indexes in SQLite or PostgreSQL.

I like the Go language for all of its efficiency and easy concurrency, but part of me can't help but think that they were dying to make some new syntax just for the sake of it.

That syntax was based on Oberon-2 (1991), given Robert Griesemer's presence on the team.

    PROCEDURE (q : Query) GroupBy*(field:  String): Query;
    BEGIN
     (* .... *)
    END GroupBy;

Great job! This is the first time I'm able to find a nice color pattern so easily. The sample images are very helpful.