colehasson

Good luck to everyone!

the underscore makes it a symbolic variable, not one with value

unbound in the lambda sense

ghcide, took a couple days to setup but the effects are phenom

https://www.youtube.com/watch?v=cijsaeWNf2E

Thank you for sharing your story

Something nice to discuss at least.

And with Puppeteer/Devtools programmers can stay in text editors.

I like the frontend design for this work. Nice job

Accuracy or precision. Pick one?

I'm

If I wanted a Windows phone... #teampixel

Seriously, Android, OTG cable, chromecast and a powered USB hub. Done.

I miss the HN I grew up with (2017ish). This post's comment thread is the most important and maybe consequential so far, that I've read, of 2017. [comment bait]

What tools and changes do 'we' want for how 'we on github' is perceived as part of our identity?

'We' is including a domain of engineers, students, employees, employers, scholars, bug complainants, star-ers, watchers, forkers, and jobCreators...

'Our identity' is including a domain of identification, participation, faithfulness, ownership, responsibility, responsivity, lineage, heritage, autonomy, unity, temporality, follows, followed-by, and profile pictures...

Them 'perceiving' may now be an employer, fellow engineer, or utility algorithm, but I would like to plan for possible futures with higher orders of transparency in all these products.

I ask HN because I know this community will be a transforming force that anneals or explodes the potent artifacts of github. My opinion may be that github is a value, but my observation is that it has given me value. Now, what may we hypothesize together?

NixOS has my vote.

On the first ~CON: If the "end user" is a developer that is new to nix and nix expressions, the transparency of nixpkgs and its nix expressions may turn tweaking from a problem into an opportunity. Seeing the details of builds, configs, and installs clearly laid out in a nix expression taught me more about the package that I was blindly depending on. Having the same tools (nix, nix-repl, nix-shell, *.nix) available across projects and vertically within developments has reduced the "special knowledge" that "end users" need to know for both development and operations.

Extra PRO: Have the expression for your configuration just perfect? Need to build on multiple VMs, machines, EC2? Simply add an expression for networking and deploy with Nixops https://nixos.org/nixops/. Now logical and physical configuration is a declarative data file. If a build fails, I check the source. If my cloud fails, I check the source.

For me, the reproducibility and variable independence in NixOS puts the SCIENCE in Computer Science.

I worked with WISP in school. My contribution was demonstrating the platform providing sensor data from inside a chemical reaction vessel.

Also, this was the first hardware project I worked on where the community used a wiki as the primary communication and it worked! Kudos to Intel

I arrived in Mountain View tonight. I want a job. It must involve Haskell. Anything else is a waste of time. My prediction: Haskell will be ready for production when people are ready to engineer code that lasts 1000 years.