882 karma · joined May 26, 2014
For what I do, throwing up Slim, Guzzle, and Doctrine works well. You could make the argument that any one of those individually is a "framework", or that collectively I've made a new framework in 3 lines of composer.json by combining them. Point is many (and the article suggests) see framework or no framework as some massive all-or-nothing choice, when picking the parts you want, even after you've built your system out, us also an option.
While I can understand the resistance to selection criteria if it removes more nuanced decisions necessary in building a team, I can't think of a better way to offset those biases you describe. Those biases are extreme and clearly, left to our own devices, we do a bad job addressing or recognizing them.
Much like the other problems in the article, there's no obvious villain, and it's a long process to change a deeply flawed system.
Flash seems like the more direct competitor that he touches on. It's easier to see in hindsight, but they really won by taking care of the content creators. I tried a few times to make RIP graphics back in the day but could never really figure it out. Flash, in contrast, had an experience for the designers and artists that is still remembered fondly today. It set the course for a whole new generation of animation.
I'm about 1.5y into a startup that's picking up steam, and I've stopped feeling worried about similar "ideas". We have a plan for who wants our product, what they care about, and how much they'll pay for it. We have an platform that can be used to support a plethora of unique marketable products. We have a sales team in place. There's so much more going on than the original "what if we used version control thinking with contracts and legal knowledge?"
Eg we'd been using the `iss` field, a claim, to determine which key to use, when we should've used the `kid` in the header. All claims are now completely inaccessible until verified to the point where there's no way to access them short of manually deserializing the jwt. We'd also allowed some invalid tokens where the `exp` was in the past, only if you were refreshing the token of an active session. This could've caused problems if we ever wanted to issue a token that expired very quickly, since you could have a token that's theoretically 10-times longer lived than you intended.
I find good managers are capable of measuring progress without demanding frequent "status updates". It varies from job to job, but I find getting frequent, small PRs (even to dev branches) works well.
This situation you describe sounds a lot like dealing with garbage-collection cycles, so you give a good recommendation on something to watch out for, as rust performing at the level of a GC'd language removes a big reason for choosing rust.
The surprising thing is, I find rust an incredibly effective language at sparing me from worrying about trivialities. Once you learn the slight differences in what all those things mean, you can be pretty direct. Overall I find rust one of the harder languages to write, but one of the easiest to read, and reading code is generally where you'll spend more time.
One way it's helped, is it's a really easy topic to bring up with clients or on sales calls. It makes me more relatable, and gives a good first impression since people assume I'm at least competent enough to provide basic care to a child.
That said, constructing the resolvers with the `#[juniper::graphql_object` macro has been incredibly easy. They used to use some clunky DSL, but since the move it's been great. Don't think I'd consider moving if async-graphql isn't as strong on that, but I won't really know until I try both.
It's especially galling because the people pushing for these nigh-Stalinist levels of fed intervention and central planning (look how much support oddly favoured industries like manufacturing and coal get) are also posturing as champions of the Free Market. It's like we can't make any progress because nobody in charge is willing to argue in good faith.
As a programmer, I want Good Software to align with work that they'll pay me for. I'm fortunate enough that this is the case with my current work, though I can recognize that this hasn't always been the case over my career.
The big problem with comparing directly to europe, is not only the timing but the demographics. Italy was hard hit because they have a lot of old people. Canada already has a lifespan 4 years longer than America's, which if you think about it is probably better proof that America is failing than most of the article.
Interestingly they picked the best possible case to showcase rust's strengths, where the free happens on drop. If it were a case where you needed strict control over where that memory came from and _when_ it gets freed, C would seem like a nice fit, but rust is great when you only care that the memory is gone once your variable's out of scope.
The sqlx crate for rust also has a macro called query!, which (at compile time) validates the SQL and created a value of type "record". Similar idea there, since you'll get early exceptions thrown by the compiler if you write sql with errors in it.