86 karma · joined October 1, 2015
Sorry for the pointless post but got to reminiscing.
Dismissing a new feature in an existing library seems quite excessive and possibly zealous. Or perhaps we should just stop using OSes entirely because they continue to release new features in memory unsafe languages.
Disclaimer: I wrote the OTel one, and am sad to see yet more context implementations being made, including the OTel one, these really need to all be on the way out.
While there are likely sustainability issues, I guess we will still continue to have these projects and hats off to everyone like Daniel working not just for themselves but also for their community.
Wanting to hold Python+C ecosystem more accountable is fair I think, at least from my own experience around half a year ago, Anaconda doesn't work and you need a Dockerfile for any sort of reproducibility, which can have issues since GPU with docker isn't that easy. And this means developers from the vendors working with Anaconda, for example, on solving the issue rather than just hoping for contributors to do it. If AMD were to make easy, reproducible builds without root or VM a reality, that would be reason enough to try their hardware. If not, hopefully Nvidia does and then there really would be no way across the moat for me at least.
I have a feeling the answer is yes, or don't know, and if there were any regulation enacted the best would be to ensure gratuities before service provided are either banned or guaranteed to be hidden. Gratuities after service provided don't seem to require any restriction.
Disclaimer: I live in a country without tips and love it, would feel better on trips to the US if it were the same.
The strategy I found for charging is to habitually plug in when in the shower, the few mins of charge per day provides "forever" battery life for me.
As others have mentioned, this is not all that useful of a service - it doesn't seem to even have the concept of a "plan" let alone any approval system and seems to only allow for the most basic of workflows. Given that TF by default will store state in a bucket with true locking, I can't come up with any potential benefit this provides vs using Terraform directly.
The main question is whether this will be improved in the future or is intentionally just "Terraform Trial Edition" with terms of partnership preventing anything encroaching on Terraform Cloud. Perhaps for the former, the trial is important to understand usage to better inform revenue sharing for a future improved product.
https://github.com/google/project-gameface/pull/31#issuecomm...
More interesting is not having the "This is not an official Google project so not supported" disclaimer so many repos in their org has.
Shady origins, shoddy maintenance, but the incident will be forgotten as is usually the case. The reality is Google still has huge mindshare and respect among engineers and will likely be immune to damage in these situations.
I have used clion with rust plugin and while it's better than nothing, it's generally been pretty spotty on all the features, completion, marking errors, refactoring. I'm looking forward to RustRover "pulling a GoLand" by bringing a proper IDE experience to rust.
FWIW my best config experience has been with HOCON via typesafe|lightbend/config in Java. The ability to compose environment specific defaults in a reasonable way just felt good. Of course /internal/config to dump the config was a necessity, but trivial, so I tend to be less sympathetic to DRY is not necessarily good arguments.
Have been missing it in Go, unfortunately Java's ability to publish files within packages (that can be imported in config) was a key part of the UX that is missing in any compiled language I've seen.
There is then the point where a startup may need to "step up" to a more large-scale language, for example when Twitter started incorporating Scala. But succeeding enough to reach this point is a small subset of startups, many probably not even called startup anymore, so any language at this stage may not "feel popular" when limiting to startups.
It really doesn't take a journalism major to see this is just a blog and may as well be a sob story for SBF since it does little more than that...
I believe this is likely the main point being made about luck - be unlucky enough to hit up an inexperienced interviewer and all the time spent preparing as in the linked OP is up in smoke.
Not sure if it counts as an average tech company, but in terms of non-FAANG I think startups and smaller companies can end up relying less on luck. There is more time and motivation to truly flesh out candidates, maybe giving non-interview coding tasks and such to balance out interviews. At a FAANG if there was an issue because of an inexperienced interviewer, again you need luck for a recruiter or committee to attempt a save among all the other applicants.
Got obliterated.
Also then started playing Shogi with him for the first time and while it didn't take that long to triumph with an all pawns handicap, after much effort finally reached being able to win including rooks/bishops. But it was obviously basically cheating since eventually you realize how easy it is to win with handicap be just putting 100% into defense.
Anyways, with those games to me it really felt that Shogi is the more strategic game, having similar mechanics to chess but being more dynamic. Chess in the end, even looking at GM matches, looks like much more pattern matching, i.e., tactics.
So my takeaway from that was that as much as I enjoy chess, Shogi is just the more complex game and its experts may just be able to defeat masters if they cared to because of the otherwise similar mechanics, as one of the anecdotes in the article.
Random share this is just personal but honest feeling from past experience and not an endorsement. Really fun memories.
I don't know if the license change actually means providers will not be able to work with Pulumi, but if it does, it seems risky to use Pulumi even for personal projects if newer provider versions (i.e., versions that work with newer products released by the cloud provider) will not work with Pulumi, it's a dead end. And that's not to mention the useful providers that aren't cloud and completely community developed that will not have the resources to maintain two codebases in any case (I'm thinking of Sendgrid).
I looked at terraform-sdk license - it still seems to be MPL. I think this means that all providers can continue to be open and work with both platforms, it will be important for Pulumi to clarify this to prevent the death spiral. Given some negative feedback towards the Hashicorp blog post from Pulumi employees on this thread, I am somewhat skeptical of this since if everything is fine, then complaining will otherwise have a negative effect, that us users have to assume that Hashicorp is actually stomping them out. And if it's the case, sorry but in good faith to everyone else that may need to work on infrastructure I make, I will have to be complicit in the stomping.
So I assume that's one reason to take an Uber? I was going to look into a charter anyways based on that advice.
Amtrak I'm more familiar with but at least in California it's just incredibly slow.
Currently I am thinking of focusing on AWS route 53 domains under the assumption that there is always a non-zero chance of needing something else on AWS so it reduces the number of accounts/IAM (either 1 or 0 versus guaranteed 1). Anyone have their favorite reasons to go with porkbun instead?
I've generally seen the release of a branded IDE for a language from Jetbrains to be when they have great support for it, hopefully it'll come for Rust but it's taking a long time, which unfortunately for a Jetbrains user to death at this point, means not using Rust itself.
Maybe, but if a system running today has no drivers installed signed by old certs, transparently blocking them, as well as defaulting to block, with an IT admin ability to unblock, for new installs seems quite easy.