6,646 karma · joined February 8, 2012
I find dealing with a browser tab to be a bit awkward, especially if I'm working on a Rust project using Wasm and actively testing in a browser and having to flip between docs and my app. Having a dedicated documentation viewing app that I can show/hide with a keyboard shortcut just saves a second or so every time I need to pull up docs. And the integration with IDEs can sometimes mean I don't even have to leave my editor to get the answer I need. It also integrates documentation for std/core with docs for crates I'm using giving me a single search of everything that my Rust code can use. The only downside compared to cargo's docs is that it doesn't document my own code that I'm working on, but it's much easier to remember the details of that code.
The cherry on top is that it isn't limited to Rust. If I'm working on something with an FFI dependency, I can have the same documentation workflow for C/C++ documentation. If I'm working on a Wasm project, I can pull up HTML/CSS documentation the exact same way. All my documentation lives in the same place under the same keyboard shortcut.
I kinda disagree with this. If it were a local retailer run by your neighbors, you’d be absolutely correct. But if you’re talking about Target, you’re now in the territory of a system of economic oppression where money is siphoned out of local communities by large multinational corporations and the actual residents have no ownership over anything. During the 2020 riots, there were definitely some people trying to make the point, “we have no ownership of our own neighborhoods.”
I can see many people, especially black Americans, feeling all but imprisoned by the fact that they can’t afford to own property, can’t run the businesses that serve their community and are at the mercy of white people who move in and gentrify the neighborhoods forcing them to find new, less desirable places to live. The police who are the immediate focus of protests become merely the jailers in a systemic prison of which Target and other large retailers play a huge part.
There's nothing wrong with either approach, they just have different trade-offs because their goals are different. Rust's approach will sometimes push complexity onto the programmer to handle. But it can be made to perform better and more predictably than the Go equivalent. This might not matter if you're not pushing the performance envelope, but if you are, Rust makes that possible in a way that Go simply doesn't. You'd never want to write code using goroutines for an embedded device with limited CPU/memory, but Rust's async is already proving useful for these sorts of projects.
However if you can tolerate the performance overhead that Go imposes, giving the programmer a simpler mental model can easily be worthwhile. Technology is all about trade-offs and you have to choose the right tool for the job.
It feels like Google has it backwards…they’re siloing the fraud detection and banning across different products. If they switched that and did fraud detection across product boundaries and more targeted bans, we’d see far fewer of these AI-run-amok pleas to publicly shame them into getting a human to look into an obvious mistake.
Declare somewhat-short, fixed terms (5 years?) for every bit of content. The first term is free and then subsequent terms increase in cost geometrically. The first renewal could be an almost insignificant amount…but just the fact that it’s something would mean most content that is unmonetized would enter the public domain after the initial free term. Successive terms would start to only make sense for the most profitable content.
Being able to balance a healthy public domain with the ability for content creators to put out content that costs a ton to produce seems like it should be the goal of the copyright system.
One of the ways that I’d see a proc macro attack playing out in real life would be to attempt to obtain the API token from cargo login to allow the attacker to publish a malicious version of a popular crate. But if cargo login is only run on the CI instance responsible for publishing and developers test their code on their individual dev machines, the attack fails.
We shouldn’t worry about making security 100% effective. Rather, we should be concerned with stopping as many different attacks as we can and providing users with as many building blocks as possible to let them protect themselves. There will always be vulnerabilities. But using that as an excuse for inaction isn’t helpful.
Similarly, all of the attacks that execute code at compile time are mostly addressed currently by building code in a Docker container. It’s not a perfect security measure, but it greatly increases the probability that a build.rs or proc macro attack will fail.
Your (1) strikes me as something that can never be solved to provide 100% safety, but that there are partial solutions which, in practice, can significantly reduce the attack surface. And hiding behind “fundamentally unsolvable problem” will get in the way pushing for the meaningful half-measures that offer some degree of real-world protection.
As an example, I have shell aliases setup to cd into the folder(s) open in Finder or reference files selected in Finder.
This kind of indirect scraping can be useful for getting almost all the information you want from sites like LinkedIn that do aggressive scraping detection.
This is a dangerous message to push. The reality is that there are many lasting consequences of COVID that fall short of death but are, never the less, quite serious. The so called “long COVID” really needs to be part of the vaccine calculus because the health consequences are very much worse than the purported side effects from the vaccine.
I’ve seen this kind of phenomenon first hand when it comes to drugs. As a teenager, there was lots of anti-drug messaging trying to convince us that ecstasy was dangerous. And all of it focused on scaring kids by exaggerating the risk of death. But we could see people taking it regularly and none of them were dying. And so it undercut the message. But decades later, I know a few people who’ve had depressive episodes potentially linked to heavy ecstasy use. And that consequence was never a part of the decision-making process because the authorities discredited themselves by being unnecessarily and obviously hyperbolic.
We need better messaging that provides people with the full range of consequences for their choices. The “you’re going to die!!!” hysteria ends up being counterproductive. Even as deadly as COVID is, the truth is that unvaccinated people probably won’t die from their case…the vast majority survive. But if people understood how many recoveries included long-term health consequences that significantly affected their quality of life, they might be better able to weigh that against the potential side effects of a vaccine.
There are a number of other advantages to this too. For one, it helps immigrants integrate better the more Americans they end up working with. The current system can result in silos where immigrants mostly work with other immigrants. And it helps Americans to work alongside skilled workers by giving them increased learning opportunities. It also works better for lower-paid skilled positions like nurses and scientists who don’t have to compete with higher-paid tech workers for visas.
I’m okay with giving an unlimited number of visas (background checks required) to any company that employs at least 70% Americans in each salary band. At worst, it creates an incentive to hire unqualified Americans just to get access to foreign talent, which is still a win for this country.
But as soon as you get into consumer software with auto-update mechanisms and an expectation that end users won’t be computer professionals who know how to read a CVE and evaluate its urgency, the “written in Rust” distinction becomes a mostly irrelevant implementation detail. Or, worse, it’s an indication that the GUI will feel wrong in some way because the Rust community seems averse to writing GUIs with GTK, UI Kit and whatever the hell Microsoft recommends using for Windows these days.
We really need to start attaching eye-watering financial penalties to companies that leak data so that we make the only sane decision be not storing that data in the first place. Collect it and shuttle it to where it needs to go...but under no circumstances commit it to at rest storage.
Billionaires are a very different animal. They have armies of lawyers and financial managers that help them navigate the movement of wealth through the global system to avoid taxation. They avoid recognizing income at all opportunities and strategically use debt to provide for themselves without exposing themselves to tax consequences that would come from getting the money they want to spend. They can traverse the globe looking for the most favorable taxation rates to maximize their wealth.
There’s been a lot of “tax billionaires” and “billionaires shouldn’t exist” rhetoric without much substance to how to actually achieve that goal. Billionaires aren’t just going to say “aww, shucks, guess we’ve got to pay up” when governments decide to up their taxes. They’re going to react in ways that are both hard to predict and harder to stop. Capital flight is a real threat and will require a massive, coordinated effort on the parts of all the nations that comprise the global financial system to curtail. The efforts towards a minimum corporate tax rate are a good start, but that’s only one step of many that are necessary before “tax billionaires” becomes a realistic target.
Sam Harris has a lengthy discussion about this separation in "Waking Up: A Guide to Spirituality Without Religion" where he looks at what we've learned from patients who've undergone a corpus callosum surgery. The TL;DR of that surgery is that it's done on people with severe seizures to sever the two hemispheres of the brain to minimize the seizures. But it also tends to (gross over-simplification incoming) create two distinct personalities in the same person, so Harris looks at essentially what gets doubled as elements that cannot be part of the self.
A lot of the rest of the book also deals with the nature of self as revealed through meditative practice and drug use. It's a somewhat tedious read, but it's really fascinating stuff.
This is why both are so necessary. Integration testing tests whether the whole thing is coherent when put together. But it’s terrible for testing edge cases and error scenarios. That’s where unit testing comes in. It gives the developer a chance to codify every edge case they’ve considered to automate the process of catching regressions.
I also remember attending a session that Intuit offered on the competitor landscape and being quite surprised that Wave wasn't covered. Intuit just doesn't take them seriously, but their products, to me, seem better than just about every competitor covered in the session, including Xero. They've got a self-employed offering [0] that might be worth experimenting with since you can start for free and only pay when you need the premium features.
Lunch is, IMHO, the biggest loss when going full remote. It’s also somewhat of a magic bullet for fixing individual communication breakdowns. As a manager, when you see two people failing to coordinate, especially across teams, just have them eat a few lunches together. Offering to have the company pay is usually enough to make it happen. For a few tens of dollars, you establish a relationship with very low communication friction. It’s ridiculously good value for the company.
I’m toying with the idea of adding an options page so that I could release it to the chrome store, but I hate UI work, so I haven’t gotten around to that yet.
The neat thing about lunch is that the conversations are entirely non-directed without feeling like the time is being wasted in a meeting. Conversations can cover a specific project, when a high degree of coordination is necessary, generalized venting, when there are shared frustrations or just be about non-work topics that help a team bond and get to know each other as people rather than workers. It’s like a meeting that doesn’t feel like a meeting that can be strategic or therapeutic as needed. There’s really no way to replicate the beneficial effects of eating lunch together when workers are remote.
As a manager, this has also been one of my go-to tricks for successful cross-team projects lasting any significant amount of time. I tell one of my team members to setup a lunch with at least one member of the other team on a weekly basis and use the incentive of authorizing the company to pay for it. For ~$20/person/week, the cross-team communications issues basically disappear. It’s ridiculously cost effective and almost magical in how well it works.