I've always liked dev tools as a place to learn about how HTML, CSS and JS actually work. The latest iteration of that: Firefox to show which properties don't actually do anything on a given element
I've been involved in DevTools dev for years, and I've both had and heard many good ideas to improve it.
It's always a special feeling seeing on of them finally take shape.
Latest one to date: detect C…
And yes, Firefox is still fighting a huge uphill battle against Chrome interop, and I have no idea how they're even able to keep their heads above water. They need all the help they can get, because they're battling stupid bugs like this every single day.
WebKit (Safari) is no less amazing for the comeback they've pulled off in the past few years, although they have fewer interop pressures. Web devs make sure their sites work in Safari, because the CEO has an iPhone.
> In this paper, we aim to answer a long-standing open problem in the programming languages community: is it possible to smear paint on the wall without creating valid Perl?
> We answer this question in the affirmative: (...) merely 93% of paint splatters parse as valid Perl.
The idea is very funny, the presentation is hilarious.
Rewrote emoji-mart's tests to run in Jest rather than Karma (https://github.com/missive/emoji-mart/pull/302). Gotta admit, Jest is nice:
- can test React components purely in Node
- has a concept of "snapshots," where it writes your expected component tree to a file and then tests against that file, which is what I want to do with my tests 99% of the time, except now it's automated
- I didn't even need a config file, what year is this
"I don't really want to argue against optional chaining because it's so popular and I don't want to make enemies, but here's how *other* people might argue against it."
A retrospective on the things I would have liked to try in Firefox Test Pilot: http://www.ianbicking.org/blog/2019/03/firefox-experiments-i-would-have-liked.html
We'd like to thank you all for the follows, responses and support the last few days... Show more
have you ever noticed that someone post a screenshot of text without providing an image description, preventing you from being able to read it? or maybe they posted a huge amount of text that just can't possibly be described with the image description feature?
simply tag @OCRbot in a direct reply to the image. it will download the image and scan it using tesseract OCR to output the text contained in the image!
because OCRbot runs on fedi.lynnesbian.space, it has a character limit of 65535, so even the longest images should work OK!
check the reply to this image to see it parsing the attached screenshot!
All this is powered by freely available open source tools. More info at my blog: https://vincenttunru.com/fearless-deployments/
Front-end developer trying to open up access to academic research and helping out with @ToSDR. My current "boring stack": React+TypeScript.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!