Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
epage
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
17 ms
·
241.
▲
by
epage
4y ago
> A) is easy to write one off scripts that do a job fast, with minimal thinking and effort. I am thinking of Python and Ruby. For me I can write code with high velocity in these languages. Once I wrap up some other projects, I plan to ex
242.
▲
by
epage
4y ago
Put another way, writing clean code is like writing prose. You need to clearly break down your thoughtt, whether its sections, paragraphs, sentences, and fragments, or files, functions, blocks, groups of lines. Drove me nuts when working in
243.
▲
by
epage
4y ago
What is with the modern C++ community treating "C/C++" as a shibboleth to gatekeep over? I'm a seasoned C++ dev (using it before C++98 was available, kept up with trends) and I've never seen this before until the la
244.
▲
by
epage
4y ago
I think https://fosdem.org/2023/schedule/event/rust_rust_api_design_... has a lot of general application outside of Rust.
245.
▲
by
epage
4y ago
To add, in rust 1.63, cargo added support for negative numbers, so you can say `cargo build --jobs -2` to leave two cores available. See https://github.com/rust-lang/cargo/blob/master/CHANGELOG.md#...
246.
▲
by
epage
4y ago
Hosted pre-compiled builds would need to account for - Feature flags - Platform conditionals - The specific rust version being used - (unsure on this) the above for all dependencies of what is being pre-compiled There is also the impediment
247.
▲
by
epage
4y ago
>C++ is becoming a legacy language and finding contributors in the future will become difficult To add to this point, I used to work at a large-ish C++ shop and we were already having problems finding C++ developers years ago and I'
248.
▲
by
epage
4y ago
See https://github.com/rust-lang/libs-team/issues/72#issuecommen... for what I believe is an exhaustive list of possible ways of helping the situation.
249.
▲
by
epage
4y ago
I'm interested in making REPL support for Rust first-class and am curious where people think evcxr lets you down in usability and any suggestions in overcoming them. Compiled languages offer unique challenges for REPLs and I feel like
250.
▲
by
epage
4y ago
Also git-stack has a --pull flag to rebase all local branches and --push to force-push-with-lease them. EDIT: oh, article author is git-branchless author, they know of git-stack.
251.
▲
by
epage
4y ago
> Can you give an example or provide a citation to this? I'd love to read more. `nom`'s `Parser` trait is implemented for functions. You can mix and match parser functions and parser types, including the built-in types that ar
252.
▲
by
epage
4y ago
> * The borrow checker. Memory safety is great but there are plenty of memory-safe designs that the borrow checker complains about. With modern C++ and sound design techniques, memory safety is not something I worry about much in my C++
253.
▲
by
epage
4y ago
> Some Rust programmers, when faced with performing operations on a sum type (like Result) or container, tend to reach for point-free map-filter-reduce code stuffed with higher-order functions, lambdas, trait generics, and return type in
254.
▲
by
epage
4y ago
A surprising source of slow compile times can be declarative macros in Rust [0]. I believe the core of the problem is that it has to reparse the code to pattern match for the macro. One egregious patter is tt-munchers [1] where your macro i
255.
▲
by
epage
4y ago
Someone recently looked into doing this by default. The problem was the results varied depending on how often your "host dependencies" (proc macro, build.rs) were shared with your "target dependencies" (`dependencies`,
256.
▲
by
epage
4y ago
I appreciate when they work well as a general purpose language. I might need more control in a kernel. Userspace support code benefits from being in the same language and needs some systems programming features but doesn't need as much
257.
▲
by
epage
4y ago
Interesting ideas but I'm in the camp that having everything be explicit causes complexity to be foisted on the user. There are times and places where that simplicity might offer some advantages but I'd rather my systems language
258.
▲
by
epage
4y ago
He didn't expect to rake in that much and iirc kickstarter doesn't let you pass on economy of scale to your backers (hence stretch goals in a lot of campaigns). Like with his Audible comments, this also served as another way for h
259.
▲
by
epage
4y ago
> That said, there was a floor which we were not allowed on, and I believe that was the sales floor Is it just me or is this nuts? The only time I've seen restricted access is when there are security concerns (national security, sp
260.
▲
by
epage
4y ago
Of the changes that didn't make the blog post (but is buried in the release notes) is that cargo-publish will now block until the publish process is complete. This affects you if you are releasing a series of crates in a row or releas
261.
▲
by
epage
4y ago
Moving cargo-edit into cargo has been a slow but fruitful process. Besides any of the technical work involved in getting this into cargo (e.g. making `toml_edit` production-ready), we had a long discussion about the exact UX ( https:/
262.
▲
by
epage
4y ago
Really grateful for the work cassaundra did to get this in! A part of the cargo-remove work that didn't make it into 1.66 is that cargo-remove will garbage collect references to the remove dependency. For example, if you remove the la
263.
▲
by
epage
4y ago
My first job out of college had 3 basic titles that broke down into - New grad, takes more than give - Individual contributor - Team technical lead I really liked it as it was clear what the roles where and how to move up. We kept running i
264.
▲
by
epage
4y ago
Agreed that there are categorical tiers of CI times (instant, check something, grab a coffee, grab a lunch, see you next day) and optimizations within a tier don't matter. I will say blocking review on CI is unneeded and, depending on
265.
▲
by
epage
4y ago
> Nim is also easier to learn - if you know Python and any conventional statically typed language, it's a walk in the park. I I kept hearing the comparisons to Python so I thought it'd be interesting to pick up but the syntax a
266.
▲
by
epage
4y ago
On top of what others said, cargo is looking to further improve the fix workflow. Right now, some errors offer fixes and these are marked machine-applicable. cargo-fix will apply these. The workflow was originally written for Edition migrat
267.
▲
by
epage
4y ago
Not like I always get two day shipping anyways. They now shuffle things between warehouses so they can say it shipped in two days (from the closest warehouse) but the effective shipping time can be longer.
268.
▲
by
epage
4y ago
Looks like you are using clap v2? Feel free to ping me for help on moving to v3 then v4. I expect the rate of breaking changes to be slowing down and to be smaller in scope (from the users perspective) so now is a good time. Id love to hear
269.
▲
by
epage
4y ago
Whats the "aha" moment for it, the Froms? The author might not have included that as they call out you likely shouldn't directly wrap another error. I go a step further and think that public errors shouldn't have From&#x
270.
▲
by
epage
4y ago
Doesn't bstr replace memchr? Unsure if it replaces bytecount.
More ›