It'd be nice to have a comparison here: https://morotti.github.io/lzbench-web/?dataset=silesia/sao&m...
4,486 karma · joined June 11, 2015
It'd be nice to have a comparison here: https://morotti.github.io/lzbench-web/?dataset=silesia/sao&m...
However: https://www.reddit.com/r/typescript/comments/wbkfsh/which_pr...
so looks like it's not written in go :-)
"One thing is certain, is the less reliable gains from compute makes our purview as computer scientists interesting again. We can now stray from the beaten path of boring, predictable gains from throwing compute at the problem."
Isn't Ilya Sutskever who said some months ago that we were going back to research ?
But if they want to have me as a customer on these core values (which I'm pretty much aligned with), then they need an additional core value: they need to convince me their higher price is justified. So I want transparency on the way they use my money (and the one of their other customers).
Without that, I'm left wondering if it is not some "green washing".
IOW I'm sure Apple is expensive because it's luxury, I'm sure other laptops are not expensive because they're cheap/sold by millions. But FrameWork, I don't know why their expensive. And repairability doesn't count, design for repairability doesn't make things inherently more expensive I guess.
One hundred kilometers from there, there is this station: https://en.wikipedia.org/wiki/Li%C3%A8ge-Guillemins_railway_...
by the same architect, and budget exploded as well...
So either local governments or Calatrava is messing around :-/
IOW: when my network fails "No route to host", I want to know who failed and why. Not just "hey, start the route tool on your production sever which you don't have access to, to get to know who slipped"
So if you're concerned with privacy issues, you can run the assembly version proposed in the article locally and be well within the same order of performance.
Let's thank the author of the article for providing a decent alternative to Google.
ah, but the license is not that good we can't reproduce his code.
ahem... We're not the 1st of April...
I know, a linked list is not exactly super complex and rust makes that a bit tough. But the realisation one must have is this: building a linked list will break some key assumptions about memory safety, so trying to force that into rust is just not gonna make it.
Problem is I guess that for several of us, we have forgotten about memory safety and it's a bit painful to have that remembered to us by a compiler :-)
At that time you didn't even have the tools to cut sprites from image in the first place. That's why it took a lot of time (and I was 12 years old and my dad was pretty far away from an engineer, that didn't help).