Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Ah I see, so Google doesn't use the open source version at all. I thought it was like Flutter or Angular where the OSS version was used but it's different in this case.
Just had another question, I actually just filed a feature request for Dart (based on reading this thread about Option and Result types) about whether Dart has a Result type [0]. Looks like it does in Flutter's async module, but I wasn't sure why that wasn't also brought to the rest of the language.
[0] https://github.com/dart-lang/language/issues/2697
> For Dart in particular, it sounds like there was a serious discussion about the choice
Yes, we debated it for years.
Literally the day we launched, a user filed an issue requesting support for null safety: https://github.com/dart-lang/sdk/issues/22
For most of Dart's history, that was the #1 upvoted issue on the issue tracker.
Back in 2011 before I worked directly the language, I proposed null safety:
http://journal.stuffwithstuff.com/2011/10/29/a-proposal-for-...
I'm immensely glad we finally did it, even though the migration has been a ton of work.
The main sass implementation is in dart https://github.com/sass/dart-sass, which I think is dumb because it's a fair amount slower than the old libsass written in C.
The reason they spouted was due to "Low developer resources" due to the difficulty of C, so they swapped to a language pretty much only used by Googlers. Google now has control of sass, which then gives them greater influence (even greater than just having browser majority) over CSS Spec choices (see CSS Nesting spec).