eb
TheSilentDrifter
eb7246eb8e26b0c48dd4f9c2a822a0f4d5c84138937195090932b61a2d756051

On Wikipedia they linked to the project which required membership to UC Berkley. However, I did just find this (not sure if it is actually the same)

https://github.com/OSPreservProject/sprite

I was very surprised to learn it was this low. nostr:nprofile1qqs2rlzal4lleatrezg4tdrxw5d4srg3tcfkutuvjr5fzvu9h0kmrncpzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qgdwaehxw309aukzcn49ekk2qghwaehxw309aex2mrp0yh8x6tpd4ehgu3wvdhk68uj6gq have you covered this in an episode of #tspc ? I would be interested in your take on how to reverse this trend.

Definitely worth seeing! The also have a bridge at the base where you can get up-close and personal, too. If you like biking, there is a bit path along the trail, too. It is a lot of fun.

I agree. Really cool, but missing some critical features my wife wants. I honestly haven't found a great financial app. Planning in making one of my own.

I have experience with all three. It depends on what you are looking for. Do you want speed of development? Python has the lowest barrier of entry. You can crack it out in a few hours. However, you will have poor performance. You want something a little better, use Go. A little harder, but a bit faster. You want the best performance and most security? Use Rust. It is the hardest, but best in the end for size and performanc

https://haslab.github.io/SAFER/scp21.pdf

Can you just put a configuration conditional block to check the architecture you are using? Create a type alias which is then set to either usize or u32. That way you could leave all type annotations as your aliased type regardless of the architecture.

go vs rust:

go: easy to read, concise, many good texts on making use of good names, and consistent layout due to gofmt, and no macros because of how they complicate static analysis and symbol mappings

rust: hard to read, ugly, and no consistent layout enforcement or culture, and macros

go: uses a GC so for most small pieces of code it is not polluted with memory management annotations or allocation/free operations, no immutable types except the stupid strings, which should be abolished anyway, friction is low for your early stages of learning

rust: uses an arcane, hard to learn semi-automatic garbage collection scheme that requires you to pollute all your code with these annotations, that will prevent you from finishing a basic next-after-hello-world program before 2 months from starting with the language

go: designed by two of the most important people in the history of operating systems and programming language, Rob Pike, who invented Newsqueak that enabled concurrent programming and designing software as a production line and easy, lightweight threads, and Ken Thompson, who invented the language B and was heavily involved with the development of unix

rust: invented by Graydon Hoare, while he was working at Mozilla, who went on to sponsor it and fund an aggressive campaign of popularising it that seemed to really hit the spot getting shitcoin projects to adopt it, especially, and now is the most popular language for shitcoin devs, and mozilla, a company who in contrast to google, who is just as much a spook front (mozilla is netscape btw) do not shove DRM down the throats of users with a non-disableable nag for DRM widevine that literally stops you being able to screenshot your entire display when one of these pieces of shit is being painted on a window on your display, as opposed to chrome, which does not force this on you or nag you to enable it

Go is the product of the work of guys who have been doing production software development for 40 years, versus this new language from some rando sponsored by a company that doesn't see a problem with DRM

Rust is a product of the same people who brought us javascript in the browser and the dumpster fire of security that is the web-browser-as-app-runtime, and its compilation times nearly reach the heights of C++ as well as the compilation memory usage, and until they introduced cargo, which is basically the Go tool for rust that manages compiled object caches and source repositories... AND the cargo has a centralised registry that is under the control of Spookzilla whereas Go, google runs a proxy cache that is used by default, but the hosting of your code is only centralised by the DNS system, and requires no procedures or other complex namespace hoops to jump through

plus, Google doesn't try to push everyone else to use it, they more than sufficiently benefit from using it to develop much of their own infrastructure, and Docker and Kubernetes both are built on Go and run half the internet

lastly, rust users are rabid cult drones who are constantly bragging about how they built their thing in rust, a brazen vanity that you don't see anywhere near as much with Go devs

I hate rust, and i hate everyone who loves rust, you can all GFY

#goodvibesonly #golang #rust #gfy

Spoken by someone who is clearly biased, cares nothing for performance, does not understand the importance of memory fundamentals, and couldn't care less about the actual history. You, sir, have just proven your opinion means very little to me.