Love the source code, so clean. First time I see a makefile used like that with Docker and front commands.
Show HN: Print a WiFi Login Card
171–180 of 347 posts
Re: Show HN: Print a WiFi Login Card
#172qrencode -t utf8 'WIFI:T:WPA;S:network;P:password;;'
wow ok, so you expect me to have a computer (?!) with: - a keyboard? - access to a terminal??!?!?! - ability to install qrencode??? - knowledge of copy and paste!?!?! - some way to edit the command you posted to my specific username and password?! franky this is ridiculous when i could just make a repo that uses make, docker, yarn, npx, nginx, react, and jest /s
Re: Show HN: Print a WiFi Login Card
#173Earlier quoted context omitted.
A lot of developers only know the new, needlessly complicated ways of doing things. I have met professional software engineers who have never heard of shared web hosting, for example. It's also surprisingly possible to learn enough about programming to get a job without understanding basic computing concepts. I've met professional software engineers, with multiple years of experience and promotions under their belt,…
I thought that was crazy, but reflecting over my CS education they haven’t gone over the difference between disk space and RAM. I suppose they figure everyone already knows?
Re: Show HN: Print a WiFi Login Card
#174Re: Show HN: Print a WiFi Login Card
#175Re: Show HN: Print a WiFi Login Card
#176Re: Show HN: Print a WiFi Login Card
#177Re: Show HN: Print a WiFi Login Card
#178Re: Show HN: Print a WiFi Login Card
#179Earlier quoted context omitted.
To be fair it’s fairly easy to check that it didn’t send any data over the wire
> To be fair it’s fairly easy to check that it didn’t send any data over the wire ... after the fact ... ... for a user of the web app who watches the network panel from their browser's developer tools
Re: Show HN: Print a WiFi Login Card
#180Asking as a person who understands the fundamentals of all of the technologies involved but is horrified by much of what goes on in the minds of today's web developers and designers, what motivates the decision to make this repo use make, docker, yarn, npx, nginx, react, and jest rather than a bit of static HTML and css and something like qrjs2.js or VanillaQR.js with a simple canvas or datauri update in onInput?
Answering as the author who also understands the fundamentals of all of the technologies involved and questions much of what goes on in the minds of today's web developers and designers-- I use Make as the standard way to interact with every repo I own. This allows me to type `make build` instead of `$some-language-specific-command-I-forget-in-2-weeks`. I use Docker for distributing every app I build. If the app is a…