I remember about 8 years ago there was an "experimental" site for one of the US government's aviation weather products. And it was so very good, designed modern and usable and clean. Didn't look at all like the usual awkward government website. The team seemed like nice folks too but were caught up in some multi-year government funding system. It eventually got shut down and IIRC, none of their work ever got promoted to the main site.
We are very lucky in the US to have a fantastic weather service and a mandate for their products to be free and public domain. Unfortunately there's also a lot of political pressure on them to not be too good so that some commercial company can profit. AccuWeather was one such company, at least back in 2005: https://www.onthecommons.org/privatizing-weather/index.html
I would recommend to steer clear of a language that makes these sorts of decisions -- that certain features are off-limits to the regular developer because they can't be trusted to use them correctly -- because if you find yourself in a situation where you need that to solve your problem, you're trapped. I included Go in the set of languages I would recommend steering clear of for years, due to their decision to allow their own `map` type be a generic[2] type but no user-defined types could be[3], leading to ridiculously over-verbose codebases, but they have finally corrected course there.
If you're looking for something kinda like Elm but not likely to break your own work in the future, I'd recommend checking out ReasonML[4] instead.
[1]: https://lukeplant.me.uk/blog/posts/why-im-leaving-elm/ [2]: https://go.dev/blog/maps [3]: https://go.dev/doc/faq#beginning_generics [4]: https://reasonml.github.io/
Edit: this problem only seems to happen on Intel, not Apple silicon machines.
1) PERM processing time keeps getting longer and longer (now at 11 months, up from 5-6 months a few years ago). Do you know why or if DOL has any plans to improve it?
2) What’s the current average PERM-based I-485 processing time you’re seeing in your office? Any processing time advantage to submitting I-485 separately versus concurrently with I-140?
Thanks.
My hot take on things: When the Puppeteer team left Google to join Microsoft and continue the project as Playwright, that left Google high and dry. I don't think Google truly realized how complementary a browser automation tool is to an AI-agent strategy. Similar to how they also fumbled the bag on transformer technology. (The T in GPT)... So Google had a choice, abandon Puppeteer and be dependent on MS/Playwright... or find a path forward for Puppeteer. WebDriver BiDi takes all the chocolatey goodness of the Chrome DevTools Protocol (CDP) that Puppeteer (and Playwright) are built on... and moves that forward in a standard way (building on the earlier success of the W3C WebDriver process that browser vendors and members of the Selenium project started years ago.)
Great to see there's still a market for cross-industry standards and collaboration with this announcement from Mozilla today.