Hacker Newsnew | past | comments | ask | show | jobs | submit | debazel's commentslogin

The limitations are a large reason for why they're so resource efficient in the first place.

If you just reimplement Electron in a native language then you get... Chrome, which is already written in C++. The majority of RAM usage in Electron applications is from the native parts of Chrome itself and a decent ~40 MiB chunk for the Node.js runtime.


Name one feature that is a reason for a GUI framework to require lots of resources.

To me it seems like all frameworks and apps use much more memory than 10 years ago, but don't really offer more features.

Maybe a really young GPUI still has limitations, but I doubt it would suddenly need to use 5x as much memory if you added them.


Because joining group A means you will soon be out of a job once group B out competes group A.


You seem to be the only person that got my point so thanks I guess.

I am actually pro Union but yikes the left needs to go back and actually read some Marx.


The side effect of this is also that the value of software itself has never been lower, so starting a new software business isn't very attractive in today's market.


the cost of developing software has never been lower. That is maybe 10-15% of the value in a software business believe it or not. If you can do the other 85% it's a great time to start a software business.


It doesn’t have anything to do with indexing more than one thing.

The issue with truly random IDs is that inserts are scattered throughout the B-tree index, which cause page splits, fragmentation, and poor cache locality. Using a timestamp prefix makes new IDs sequential, so inserts tend to land near the end of the index, which avoid all the B-tree trashing and improve write performance.


Yes, which means that you should probably be able to provide your timestamp to the database so it can use it for optimizing its index, rather than trying to shove it in your ID


If you did that you would also have to provide the timestamp every time you wanted to look up an ID, and now we're back to UUIDv7 again.


Sure but at least you are being honest about it. For what it's worth the database can handle this internally without you needing to hand this back but if you have a bad one then yes you should probably have it give you back a location hint that you use for future queries


How would it internally sort your index by (timestamp, ID) without you later having to provide the timestamp to locate the ID?


Sanctions force them to treat you terrible, it is the intended effect of sanctions.


Don't you say. You don't even know what was that horrible treatment exactly - didn't even ask, why would you, right? - but you've promptly explained to the guy that it was his fucking fault - he's from the sanctioned country after all, he should know his place and be quiet. You guys are just adorable, aren't you?


Look at the fuel cap, the green part of the front wheel, or the vertical frame split behind the fuel cap. AVIF smooth the details out too much.


Why do you think YubiKey would be an allowed option? Sites will require Google/Apple password manager and use this as a proxy to prevent bot accounts.


What do you do when Apple ban your Apple account?


> any tool that becomes more powerful tends to become more specialised and expensive to operate,

Isn't that exactly what is different about AI automation? AI is more generalized and cheaper to operate.


Any time big corp implements strong sandboxing they'll inevitably put the user inside of the sandbox.


That's a valid concern, but not an argument against sandboxing, in my opinion.


Sandboxing is great, as long as the user has absolute control of it and final say on what goes in and out of it. No program needs to know what else I run on my system that might go against the program creators interests. Like for instance me running a bot do the grunt work of cancelling a gym membership through their app should not be possible to prevent. Sandboxes where the system, or even worse the application inside, decide that the users wishes aren't worth respecting is an attack (that tragically often succeeds) on the user.


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

Search: