Hacker News new | past | comments | ask | show | jobs | submit | attilakun's comments login

I used it too. It's useful to implement Promise-like semantics in Go.

If only there was a rich 3-dimensional physical environment we could draw training data from.

I made a Google Sheets add-on to evaluate JavaScript inline: https://www.evaljs.net/

It uses QuickJS compiled to WASM in the backend to sandbox JavaScript execution.


Is there a good primer that explains the math basis of this?



I do something similar in my file-renamer app (sort.photos if you want to check it out):

1. Render first 2 pages of PDF into a JPEG offline in the Mac app.

2. Upload JPEG to ChatGPT Vision and ask what would be a good file name for this.

It works surprisingly well.


What's the labor?


Using yet another app.

I use Obsidian, OneNote for note taking and I can easily create a note just for taking quick notes when using my phone but I still self text on multiple messaging apps because those are something I already use, they are quick and simple.

Having yet another note taking app just puts my reliance on that app and keeps it for a purpose, it also becomes a barrier of sorts for me to enter quick text, that I now need to do it on separate new app/platform.


Long: you buy a stock, hold it, later on sell for profit or loss.

Short: you borrow a stock, sell it, hold the money and later on buy the stock back at a lower or higher price you originally sold it for. Then return the stock to the person who lent it to you.


Why is Golang questionable for web backends? I thought it was designed for that.


It's designed to be more CPU-efficient than NodeJS or Python, but if all your heavy lifting is really in Postgres and other services you're calling, it doesn't matter and it's a bit pedantic. I think Golang was designed for something in the middle, maybe building a DBMS or some deeper backend.


I strongly disagree with this statement, Golang is excellent for building backends and just the orchestration of all the services you are calling is better done in a typed/compiled language with great multi threading support and fast compilation times that is exactly what Golang excels at.


This is trying to solve a problem a lot of people never really had. I've never been working on an Express backend and thought gee, wish I had threading.


Not true. Go is also made for this.

Node is awful with lots of connections. Go gives me way fewer bugs, easier to properly trace, static typing is a blessing, etc.

With a db that can handle thousands upon thousands of connections, Go trounced Node in my experience


using a systems language for a backend mainly gains throughput over python than latency. each request might not be faster but you can handle 100x more users.


Amdahl's law, it won't be 100x when my server is waiting on RPCs and other I/O most of the time anyway


Why was the investor okay with this?


My guess is this was small change for him and he enjoyed the adventure somehow.


Is there a Guassian splat model that works without the "Structure from Motion" step to extract the point cloud? That feels a bit unsatisfying to me.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: