Flutter Heroes
📈 Telegram kanali Flutter Heroes analitikasi
Flutter Heroes (@flutterdev) Ingliz til segmentidagi kanali faol ishtirokchi. Hozirda hamjamiyat 21 966 obunachidan iborat bo'lib, Texnologiyalar & Aralashmalar toifasida 6 051-o'rinni egallagan.
📊 Auditoriya ko‘rsatkichlari va dinamika
невідомо sanasidan buyon loyiha tez o‘sib, 21 966 obunachiga ega bo‘ldi.
13 Noyabr, 2026 dagi oxirgi ma’lumotlarga ko‘ra kanal barqaror faollikka ega. Oxirgi 30 kunda obunachilar soni -211 ga, so‘nggi 24 soatda esa -10 ga o‘zgardi va umumiy qamrov yuqori darajada qolmoqda.
- Tasdiqlash holati: Tasdiqlanmagan
- Jalb etish (ER): Auditoriya o‘rtacha 6.33% darajada jalb etiladi. Nashrdan keyingi dastlabki 24 soatda kontent odatda umumiy obunachilar sonining N/A% ini tashkil etuvchi reaksiyalarni to‘playdi.
- Post qamrovi: Har bir post o‘rtacha 1 392 marta ko‘riladi; birinchi sutkada odatda 0 ta ko‘rish yig‘iladi.
- Reaksiyalar va o‘zaro ta’sir: Auditoriya faol: har bir postga o‘rtacha 1 ta reaksiya keladi.
- Tematik yo‘nalishlar: Kontent developer, firebase, widget, hemantpra389, engineer kabi asosiy mavzularga jamlangan.
📝 Tavsif va kontent siyosati
Kanal uchun tavsif kiritilmagan.
Yuqori yangilanish chastotasi (oxirgi ma’lumot 14 Noyabr, 2026 da olingan) sababli kanal doimo dolzarb va katta qamrovli bo‘lib qoladi. Analitika auditoriya kontent bilan faol hamkorlik qilishini, uni Texnologiyalar & Aralashmalar toifasidagi muhim ta’sir nuqtasiga aylantirishini ko‘rsatadi.
exam1(i) { var n1 = i + 4; // should this be okay? int n2 = i + 4; // this compiles int n3 = 4 + i; // this does not } In my dream world this code should – from a safety standpoint – not compile. Adding the integer 4 to anything that I put in and it is okay with that?? This is madness! Creating an integer from anything plus 4 is okay? Strangely enough 4 plus anything is not okay?The language should force me to use specify types everywhere! Leaving it blank to mean “dynamic” should not be an option. Being explicit is key! “Yes I want dynamic type here” / “Oops you are right, the input/var should be an int”.If I use dynamic type, it should again force me to cast it to an integer before use and provide a default value if that fails.EXAMPLE2void exam2() { List<int> nums = [1, 2, 3]; int n1 = nums[8]; // not safe (crash) int n2 = nums.elementAt(8); // not safe (crash) // something like this should be possible if nullable types were used instead of exceptions and it would be safe //int n3 = nums[8] ?? 5; //int n4 = nums[8, default: 5]; //int n5 = nums.elementAt(8) ?? 5 //int n6 = nums.elementAt(8, default: 5) } Why is there no easy and short why to access a list in a type safe way (without comparing index to list length)? If indexing a list or using elementAt provided a nullable type (e.g int?) you can work with lists in a 100% type safe way and even specify a default value if the index is out of range.Dart should make more use of nullable types and less exceptions. Exceptions crash your program (if not handled); using nullable types and null-safety prevents this.EXAMPLE3void exam3() { List<int> nums = [1, 2, 3]; int n1 = nums[8]; } Calling a function should always (99.99%) be safe. Other programming languages have keywords like “throw/throws/throwing” to indicate that a function call is not save and you need to handle errors. For me it is super annoying that I cannot be sure that the function I call is safe and I might have to dig into the documentation for details. Again, having the language/compiler force me to specify throwing functions with a keyword and to handle those exceptions provides safety!There should be some keyword that indicates if a function/method can throw an exception so the compiler forces you to handle these to provide safety.Sound null-safety is a great start but there is much more a language can do to prevent bugs/errors/crashes.I think in a “sound language” the program should not be able to crash unless the programmer explicitly allows it!This is only my opinion that is heavily influenced after using swift for many years.Do you think this is something that is planned for dart (maybe 3.0?), or do you think that the new “null-safety” is safe enough and the dart/flutter team will not improve safety much more??
March 17, 2021 at 10:57AM by JulianCologne
https://ift.tt/3rYow6p