The game rules are actual math, and the puzzles turned out to be fun for kids as well as mathematicians (from my friend circle)!

- daemons

- whoami

- traps

- curses

- pwd

- inbox

bags hanging underneath them:

- spawn

- nroff

- dates

- root

a log against the fireplace wall which says "login",

with potion-like bottles saying "uucp"

and the biggest bottle of potion is named "C" (of course),

while an old broken bottle lies on the ground called "B" (of course)

Symbols on the wizard's clothes are all unix symbols:

- $ (default PS1)

- * (glob)

- % (substring)

- > and < (pipe redirection)

Now to the bottom (right to left):

- A jar called "troff"

- A spool called "usr"

- Container called "awk"

- A jar of "oregano"

- Cursive writing on a parchment paper, "shell script"

- A small cup of "tar"

- Another bottle called "diff"

Update: Ah, you said excluding the words! I guess I was too excited to write down what I saw :P

It's not ok to suggest that the Tech sector, being one of the most important industries for gaining financial independence and making an impact on the world, must remain the white male bastion that it is.

Comments URL: https://news.ycombinator.com/item?id=25202779

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=24372403

Points: 2

# Comments: 1

Here's the code:

F=()=>{ c=v.getContext('2d') c.lineWidth=.03 C=[1,-.5,-.5] S=[0,.87,-.87] P=[[X=300,Y=300],[X,Y],[X,Y]] R=()=>{d=parseInt(Math.random()3) P=http://P.map (([x,y],i)=>(c.moveTo(x,y),c.lineTo(X=x+3C[I=(d+i)%3],Y=y+3*S[I]),[X,Y])) c.stroke() setTimeout(R,17) } R()}

Assumes no existing dependencies or dwitter-like shortcuts available. Needs this HTML to be on the page:

Demo here: https://runkit.com/asyncanup/5cd629840a18bf001b4860e9

Comments URL: https://news.ycombinator.com/item?id=19927236

Points: 6

# Comments: 4

Comments URL: https://news.ycombinator.com/item?id=19726620

Points: 2

# Comments: 0

The ui seems considered and polished, works good on mobile for me

--------

Service discovery has been made too complex by combining it with orchestration. There are too many beasts-of-a-tool out there that do too much, and yet can't do versioned microservice deployments. This talk will walk you through 100 lines of Node.js code with no dependencies other than redis, and implement a discovery service with the following features:

1. Semantic versioning of services:

Services depend on specific versions of other services, so v1.2.3 & v1.3.0 can both be live, and you kill off old services that have no users.

2. Live health checks with inversion of responsibility:

Don't ping a service under high load with status & health checks, instead let it ping back when it can. If it can't ping back because it's near-capacity, then don't route any more traffic to it!

3. Mocking services during testing & development: Should not have to bring up the entire microservices stack to develop one of them.

4. Randomized scheduling: So you don't starve any one service, instead pick one at random from the ones available & healthy.

5. No highly-available service discovery service: Solving the chicken & egg requirement of a highly available service discovery service, in order to enable other highly available services. Only the service discovery database (redis) needs to be distributed.

A surprising number of tools out there simply fail to provide these set of features together, and yet pack in too many other things they want to do. This talk does the above in easy-to-understand 100 lines of Node.js code that you can use & modify with confidence!

Also, https://github.com/asyncanup/vasco-frontend lets you hook up a real-time UI on top of the service registry to show a dashboard of all the live (and dead) services

This was the first major conference talk I gave at DeveloperWeek 2018 in SF, and am mainly looking for some healthy feedback.

Comments URL: https://news.ycombinator.com/item?id=16471380

Points: 2

# Comments: 4

Apper provides:

- Much needed structure to server-side code with strong conventions

- Reliable directory hierarchy for code based on REST end-points

- Design for real-time right off the bat

- Transparent minification & bundling for single page apps

Apper lets you create bigger apps by using smaller independent chunks as subapps. Simply place individual subapps anywhere in the directory hierarchy, and they get exposed under a relative base URL.

Nested subapps are totally cool and highly encouraged. In fact, simply by moving a subapp directory to another directory updates the exposed relative URL of that subapp. No frills.

PS: Posting to Hacker News for the first time, always been an anonymous reader. Would love some constructive comments about where to take this framework thing forward :)