echohack5

Joined 8 years ago

Karma
415
Submissions
78
Member since
May 5
Gaming Tech Creator | http://youtube.com/echohack
View on Hacker News

Recent submissions

Comment · 1 day ago
Isn't the current economic scenario unsolvable from the supply side in a 20 year time span? Like is ASML going to magically start mass manufacturing EUL machines, the universities magically gonna spit out 10K more PhD grade level people to work new foundries, and some country magically going to make all the infrastructure investments to build entire cities of compute manufacturing?

Maybe I am wrong but the supply side of this equation seems completely hosed from a fundamental perspective.

Comment · 14 days ago
Hey yall!

Been doing some architecture work lately, and decided to start rendering these using Factorio sprites and factory style layouts. For me, it's been extremely useful for spotting certain patterns and problems.

Released as open source, feel free to take it for a spin. PRs are welcome.

- Echo

Comment · 1 month ago
Am I supposed to feel bad for the cancer juice people?
Comment · 1 month ago
As someone who has been using alot of spacetime for side projects (like https://heat.echohack.app), I am continually impressed with the speed at which it operates.

I think there's alot of interesting things happening in the database space. Vitess/Neki, vector stores, spacetime are all really good things to be happening. I think it's a shame that database developers seem to have a drama filled timeline out there. It's... all very exciting, together.

Anyway, Some things that need improvement (some of which are addressed by this blog post):

1. Backups (fast recovery) and Disaster Recovery (slow, durable recovery)

This is a big one, but sometimes speed is not the only objective you have to meet. You need to have certainty that, if everything goes down that you (eventually) can bring things back online. I don't really have a way of doing that today.

2. Read replicas sure would be nice for analytic workloads

3. Durable writes to s3 would be nice for intermittent bursting workloads (like ci systems)

I think the Spacetime folks have their work cut out for them, not necessarily because of the technology (that's hard too) but because the AI models have seemingly decided that Neon and Postgres are all that exists.

I think spacetime has a bright future ahead of it, and I am wishing the team all the best as they work hard to imprint something new on the universe.

Comment · 2 months ago
The weirdest payment method has got to be the Coke ON vending machines that do not support SUICA but instead require you to QR code-IR blaster you to a website where you bluetooth pair with the vending machine then buy it on your mobile browser.

Like....somehow they turned a sub 1ms operation into a 4 minute 32 second one. It boggles the mind

Comment · 4 months ago
Which is precisely why powers will try to make all these illegal
Comment · 7 months ago
The oxford comma debate is so annoying because it clearly has nothing but advantages. Removing commas from a delimited list does nothing to resolve ambiguity, whether lexicographically or syntactically.

It's so useful as a delimiter and anti-ambiguity machine, that you don't even need spaces for it to work! See CSV or Japanese.

Comment · 9 months ago
I have found AI great in alot of scenarios but If I have a specific workflow, then the answer is specific and the ai will get it wrong 100% of the time. You have a great point here.

A trivial example is your happy path git workflow. I want:

- pull main

- make new branch in user/feature format

- Commit, always sign with my ssh key

- push

- open pr

but it always will

- not sign commits

- not pull main

- not know to rebase if changes are in flight

- make a million unnecessary commits

- not squash when making a million unnecessary commits

- have no guardrails when pushing to main (oops!)

- add too many comments

- commit message too long

- spam the pr comment with hallucinated test plans

- incorrectly attribute itself as coauthor in some gorilla marketing effort (fixable with config, but whyyyyyy -- also this isn't just annoying, it breaks compliance in alot of places and fundamentally misunderstands the whole point of authorship, which is copyright --- and AIs can't own copyright )

- not make DCO compliant commits ...

Commit spam is particularly bad for bisect bug hunting and ref performance issues at scale. Sure I can enforce Squash and Merge on my repo but why am I relying on that if the AI is so smart?

All of these things are fixed with aliases / magit / cli usage, using the thing the way we have always done it.

Comment · 1 year ago
Office because lawyers send docs in .docx format like it was written in the blood of the Benjamin Franklin

DirectX because steam defacto runs on Windows only for the vast majority of games, and not everyone wants a steam deck form

I can't think of any other S tier use cases tbh

Comment · 1 year ago
This was a fun thing to realize in my early days of programming in Delphi. I guess the author will soon realize why old systems name things ticket "00001" and so on.
Comment · 1 year ago
In 2012 managing the JVM was a nightmare. Java is fine now.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton