> Continuing work to restructure Firefox’s JavaScript memory management to be more performant and use less memory.
I went back the last few versions major release notes and didn’t see mention of the initial work to improve the JavaScript memory management. Is anyone aware of this work/what’s going on to improve memory management here? Interested to read more about the technicals!
Servo has very little to do with JavaScript, so no.
The parts of Servo that made it into Firefox are still being worked on by Firefox developers. I don't know how much activity is happening on the now-external Servo project itself.
> Under Swiss law, it is obligatory for a user to be notified if a third party makes a request for their private data and such data is to be used in a criminal proceeding.
They’re not explicit with regards to the activist, this would mean the activist was notified upon ProtonMail receiving the request?
I’m not sure there’s much you can do but lawyer up if you receive such a notice, but potentially the activist could have immediately started using Tor (maybe too late though, because to read the notice they might have already leaked their IP).
I did, it was non-mandatory and most of the (small) company would be on the call each day. I would turn my camera off and opt for just audio, but others would leave theirs on.
I enjoyed it for being able to have a quick back and forth when I had a question for something that was stopping my current task. Alternatively, I would be waiting on an unknown response time to a chat message which lead to a lot more task switching mid progress. But most of all, I just enjoyed the general talk that comes from being on a non-specific all day call - sports, family, news, etc. I learnt a lot more about my work mates that I otherwise wouldn’t have, which made us closer and work more enjoyable, plus working remotely can just get lonely sometimes.
I say all this and must mention that this call would happen daily for 6 months or so, but has slowly lost participants or only happens every other day as the company changes/grows. For me, I would like to see it come back!
I have an identical setup to this, painless to deploy updates/blog posts and zero cost.
I was previously using Jekyll, but moved over to Gatsby a few months ago and have enjoyed the built-in features of Gatsby and it’s surrounding ecosystem so far.
I have also considered integrating a git based CMS like Netlify CMS, but because it’s so easy to make new blog posts with just a git commit and a push I haven’t taken the time to change the workflow.
- I can edit markdown as either plain text or rich text, and switch between them with a toggle
- (Most important) I don't need to worry about whether I've properly filled in the 'frontmatter' section at the top of the file
The format of the frontmatter is indicated to Netlify CMS by the existence of a simple config file in your repo. So it should be easy to give it a try if you want:
The CyberWire is a daily (Mon - Fri) podcast for cyber security news. Each episode goes for around 20 minutes and breaks down any significant news from the last 24 hours/weekend.
This is about the only cyber security news I directly follow and it tends to keep me abreast of the major going ons and the 20 minute length is short enough to digest daily.
I can see use cases for a delete function, but as people mention it’s all about how you manage abuse.
If a project owner really wanted they could just delete the whole repo (which includes issues et all) with no warning or confirmation from collaborators. But that’s a larger more destructive move, whereas, deleting a politically fuelled issue can be abused with far less repercussion.
Not on an issue, but I did once have a moment where I could have used a delete function on a pull request. I merged a pull request with my personal account on a repository I had only been working on under a pseudonym. From memory even resetting to an earlier commit and re-merging again with the correct identity didn’t work as GitHub kept a record of the original merge on that pull request. Which only further tied my two identities together as I tried to correct the mistake.
There were two things I thought could use some improvement.
First were the two images of a list of hyperlinks that look clickable. I tried clicking on the links to no avail thinking they were broken, only to realise I was clicking on an image. The two images in particular are the News Sections and Newsmakers images on the homepage.
The second point was that I initially couldn't figure out how to access the service. I had to click on "Read the U.S. edition" which sounded like a sub-section of the site, not the main news aggregator service. What threw me off was the website slogan of "Daily news from around the world", I was trying to find the rest the news, not just the U.S. edition. If this is the only option right now, it could possibly just say "Read the News". Take this with a grain of salt though as I am not a U.S. citizen, so I might not be your current target audience right now.
> First were the two images of a list of hyperlinks that look clickable. I tried clicking on the links to no avail thinking they were broken, only to realise I was clicking on an image. The two images in particular are the News Sections and Newsmakers images on the homepage.
We heard this privately from a couple of other people as well. We'll definitely look into making the Features section a lot less ambiguous.
> The second point was that I initially couldn't figure out how to access the service.
> I am not a U.S. citizen, so I might not be your current target audience right now.
We're looking for feedback from non-U.S. citizens on which other news editions they would like to see. For example, we've come up with Canada, UK, Europe, Africa, India and Japan as geographical areas that could have news editions but we'd rather work on what our readers want than what we think they want.
This seems to be only a WebKit issue, you can produce the same results on desktop Safari. Other browser engines must detect when an alpha channel value is used with an `rgb` CSS attribute and update that attribute to `rgba` accordingly as an assumed fix.
Could be more (people stop watching and go outside) or less (people go back later to watch what they would've watched anyway, and free advertising for everyone talking about it) depending on several things.
Very disappointing, this was my go to weather app. Any other recommendations? I'm using iOS in Australia, but also like an app that can track international weather.
I went back the last few versions major release notes and didn’t see mention of the initial work to improve the JavaScript memory management. Is anyone aware of this work/what’s going on to improve memory management here? Interested to read more about the technicals!