coolcase

Neuro-visual I think. Hard to see 100s of dots in a circle as not a circle.

The same principle is why this looks like a circle/ellipse but it isn't:

O

> Totally out of left field here, but I got some auditory synesthesia from watching this, especially on high speed. If any of you did as well and are interested why, it's probably the same phenomenon talked about here: https://www.newscientist.com/article/dn14459-screensaver-rev...

Second this old comment!

I found my new loading icon

Is collaborative text editing with offline sync a nerd snipe [0]? I work for a big tech and write a lot and usually worse case someone else edits at the same time and the server can figure it out. yes it needs some kind of algo but most concurrent edits are on different parts of a huge doc.

Compare this to Git workflows. Git already handles merging most changes seamlessly.

[0] https://xkcd.com/356/

I was imagining for a bad behaved site run it in a cgroup but it would be better if the browser did that per tab

Does that create a sort of Conway's law pushing complexity to the FE?

"Phone as in the protocol" might be over but the idea of a voice only channel for synchronous communication is not.

When cars came along the horse was over but the carriage bit is still going strong!

Virginia, us-east-2, U.S.A.

(P.S. check your spelling!)

Big tech ain't investing heavily so you can run local, what data does that leave them to sell, and what power and control does that give them. Zilch.

The human is alive anyway so zero extra footprint.

Run the browser in a cgroup?

Here is a number that has all those pictures encoded: π

I want to hear the perspective of someone who lost 100kloc and had to rewrite it all!

There is a lot of value in code. It works in prod. It is continuously regression tested by its load, so when there is a problem you figure out a tiny delta to fix it.

If you rewrite from memories you'll get a lot of bugs you need to fix again.

Code being worthless and "must keep PRs small" seem to be in tension.

I'm talking about the runtime though e.g. concurrency story being the main thing. Speed too. Easier multiform use. Memory footprint.

JS fetch function in three browser.

Add a route on the back end.

RPC means just call it! don't worry about REST, GQL etc.

That is dodging the point. The guy ripped people off. By luck they got the fiat value of their investment at some past date back. Yes if a single investment pays off well enough to negate fraud losses on that scale over a short time scale. It's fucking luck.

You don't need to deal with those anyway. RPC it. fetch one one end, route on other.

I'm torn between Go (nicer runtime) and Node (get to use TS for nicer types!)

Finding a job with an office with a shower? Guess it is luck lol

Kubernetes pods?

SuperPAC and other corruption

That's why you need teams. Red team for example! Security team. App developers. Code reviews. You need all the process too. Security that relies on one genius is fragile.

How is that fair? It was luck from the AI investment. Pure luck.

Yeah the /leakitbaby endpoint was meant for just them, not the world! Doh!

Most places I work have a shower - albeit not just off the main office. Usually part of the building infra. It's great if you cycle to work for example or play sport at lunchtime. It's a good thing if well placed.

I see LLMs as a faster stackoverflow rather than a cheaper human

Ideally assistants will look at your package.json then make web calls to bring in the docs. Maybe a README.AI file that is more token efficient can provide the data.

Guess here X25 is the YC batch.

What if the opt out list gets pwned?

They buy politicians