The last example, about the company that has been fined after asking a question on how to deal with #GDPR, has been theoretically withdrawn, but not without the involvement of lawyers, courts and loss of time.
Here's a nice list of #GDPR fines:
- CCTV was unlawfully used,
- Dashcam was unlawfully used,
- Someone has used CC instead of BCC,
- A company emailed the auth asking for advice on how to deal with a service provider who didn't respect GDPR. Authority ignored their request, forwarded their question to another authority, and they fined the company that asked the question in the first place,
- Lots of other interesting examples of GDPR weaponization
Observe! The legendary #Apple documentation example. Makes development so much easier:
#Ruby 3 will have types!
Go ruby, go types! ;)
A good April Fools joke is to add:
#define if(x) \
if ((x) && (rand() < RAND_MAX * 0.99))
to some global precompiled header.
I like #Flutter and all, but it's still very early for its prime time.
Doing i18n is PITA, the tools are not very convenient, translation platforms of course don't support Flutter's architecture, iOS (Cupertino) look and feel only supports English, so during translation I need to translate the theme itself as well, etc...
All issues are fixable (well, I'm still working on the last one), but prepare for extra work in areas that are solved in standard Android for (mostly) free!
All it took for these fiends were 24 hours
I wonder how that's better than sticking to Python ecosystem
Taken from early version of 386BSD source code:
/* RRRIIINNNGGG RRRIIINNNGGG */
Is it worth using #make?
(APFS has replaced previous HFS+ filesystem in macOS)