.no Files
Posted: September 16, 2022, 3:13 pm
'No Code File'
No code is the considered the best way to write secure and reliable applications. Write nothing; deploy nowhere. Written in Dockerfile, the only valid code is no code.
All no code programs are the same, regardless of use case. Any code written is a liability. No code is not stored in files, but if required, the .no file extension is used (eg. main.no). There is only one way to write no code and the du command can help identify any issues (eg. du -h main.no).
Sources:
https://github.com/kelseyhightower/noco ... r/STYLE.md
https://github.com/kelseyhightower/nocode
No code is the considered the best way to write secure and reliable applications. Write nothing; deploy nowhere. Written in Dockerfile, the only valid code is no code.
All no code programs are the same, regardless of use case. Any code written is a liability. No code is not stored in files, but if required, the .no file extension is used (eg. main.no). There is only one way to write no code and the du command can help identify any issues (eg. du -h main.no).
Sources:
https://github.com/kelseyhightower/noco ... r/STYLE.md
https://github.com/kelseyhightower/nocode