Do the vendor compilers have a very focused feature set as a result? To reduce both test surface area and chance of expensive mistakes?
66 karma · joined November 30, 2018
Do the vendor compilers have a very focused feature set as a result? To reduce both test surface area and chance of expensive mistakes?
Also, the horn is a signal. It allows you to evade and alert other users that something needs their attention. Maybe they need to avoid you while you avoid something else.
What does a vendor compiler do or do better than a compatible generic one?
Suppose something like CATIA was available on Mac and offered lets say a performance benefit. Would you consider Mac? Or would you for example still need a whole other set of tools to be available as well for it to be even possible?
Apparently, this does not happen at enough places.
When any of us remain silent when we witness or hear about abuse we are allowing other people to be victimized now and in the future.
How does that even work? How can one be 'non-technical' when they are managing people who produce technical output? Is it not key to managing this situation that one understands what is being done to at least some degree? And if one understands to some degree then one is not 'non-technical' I would say. If understanding is lacking; it can be learned.
It's not like it's magic!
Or more directly: sparkles and flashing lights.
Seems like this Wikipedia entry is relevant: https://en.wikipedia.org/wiki/Blinkenlights
This was entertaining: ": ACHTUNG! ALLES TURISTEN UND NONTEKNISCHEN LOOKENPEEPERS! DAS KOMPUTERMASCHINE IST NICHT FÜR DER GEFINGERPOKEN UND MITTENGRABEN! ODERWISE IST EASY TO SCHNAPPEN DER SPRINGENWERK, BLOWENFUSEN UND POPPENCORKEN MIT SPITZENSPARKEN. IST NICHT FÜR GEWERKEN BEI DUMMKOPFEN. DER RUBBERNECKEN SIGHTSEEREN KEEPEN DAS COTTONPICKEN HÄNDER IN DAS POCKETS MUSS. ZO RELAXEN UND WATSCHEN DER BLINKENLICHTEN."
Seems to fit what our author was going for too.