Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
estebank
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
22 ms
·
301.
▲
by
estebank
1y ago
Do note that when rolling out features like these, they geoblock them, even on a per run basis, so it might be happening a lot throughout the world but it just hasn't reached your country. For an example, mobile YouTube in the US lets
302.
▲
by
estebank
1y ago
Even for the monolingual Google employees it's not uncommon for them to travel to other locales, even as part of their job, so they would be on the receiving end of this "experience" too. We've had 2 decades of experienc
303.
▲
by
estebank
1y ago
On the phone, so I can't now, but someone should file a ticket to that project about that error: https://github.com/learning-rust/learning-rust.github.io/iss... Be aware that it is not part of the rust-lang o
304.
▲
by
estebank
1y ago
Would you mind filing a ticket on GitHub.com/rust-lang/rust with that exact request? (I'm on the go and am not logged on GitHub on this device and wouldn't want this feedback to be lost). This should be relatively easy t
305.
▲
by
estebank
1y ago
You're moving the goalposts. You started at > it's fairly common knowledge that the Rust community leadership regards all other programming languages as existing in an adversarial, finite-sum outcome space with any remotely adj
306.
▲
by
estebank
1y ago
> it's fairly common knowledge that the Rust community leadership regards all other programming languages as existing in an adversarial, finite-sum outcome space with any remotely adjacent programming languages and regard it's
307.
▲
by
estebank
1y ago
> Aside from anything else, it’d be great if rust had better error messages when you run into this issue. Would you mind filing a ticket detailing what you'd wish the error had been? Without additional context, the only improvement
308.
▲
by
estebank
1y ago
This has problems as soon as it hits generics and lifetimes. That being said, I think a limited version of the feature that disallows the the same type with divergent lifetimes or even all generics would still be useful and well liked.
309.
▲
by
estebank
1y ago
Fun fact: the compiler itself has some limited inference abilities for return types, they are just not exposed to the language: https://play.rust-lang.org/?version=nightly&mode=debug&editi... I have some desire to m
310.
▲
by
estebank
1y ago
It depends on what you call "performance". IO throughput can be the same. So can be CPU utilization. Memory consumption will always be larger though, and the kind of code you need to write in Java to achieve parity might not look
311.
▲
by
estebank
1y ago
To illustrate: fn foo<S: Into<String>>(s: S) { fn inner(s: String) { ... } inner(s.into()) }
312.
▲
by
estebank
1y ago
Side note: There's an effort to cache proc macro invocations so that they get executed only once if the item they annotate hasn't changed: https://github.com/rust-lang/rust/pull/129102 There are m
313.
▲
by
estebank
1y ago
This is a pattern a crate author can rely on (write a function that uses genetics that immediately delegates to a function that uses trait objects or converts to the needed types eagerly so the common logic gets compiled only once), and the
314.
▲
by
estebank
1y ago
For loops are sugar around an Iterator instantiation: for i in 0..10 {} translates to roughly let mut iter = Range { start: 0, end: 10 }.into_iter(); while let Some(i) = iter.next() {}
315.
▲
by
estebank
1y ago
Are the US and Israel going to continuously bomb any working crew in the area that goes to dig?
316.
▲
by
estebank
1y ago
Some people on this thread are talking about things like canvas bags, which are more expensive and meant to be reused a lot, and others are talking about plastic bags that have a lot of material and are more durable than the old school &quo
317.
▲
by
estebank
1y ago
You are making the baseline assumption that the reason for reusable bags is to reduce greenhouse emissions , instead of reducing the number of plastic bags being discarded in public areas causing negative externalities like affecting wildl
318.
▲
by
estebank
1y ago
I also agree that the machine doesn't go off on a puff of smoke the second the OS is no longer supported, but having an Internet connected device with an unsupported OS is not tenable. There are options , like of course running Linux
319.
▲
by
estebank
1y ago
There are multiple avenues to improve both first and incremental compiles. They "just" require large architectural changes that may yield marginal improvements, so it's hard to get those projects off the ground. But after the
320.
▲
by
estebank
1y ago
> Why not both? For better and worse, the Rust project is a "show-up-ocracy": the work that gets done is the one that volunteers (or paid employees from a company donating their time to the project) spend time doing. It's
321.
▲
by
estebank
1y ago
There's a strong culture of "leave things better than you found them". When a user gets confused by the tooling/language, it's not the user's fault. If you got confused, chances are that others will too, so fix
322.
▲
by
estebank
1y ago
Whether a joke is funny to a given person is context dependent. “A dog walks into a bar and says, ‘I cannot see a thing. I’ll open this one.’” Is this a good joke? Do you find it funny? If not, do you happen to be a Summerian circa 1983 BCE
323.
▲
by
estebank
1y ago
Americans have been moving less and less, and that trend hasn't reverted. https://www.census.gov/library/stories/2022/03/united-states...
324.
▲
by
estebank
1y ago
Hot take: the primary role of a compiler is to turn malformed code into human readable diagnostics. They are error reporting tools with a codegen is side-gig.
325.
▲
by
estebank
1y ago
I think the interaction of "thing is cheap" and "thing is tiny" break all of our heuristics for "thing is difficult and energy intensive to produce".
326.
▲
by
estebank
1y ago
When maintaining a project, one gets exposed to the worst parts of it at an elevated rate. This makes maintainers be more critical than most, as we have an skewed view of the projects faults. So I can absolutely understand when someone cl
327.
▲
by
estebank
1y ago
This is an approach that I really like because of some not necessarily obvious properties: the behavior of the code as written is easily predictable, while still getting the benefits of a compiler's help. The suggestions can be more ag
328.
▲
by
estebank
1y ago
When an error happens it's the best time to teach the user something. If you can figure it what they were trying to do something, you can tell them why what they tried to do doesn't work, and what to try instead.
329.
▲
by
estebank
1y ago
This is something that I never get tired to hear. I'm really glad that you've found them helpful.
330.
▲
by
estebank
1y ago
That was done by @compiler-errors, as part of an improvement to make some of the suggestions I introduced easier to read.
More ›