The login form example which returns values reminds me a lot of imgui and other immediate mode GUI frameworks.
1,838 karma · joined May 14, 2020
The login form example which returns values reminds me a lot of imgui and other immediate mode GUI frameworks.
But GJK only gives you part of the story. The fun bit comes after with EPA[2], which gives you more actionable information for your collision detection routines. It took me a bit longer to grok EPA than it did GJK; I probably spent a week or so fixing bugs and handling edge-cases before I had something that worked consistently. However, the fact that you can just use the last simplex you calculated from GJK to continue with EPA was a very nice property to have.
[1]: https://youtu.be/Qupqu1xe7Io [2]: https://dyn4j.org/2010/05/epa-expanding-polytope-algorithm/
My concern with fragmentation is that this is essentially a reimplementation of Rust in another language (C++) targeting a different backend (GCC). It's only natural for there to be differences between the two, especially over a long period of time.
There is a separate initiative that may be more in line with what you're thinking which adds GCC backend support for the existing mainstream Rust compiler.
On one hand, having frontend diversity for a language helps bring new people into the language; think of the groups who can't use Rust because it doesn't support certain targets or can't integrate with their existing toolchain. There is a lot of talent that could be brought into Rust just by virtue of them being able to be included and the less barriers of entry, the better.
But on the other hand, I don't want to have to think of implementation specific behaviors, bugs, quirks, et cetera. Having an ecosystem built with thousands of people wrestling with that problem seems like a recipe for buggy software and burnout. People say that a spec would help with this aspect but I'm sceptical; a spec doesn't prevent divergence from happening, it just gives you a frame of reference for what is correct. You also don't need multiple implementations to have a spec either!
I fear that the way this is going to pan out is that we'll have multiple frontends for Rust, but the vast majority of engineers using the language will only ever think about "true" Rust: the current mainstream implementation. Issues in crates that primarily affect "alternative" Rusts will go unacknowledged, be tossed out, or have hacky patch jobs. We'll end up with either a) two separate, but high quality, ecosystems or b) one shared, lower quality ecosystem that is constantly fighting itself. I hold Rust in really high regard and it's my favorite language at the moment, so this thought is scary to me.
Though, there are a lot of smart people involved so maybe it doesn't have to be so doom and gloom. A couple of years ago I thought that cross-platform software was really messy and hard to get right but languages like Rust have the proper language features to make things like this much easier (though not perfect!). It could be that the emergence of multiple frontends could necessitate features and tooling for the Rust itself which makes all of that I said a non-issue. Maybe. Hopefully.
They're affordable, ethical, and the product does exactly what I want and nothing more. I simply love Plausible and I'm happy to see them picking up steam!
It'd be pretty funny if they were also indexing into Github to train their models.
Above all, one thing is clear: the most successful part of this was the fact that the state provided essentially a free bank account; most people are choosing to bank USD and not BTC in Chivo! On top of this, the majority are either not transacting in BTC or are transacting in BTC and immediately converting to USD. This is a total failure for the cryptocurrency side of things but a rousing success for the fiat side as you could easily remove the entirety of the BTC functionality and still have a working app. It might even do better this way!
It's been repeated over and over again that cryptocurrencies will bank the unbanked, but it's abundantly clear now that cryptocurrencies are absolutely not a requirement for achieving this. If private industry is not going to provide a market solution to the unbanked, let El Salvador show that a government can easily accommodate in its place.
On one hand, it's awesome Wildbit was able to sell Postmark on their terms. To be able to build something, make money, and then walk away when you want is a huge accomplishment. Hats off to them.
On the other hand, the reason I always chose Postmark over Sendgrid, MailChimp, et cetera, even though they were much smaller, is because they seriously cared about their customers. Support is fantastic of course, but it was really the little things that made the experience great.
An example, they manually vetted each of their API consumers to ensure one bad apple doesn't spoil the bushel. It's probably not cost effective to gate customers like this, but in the end I don't have to worry about MY email not being delivered by one of the major providers because some other person used Postmark to send a spam campaign. Stuff like this happened all the time with Sendgrid and the only remediation I've ever seen was "upgrade to our $90/mo plan and manage it on your own."
Maybe ActiveCampaign will keep this level of quality and care (it is the same team after all), but I can't help but be a little cautious. I've been burned one too many times by an acquisition of a great product by a not-so-great company.
It would be nice if you guys provided a Tachiyomi plugin; most of what I read is in Tachiyomi so it'd be inconvenient to switch between two apps.
Thanks to all the contributors for getting us to the 2021 edition!
If you're using either a library that wasn't written in pure TS (maybe JS or JS with .d.ts) or interacting with some unconverted JS from your own codebase, you can easily pass a null through entirely by accident. The problem really stems from the JS end of things, but 9 times out of 10 you're going to be touching JS at _some_ level when using TS so I think it's fair to point out this gap.
Even if it was only a few hours things have significantly improved in my life in the period it went down. Zero anti-vax spam from FB sent to me via texts from older relatives.
This isn't to say it's useless, just that it's not as useful as it _could_ be. I've seen codebases in all three languages where there have been real production issues due to null values, even though the type decls say otherwise. Kotlin probably does the best job here but using any JVM library introduces potential (K)NPEs.
It's cool for preventing things like censorship. Something like SciHub would really benefit from it.
However, for "real world" use cases, many people want to be able to remove or modify what they've uploaded. With IPFS, as far as I'm aware, doing either doesn't really change the underlying data but just creates a new object in IPFS instead which you'd point to via IPNS. Anyone who still wanted to view the old content still could, provided they had the right content id.
God forbid you accidentally upload a "personal" photo, your only hope is that someone never comes across the content id of that image. There is no way to undo it!
[1]: https://github.com/WebAssembly/interface-types/blob/master/p...
We need to take firm steps to outlaw the practices that got us to this point in the first place. Ban dark patterns, mandate data-use as opt-in outside of a TOS, require breach disclosure within a set period of time, grant exclusive ownership to user generated content to the user, et cetera. There is a lot we can do here!
It's generally pretty fast, about what I'd expect if I was connecting to the box directly (which you technically are, I believe). Battery drain is probably a thing, but I honestly haven't noticed; my phone battery pretty much only needs a charge by nighttime, same as it was pre-tailscale.
I've had some concerns about GraphQL in the past when it was first coming up, but they look to be mostly addressed in some way shape or form. For example, using a CDN is now viable without hacks if you utilize something like Apollo Persisted Queries. Most of the research I've done on the topic recently has come up with a lot of outdated criticisms.
On that note, it almost feels as if people wrote off GraphQL in the beginning and have largely ignored the developments since. The people already on board the train seem to write more to an existing audience of users rather than people looking to get in.
Just hoping they come back around on CockroachDB-- I feel like it's a match made in heaven for what they're providing.